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
I have a Quarkus application where I also use Lombok annotations, such as the @NonNull annotation. When using the quarkus-rest dependency in the application, I get the following warning when running mvn clean verify:
[WARNING] [io.quarkus.arc.processor.BeanArchives] Failed to index lombok.NonNull: Class does not exist in ClassLoader QuarkusClassLoader:Deployment Class Loader: PROD for lombok-nonnull-warning-0.0.1-SNAPSHOT@f4deb35
When removing the quarkus-rest dependency the warning disappears, but for obvious reasons the application no longer works as expected.
Expected behavior
The Lombok annotations should not be indexed, they are annotations and not beans.
Actual behavior
The Lombok annotations are being indexed as if they were beans, resulting in a warning being shown because they cannot be indexed.
Just before the BUILD SUCCESS message, the warning is displayed
When the dependency quarkus-rest is removed from the pom and mvn clean verify is run again, the warning is no longer shown. Of course the rest calls won't work anymore when starting the application and trying to send a call to the endpoint.
Output of uname -a or ver
_No response_
Output of java -version
openjdk 21.0.3 2024-04-16 LTS
OpenJDK Runtime Environment Temurin-21.0.3+9 (build 21.0.3+9-LTS)
OpenJDK 64-Bit Server VM Temurin-21.0.3+9 (build 21.0.3+9-LTS, mixed mode)
Quarkus version or git rev
3.18.1
Build tool (ie. output of mvnw --version or gradlew --version)
Describe the bug
I have a Quarkus application where I also use Lombok annotations, such as the
@NonNull
annotation. When using thequarkus-rest
dependency in the application, I get the following warning when runningmvn clean verify
:When removing the
quarkus-rest
dependency the warning disappears, but for obvious reasons the application no longer works as expected.Expected behavior
The Lombok annotations should not be indexed, they are annotations and not beans.
Actual behavior
The Lombok annotations are being indexed as if they were beans, resulting in a warning being shown because they cannot be indexed.
How to Reproduce?
Reproducer: https://github.com/Wouter684/lombok-nonnull-warning
Steps to reproduce:
mvn clean verify
BUILD SUCCESS
message, the warning is displayedWhen the dependency
quarkus-rest
is removed from the pom andmvn clean verify
is run again, the warning is no longer shown. Of course the rest calls won't work anymore when starting the application and trying to send a call to the endpoint.Output of
uname -a
orver
_No response_
Output of
java -version
Quarkus version or git rev
3.18.1
Build tool (ie. output of
mvnw --version
orgradlew --version
)Additional information
Possibly related issue:
#38506
The text was updated successfully, but these errors were encountered: