Say a Maven project has a cool build plugin configured:
<project>
...
<build>
... extensions etc.
</build>
...
</project>
I want this configuration to be reusable, so that I can run the goals provided by the plugins/extensions in any new project. The above project might exist just so that other projects can reuse the config.
What is the best way to achieve this?
Use a
parent.pom. Deploy thispomto your local repository. Of course you could configureparent.poms for each type of project that you regularly develop in your organisation. Probably amaster.pomwith general values (location of servers, organisation name, general code style...) is a good idea. The project specificpoms would use this as parent.