My strategy is for the corporate POM to contain the fundamental settings like locking down maven plugins and any global legal stuff. Then each department should come up with their own POM under that, then the same for each project.
Cheers, Paul On Tue, Nov 18, 2014 at 12:26 PM, tibor17 <tibo...@lycos.com> wrote: > Hi All, > > I would like to get your help. I am still trying to explain that very large > commercial company (don't mean ASF) should not have one hotspot POM with > only one dependencyManagement (DM). One DM is too weak rule, i would say. > > My arguments are that one DM section will not fit to the needs of 4 > departments having many applications in each and much more Maven modules in > each app. They want to override a dependency versions in each leaf in > dependency section. I am calling this strategy an evil because it would > stick to the dependencies forever and it would be very hard to change > dependencies in all applications at once. > > Would you mind to explain the strategies for creating a successful > corporative hierarchy of POMs? > > My proposal was to build a dependency tree between departments, which is > very easy. Currently there are only two levels in the hierarchy. So I did > this way and created BOM files with dependencyMgmt for internal and > external > artifacts in each level. Those artifacts are not duplicated in the first > and > second level. > Is it good or wrong? > > > > ----- > BR, tibor17 > -- > View this message in context: > http://maven.40175.n5.nabble.com/Only-one-POM-with-dependencyManagement-for-entire-company-tp5814669.html > Sent from the Maven Developers mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
