Consider replacing `maven-build-plugins` with `maven-plugin-development`

[sschuberth]

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]

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]

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.