-
Notifications
You must be signed in to change notification settings - Fork 45
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
Conversation
maiflai
commented
Jul 28, 2019
- exclusion patterns appear to be broken upstream
- still investigating other breaks
Should we add a (functional) test case for running with |
Unfortunately they depend on a new function in 1.4 - do you think that's ok? |
Yeah I can see that 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 |
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, |
Conflicts: src/functionalTest/java/org.scoverage/ScalaSingleModuleTest.java src/main/groovy/org/scoverage/ScoveragePlugin.groovy src/main/groovy/org/scoverage/ScoverageReport.groovy
@maiflai We should probably update the part in the README about the |
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. |
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 :) |