Skip to content
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

Add cabe-maven-plugin #17

Merged
merged 1 commit into from
Dec 21, 2024
Merged

Add cabe-maven-plugin #17

merged 1 commit into from
Dec 21, 2024

Conversation

mk868
Copy link
Contributor

@mk868 mk868 commented Dec 15, 2024

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:

  • the cabe-maven-plugin project added
  • the examples/hello-maven project added
  • Fixed typo in the usage description

Related: #13

@xzel23
Copy link
Owner

xzel23 commented Dec 17, 2024

Thank you, I will have a look in the coming days.

@xzel23 xzel23 merged commit a414cd4 into xzel23:main Dec 21, 2024
@mk868 mk868 deleted the maven-plugin branch December 21, 2024 08:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants