Skip to content

Consider replacing maven-build-plugins with maven-plugin-development #708

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

Open
sschuberth opened this issue Mar 18, 2025 · 2 comments
Open

Comments

@sschuberth
Copy link
Contributor

The native-maven-plugin sub-project as its own Gradle plugins to build the Maven with Gradle. Maybe this custom functionality could be replaced with https://github.com/gradlex-org/maven-plugin-development which serves the same purpose.

@melix
Copy link
Collaborator

melix commented Mar 18, 2025

Would be good if you could weight in the pros and cons. Because when I started this, the maven plugin development plugin was not mature. In addition, I made particularly sure that we can build projects completely isolated from Maven home and that we can share artifacts between subprojects (there are shared artifacts between the Gradle and Maven NBT plugins). So changing this now is quite risky.

@sschuberth
Copy link
Contributor Author

I see. Obviously, I didn't know about you specific requirement, nor that you were aware of the existing maven-plugin-development plugin. My main "pro" simply is: Reduce your own maintenance burden by reusing an existing solution instead of maintaining your own.

Feel free to just close this if you think a migration is too risky, or if you cannot invest the time to (re-)evaluate the maven-plugin-development plugin.

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

No branches or pull requests

2 participants