lombok causes an IndexOutOfBoundsException in ParameterName #780
Labels
Comments
This was referenced Dec 13, 2017
|
Quick update: This can be reproduced with error-prone tasks.withType(JavaCompile) {
// workaround for: https://github.com/google/error-prone/issues/780
options.compilerArgs += [ '-Xep:ParameterName:OFF' ]
} |
This was referenced Mar 8, 2018
ron-murhammer
pushed a commit
to triplea-game/triplea
that referenced
this issue
Mar 23, 2018
Now working with lombok, still requires a workaround though :( See google/error-prone#780 for more info
Closed
|
Just wanted to cross-reference this issue as well, related to the latest IntelliJ IDEA 2018 EAP builds: |
|
@mmoayyed thanks for that snippet. Helpful until the bug is resolved |
This was referenced Jun 13, 2018
zregvart
added a commit
to chirino/syndesis
that referenced
this issue
Jun 13, 2018
Our use of Lombok and Errorprone leads to an error[1] when compiling connectors, as a workaround this disables the name check until this is resolved in Errorprone. Fixes syndesisio#2805 [1] google/error-prone#780
|
Is this fixed yet? |
|
I still see this in errorprone 2.3.1 |
|
For version 2.3.2. This issue still exists. I applied suggested workaround as a maven compiler parameter. <plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.8.0</version>
<configuration>
<compilerId>javac-with-errorprone</compilerId>
<forceJavacCompilerUse>true</forceJavacCompilerUse>
<source>8</source>
<target>8</target>
<compilerArgs>
<arg>-Xep:ParameterName:OFF</arg>
</compilerArgs>
</configuration>
<dependencies>
<dependency>
<groupId>org.codehaus.plexus</groupId>
<artifactId>plexus-compiler-javac-errorprone</artifactId>
<version>2.8.5</version>
</dependency>
<!-- override plexus-compiler-javac-errorprone's dependency on
Error Prone with the latest version -->
<dependency>
<groupId>com.google.errorprone</groupId>
<artifactId>error_prone_core</artifactId>
<version>2.3.2</version>
</dependency>
</dependencies>
</plugin> |
|
When I try the workaround mentioned above I get the following error: |
|
@anataliocs If you're using |
|
@tbroyer I was able to resolve the issue adding the arg to |
|
I'm using 2.3.2 and I'm having the same issue, this bug was reported in 2017 and it still an issue?: |
The same here. Here is the code that could reproduce the error: @Getter
@RequiredArgsConstructor
public class FileDto {
private final Integer id;
private final String type;
} |
|
This is fixed on master but not in 2.3.2 |
|
Thanks, do you know when can we expect it to be in maven ?
|
|
@epmjohnston When are you planning to push the next release? |
|
Bump |
|
Does 2.3.3 have it ? |
|
2.3.3 should contain the fix, haven't tried it though |
|
It can be closed, 2.3.3 is fine! |
|
Can also confirm that upgrading from 2.3.1 to 2.3.3 has resolved this issue for me. |
|
I use the latest version 2.3.4 and still get this error when a class uses the @slf4j annotation of lombok: So either this issue is not fixed or #1034 nor #905 are duplicates. |
|
Yeah, I get exactly same issue with only lombok |
|
re: #780 (comment), that stack trace contains |
cushon
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After #690 was fixed, I removed the exclusions for the problematic bug patterns and tried to compile a project using Lombok, but it looks like the new bug pattern
ParameterNamealso does not work well with Lombok it seems. Next time I'll make sure to try out Error Prone snapshots before a release :)Versions
Error Prone version:
2.1.2Lombok version:
1.16.18/1.16.16Maven version:
Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-04T04:39:06+09:00)Java version:
1.8.0_144, vendor: Oracle CorporationNote that I am also able to reproduce the issue with JDK 9.
Reproducing Class:
Stack trace
Workaround
Disable the newly introduced
ParameterNamebug pattern via a compiler argument:-Xep:ParameterName:OFFThe text was updated successfully, but these errors were encountered: