Skip to content

upgrade to scoverage 1.4 #107

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 9 commits into from
Nov 19, 2019
Merged

upgrade to scoverage 1.4 #107

merged 9 commits into from
Nov 19, 2019

Conversation

maiflai
Copy link
Contributor

@maiflai maiflai commented Jul 28, 2019

  • exclusion patterns appear to be broken upstream
  • still investigating other breaks

@maiflai maiflai changed the title upgrade to scoverage 1.4.0 upgrade to scoverage 1.4 Aug 10, 2019
@maiflai
Copy link
Contributor Author

maiflai commented Aug 29, 2019

@eyalroth
Copy link
Contributor

Should we add a (functional) test case for running with 1.3.1 with these changes to see they didn't break backward compatibility?

@maiflai
Copy link
Contributor Author

maiflai commented Aug 30, 2019

Unfortunately they depend on a new function in 1.4 - do you think that's ok?

@eyalroth
Copy link
Contributor

Yeah I can see that IOUtils.reportFileSearch has been replaced with IOUtils.scoverageDataDirsSearch, so there's actually no way to maintain backward compatibility.

That makes sense though; this plugin isn't really supposed to add any additional functionality and is just a "proxy" for the scalac plugin. In fact, defining a custom scalac plugin version (via scoverageVersion) should be experimental at best, much like it is with the maven plugin. Let's just update the README to clarify that :)

@maiflai
Copy link
Contributor Author

maiflai commented Aug 31, 2019

Yes - I think it's possible to do things via reflection but it makes this more complicated than they need to be, given the scope of the plugin (as you say).

@gslowikowski - please would it be possible to get scoverage/scalac-scoverage-plugin#276 merged into a Snapshot so that we can test this?

Thanks,
Stu

Conflicts:
	src/functionalTest/java/org.scoverage/ScalaSingleModuleTest.java
	src/main/groovy/org/scoverage/ScoveragePlugin.groovy
	src/main/groovy/org/scoverage/ScoverageReport.groovy
@maiflai maiflai merged commit 7940992 into master Nov 19, 2019
@maiflai maiflai deleted the scoverage_1_4_0 branch November 19, 2019 20:38
@eyalroth
Copy link
Contributor

@maiflai We should probably update the part in the README about the scoverageVersion option; we should note that (a) the default value has changed, (b) the plugin is compatible only with 1.4+ versions, and (c) it is experimental.

@maiflai
Copy link
Contributor Author

maiflai commented Nov 20, 2019

yes, agree on (a) and (b) but not sure what you mean by (c)? it's new, but I wouldn't call it experimental.

I do think we should release this as a new major version of the Gradle plugin - as you pointed out before, the behaviour of the plugin has changed significantly. I'll add notes to the upgrading section.

@eyalroth
Copy link
Contributor

It is experimental as it might not be compatible with future versions of the scalac plugin (as happened in this case). I guess it's not crucial to mention that, though :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants