You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a possibility that JDT bails out scanning fully valid code only because the IScanner was created with wrong (too old, default) source level.
I've checked how much code still uses org.eclipse.jdt.core.ToolFactory.createScanner(boolean, boolean, boolean, boolean) and see two references in JDT that probably should use proper source compliance set.
I will try to change that and see if some test fails.
The text was updated successfully, but these errors were encountered:
To avoid InvalidInputException if the source code contains elements not
covered by Java 1.3 JLS, specify proper source/target arguments while
creating scanner.
Fixeseclipse-jdt#292
To avoid InvalidInputException if the source code contains elements not
covered by Java 1.3 JLS, specify proper source/target arguments while
creating scanner.
Fixes#292
To avoid InvalidInputException if the source code contains elements not
covered by Java 1.3 JLS, specify proper source/target arguments while
creating scanner.
Fixeseclipse-jdt#292
Follow up on the issue surprised me a lot in spotbugs/spotbugs#2134
There is a possibility that JDT bails out scanning fully valid code only because the IScanner was created with wrong (too old, default) source level.
I've checked how much code still uses
org.eclipse.jdt.core.ToolFactory.createScanner(boolean, boolean, boolean, boolean)
and see two references in JDT that probably should use proper source compliance set.I will try to change that and see if some test fails.
The text was updated successfully, but these errors were encountered: