On Mon, Jul 25, 2011 at 9:30 AM, Kasun Gajasinghe <kasu...@gmail.com> wrote: > On Mon, Jul 25, 2011 at 5:34 PM, Damian Bradicich > <dbradic...@sonatype.com> wrote: >> err...pluginManagement section even ;) >> >> Damian >> >> On Mon, Jul 25, 2011 at 8:02 AM, Damian Bradicich >> <dbradic...@sonatype.com>wrote: >> >>> Why not define the pluginDependency section in a parent pom, then each of >>> your projects uses this as a parent, and pulls in all the plugin dep >>> versions defined in it (or overrides in project pom if necessary). Seems >>> that would be simplest solution > > Since these projects are unrelated, they can't be glued together via a > parent pom.
I don't see why not. Consider the following example: http://img.skitch.com/20110727-b3j3j8fk2rg4s2h9exm225skyd.png You just need to have a hierarchy of parent poms. Sure, if you update the top Corporate Super-Pom, you will then need to update the other parent poms that depend on that pom, but this way you can share only the most common stuff, such as plugin versions and generic configurations in the corporate super pom, and then in each of the other parent poms, you get more specific. -- Larry --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
