XPlugin Issue with Maven Build Cache Extension in IntelliJ #358
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Following this checklist to help us incorporate your
contribution quickly and easily:
Note that commits might be squashed by a maintainer on merge.
This may not always be possible but is a best-practice.
mvn verify
to make sure basic checks pass.A more thorough check will be performed on your pull request automatically.
mvn -Prun-its verify
).If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.
ErrorProne Plugin Issue with Maven Build Cache Extension in IntelliJ
As part of a project, the Javac ErrorProne plugin is used. Its configuration is defined in the root
pom.xml
.Occasionally, when launching the Spring Boot application, the following error appears:
java: plug-in not found: ErrorProne
This issue occurs when the module does not have the required Maven processors configured, even though the
-Xplugin:ErrorProne
option is specified.After investigation, the issue appears to be related to the maven-build-cache-extension. A minimal project was created to reproduce the problem:
👉 https://github.com/marcosemiao/Intellij-project-test
Steps to Reproduce
mvn install
in IntelliJ.Build > Execution > Deployment > Compiler > Annotation Processors
Observed Behavior
When working correctly, modules are associated with the profile:
"Annotation profile for intellij-project-test"
Randomly, one or more modules are associated with the profile:
"Maven default annotation processors profile", which causes the issue.
A stacktrace may appear when the issue is triggered :