Hi, > That's essentially what the profile would do. But it should be added > in the corporate parent so that not all projects need to specify it. > Also, and possibly more importantly, i don't want it to be bound to > the build lifecycle for the developers as it adds some significant > build time. It should only be executed on the CI (deploying snapshots > to the repo). So it has to be in a profile not active by default.
Ok. What about the following idea: Add the javadoc and source plugin to build>>plugins in your parent pom, but without any configuration. Create two profiles, one for javadoc and one for source, and configure each plugin in profile > build > pluginManagement > plugin Then you should be able to optionally create javadoc and/or sources together with your normal build artifacts if you activate the corresponding profiles. This is basically what I'm doing in several EAR projects I'm working on with a couple of deployment targets specified in profiles in the parent pom. Regards Thorsten
