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
Deprecations from Java may be not taken into account in mixed projects #9617
Comments
Imported From: https://issues.scala-lang.org/browse/SI-9617?orig=1 |
@retronym said: |
@mpociecha said: |
@mpociecha said: There's even already my very old PR in Simon's repo (only the last commit does matter): soc/scala#3 |
@soc said: |
@SethTisue said: |
@soc said: |
Fixed in scala/scala#8781 |
There's a problem that deprecations from Java are not taken into account in Scala after parsing Java sources in mixed projects (when they are not yet compiled). I mean that warnings are not generated.
They would be generated only during the incremental compilation (Java files already compiled using javac). It's esp. problematic in case of -Xfatal-warnings as the CI build may pass but users will report problems in Scala IDE or IntelliJ.
The minimal reproduction:
J.java
S.scala
Make project (for the first time) or Rebuild Project. Everything is okay.
Now add some blank line in S.scala and start build:
Warning (or obviously Error in case of -Xfatal-warnings):scalac: there was one deprecation warning; re-run with -deprecation for details
The text was updated successfully, but these errors were encountered: