-
Notifications
You must be signed in to change notification settings - Fork 94
-
Notifications
You must be signed in to change notification settings - Fork 94
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
Exception when indexing guava-30.0-jre #93
Comments
@bennypi thanks for the report. This is an unusual one, but I will get this fixed quickly. |
Ignore bogus type annotation entries - Fixes #93
@bennypi this is fixed in 2.2.2.Final and 2.1.4.Final. It may take 24 hours for the release to sync to maven central |
I can confirm i was getting this error in Eclipse with Gauva 30. I replaced jandex 2.1.2 in Eclipse with 2.1.4 and the error is resolved. Thank you! |
Had the same problem with guava <!-- https://mvnrepository.com/artifact/com.auth0/jwks-rsa -->
<dependency>
<groupId>com.auth0</groupId>
<artifactId>jwks-rsa</artifactId>
<version>0.15.0</version>
<exclusions>
<exclusion>
<groupId>com.google.guava</groupId>
<artifactId>guava</artifactId>
</exclusion>
</exclusions>
</dependency>
<!-- https://mvnrepository.com/artifact/com.google.guava/guava -->
<dependency>
<groupId>com.google.guava</groupId>
<artifactId>guava</artifactId>
<version>30.1-jre</version>
</dependency> |
So the issue is fixed in 30.1 ? |
Well that is good news. It was driving me nuts. |
jandex is not capable of parsing the current guava release, guava-30.0-jre. It fails when indexing ClosingFuture.class.
Please see the stacktrace:
I became aware of this problem because a deployment of mine is using this version of guava, and when I deploy the EAR in to JBoss EAP 7.3.2, a warning with a similar stacktrace is thrown. The version of jandex in the JBoss is jandex-2.1.2.Final-redhat-00001, however this problem still exists with the 2.2.1 release.
The text was updated successfully, but these errors were encountered: