-
Notifications
You must be signed in to change notification settings - Fork 41
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
Gradle Plugin fails with Scala 2.13.x in Multi-Project Builds #182
Comments
Please provide a simple reproduction? I think we have simple test cases here showing that 2.13 works. Failing that, a full reproduction would be helpful, but it's often not possible to provide this. |
Yeah, I tried to see if I could modify the Integration Test for the multi-project build to give a reproduction, but it hasn't been as straight-forward as I had hoped. I know I am not the only person with the issue... so there likely is a way to reproduce, I just haven't identified a simple repro path yet. |
@maiflai When I try running the integration tests locally I found a few failing ones. However, the failures might be a different issue. Is there a setup step I am missing which might be causing this? |
This project should have locked down everything apart from the JDK version, so I don't quite know what might be different.
https://github.com/scoverage/gradle-scoverage/actions?query=branch%3Amaster says that this has built using GitHub Actions, but it's now a while ago and the log has gone. It should have used JDK 11 according to https://github.com/scoverage/gradle-scoverage/blob/master/.github/workflows/gradle.yml Please could you provide the actual test failures, and perhaps the full build log? |
@maiflai I generated a buildscan here: https://scans.gradle.com/s/lc2oudpwa5hpm The zipfile below is the |
Actually, look at this build scan instead: https://scans.gradle.com/s/f6gejlextz7rm I had some leftover cruft in the functionalTest path which I forgot to remove before I ran that last one. This is more inline with the failures I was seeing before. Sorry for any confusion. |
I think you may still have some cruft leftover here - have you tried a full |
On your original failure - what other plugins are you using please? I seem to recall difficulties with other plugins which add scala dependencies to the build classpath. |
|
can you supply the full set of dependencies for all configurations please? I don't think there's anything obvious in the main build classpath. |
Same here :(
|
Sorry - please could you provide a minimal build that reproduces the problem? Thanks, |
7.0.0
1.4.11
7.14.2
2.13.7
11.0.13
I originally filed this against the scalac-scoverage-plugin. As a result they have added a unit test for the
.aggregate()
method which this plugin calls, but it seems to pass suggesting the problem may be exist within the Gradle plugin itself.Running
aggregateScoverage
with Scala 2.13 results in the following stack trace:The text was updated successfully, but these errors were encountered: