After I wrote my response, I realized that I neglected the whole dependency management aspect. +1 with Anders. I am with him. There is no need to lock down dependencies in any corporate/division POM. Those are product concerns which are appropriate to use dependency management. Oh and I use BOMs too :-)
Cheers, Paul On Tue, Nov 18, 2014 at 1:04 PM, Anders Hammar <and...@hammar.net> wrote: > > This I am basically trying to explain them as well. They are newbies and > > the > > funny thing is that they are ignoring us. My proposal was to serve a > > contact > > of Maven PMC experts so that they would pay for new environment, build > > process, POM structures, and CI systems setup but again with no interest. > > :( > > > > Well, reality will hit them sooner or later. Unfortunately, they will by > then have created several anti-patterns which will take time to undo. > > To add to Paul's statement, I never add depMgmt to any kind of parent POM > but pure project/product parent POM. BOMs are the way to go IMHO, as they > will give the flexibility to change without having to release a new parent > POM as well as allowing different projects to use different "platforms" (or > whatever the BOM handle). JBoss EAP even provides their own BOMs which you > could use as-is. For several customers using other (not-so-Maven-friendly) > app servers I've created similar BOMs. > > /Anders > > > > > > > > > ----- > > BR, tibor17 > > -- > > View this message in context: > > > http://maven.40175.n5.nabble.com/Only-one-POM-with-dependencyManagement-for-entire-company-tp5814669p5814678.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 > > > > >