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.
This is a initial implementation of the maven plugin - there's still plenty of room for improvement, but the basic assumptions work.
During the implementation, I encountered an issue: the class files produced by the maven-compiler-plugin are placed in the
target/classes
directory, but they are not regenerated when the source files remain unchanged.This caused the cabe-maven-plugin to repeatedly perform instrumentation on the same class files.
To address this, in the example project, I redirected the compilation results to a temporary directory,
target/unprocessed-classes
.This guarantees that the instrumentation is performed only once.
I discovered this approach in AspectJ Maven Plugin.
Changes in this PR:
cabe-maven-plugin
project addedexamples/hello-maven
project addedRelated: #13