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
Set -release
parameter instead of -target
#140
Comments
@danslapman The current plugin was tested up to certain scalac versions. Without the intervention in the calss mentioned, gradle, up to the version I have tested did |
See also this bug (similiar situation happened with official graldle scala plugin): gradle/gradle#23962 |
@danslapman next plugin release will adhere to |
@danslapman just created a test able to reproduce the issue. Can you confirm this error happens when running task |
Hi @prokod! Just cheked - error does not happen on |
Tried with scala 2.12.18 & 2.13.12 |
@danslapman so i took your template repo and turned it into a test I observe the failure but ... If I comment out this part in your example
No error is thrown while compiling In this May I ask the reason for this block ? |
My bad, I added this setting years ago and missed it during the last update. I just removed -release, but the error still happens for me on |
My Java version (for your reference):
|
Would you be able to share gradle log from following run |
|
I can try other JVM if you wish |
Got same results on
|
Ok So I have managed to run the test with java 17. Interesting enough I got the same error (given that the compiler is set with |
Hello! I just updated my template repository for scala and found that now
gradle crossBuildAssemble
fails withI found that
-target
is unconditionaly set by tuneCrossBuildScalaCompileTask. Looks like the name of that argument must be aware of concrete version of scalac... Without that plugin is unusable with latest scalac versionsPersonally I'd also like to have something like
targetCompatibility.strategy = 'none'
- from sbt user perspective silently setting scalac arguments looks kinda strange...The text was updated successfully, but these errors were encountered: