Hi, +1 about the obvious need to also import the plugins configuration, as well as the dependencies configuration.
I'm interested by your solution. Is it open source, still in use, maintained, Maven 2 and/or 3 compliant? Given the answers you got, here are some additional arguments about the difference between a corporate POM and a third-party BOM, both being needed in some cases. >From a customer project point of view, since there can be only one parent POM, such an import solution is required for reusing the provider project's configuration (ie the third-party BOM: dependencyManagement, pluginManagement, properties; including profiles; maybe also the repositories and pluginRepositories, and optionally the dependencies, plugins and reporting) but in the mean time also using custom corporate configuration (ie the corporate POM: organization, licenses, distributionManagement, ...). The following figure is missing the multi-enterprise aspect with parent/import relationships from outside the company: http://books.sonatype.com/mvnref-book/reference/pom-relationships-sect-pom-best-practice.html#fig-multi-module Regards, Marcos Mendez wrote > So just to give a heads-up on what I've done. I needed the ability to be > able to import more than just dependency management (DM) from a pom. > > USE CASE: Import properties and plugin configurations from a central > location > > Once your company starts using maven and creating all sorts of projects, > this ability becomes necessary. > Managing common changes in properties, plugin versions and configurations > across multiple big projects (diff repos) becomes tedious. > > SOLUTION: Custom build extension > > I created a build extension that merges interesting (to me) items from an > external pom into the maven projects accessible to the extension. > Sort of like having an external parent pom, though not as powerful as > there are only a couple of things that work; mainly what I was interested > in - plugins and their configurations. > > LIMITATIONS: Manual property resolution. Not everything can be merged to > affect the current build. > > For example I have to resolve external properties during my merging > process. They don't seem to resolve properly even when I add them to the > project's properties. > Changes are merged into the project's build plugins. Adding them to plugin > management has no effect, probably because the projects have already been > read. > > Works for me though. I think this should probably be a feature for future > versions of maven. Importing should not just be restricted to DM. -- View this message in context: http://maven.40175.n5.nabble.com/import-plugin-configurations-tp5741927p5774388.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
