-
Notifications
You must be signed in to change notification settings - Fork 737
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
invalid start position with var
#1563
Comments
It goes away if I split the line in question into two:
|
cushon
changed the title
java.lang.IllegalArgumentException: invalid start position
invalid start position with May 19, 2020
var
The issue is that javac is replacing |
copybara-service bot
pushed a commit
that referenced
this issue
Jan 8, 2021
Fixes #1563 PiperOrigin-RevId: 350608767
copybara-service bot
pushed a commit
that referenced
this issue
Jan 8, 2021
Fixes #1563 PiperOrigin-RevId: 350608767
copybara-service bot
pushed a commit
that referenced
this issue
Jan 8, 2021
Fixes #1563 PiperOrigin-RevId: 350608767
stevie400
pushed a commit
to HubSpot/error-prone
that referenced
this issue
Jan 15, 2021
Fixes google#1563 PiperOrigin-RevId: 350823946
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of the problem:
I was setting up Error Prone for our codebase, and when running it as a maven plugin, EP threw a unhandled exception:
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
The line in question is:
It's pointing to the
new
keyword.My pom.xml (parent pom) is set like this:
where
${java.version}
is 11.What version of Error Prone are you using?
error-prone version: 2.3.4
Have you found anything relevant by searching the web?
#1124
#1129
Also I got this error, don't know if it's relevant:
The text was updated successfully, but these errors were encountered: