Ok, I may need some help for Jira but I will let you know. Romain.
Le mardi 29 mai 2012, Achim Nierbeck a écrit : > Hi Romain, > > since I didn't see anything similar yet I'm quite interested in how > this would benefit. > So please go ahead and open an issue in jira and attach your patch. > > Thanx and regards, Achim > > 2012/5/29 Romain Gilles <[email protected] <javascript:;>>: > > If you want I can do it for you and send you a patch? > > > > Then you will tell me if you like or not :) > > > > Romain. > > > > > > Le mardi 29 mai 2012, Romain Gilles a écrit : > > > >> In fact when you use the scope import it automatically substitute the > >> current import statement by all the dependencyManagement block of the > >> pointed dependency (here karaf). > >> Therefore as in your super pom you mix child dependency definitions and > >> your third party dependencies then it is more hard to me to specify my > >> dependencies on third parties because I have to take care of yours as > they > >> are imported there is an ordering issue... > >> So if you provide a bom I will get only your child projects in my > >> dependency management and do my dependency management for my third > parties > >> without take care of karaf's third parties. > >> > >> The may issue raise when you try to import 2 project that (i.e. karaf > and > >> another one) that does not have the same dependencies... (I mee in term > of > >> versions). > >> > >> Do you see what I mean? > >> > >> Romain. > >> > >> Le mardi 29 mai 2012, Andreas Pieber a écrit : > >> > >>> Well, basically we provide a "regular super pom" [1] which specifies > >>> most of our parent projects. I'm not quite sure which will be the > >>> advantage of using the type bom over pom? > >>> > >>> Kind regards, > >>> Andreas > >>> > >>> [1] https://github.com/apache/karaf/blob/trunk/pom.xml > >>> > >>> On Tue, May 29, 2012 at 4:07 PM, Romain Gilles < > [email protected] <javascript:;>> > >>> wrote: > >>> > Hi all, > >>> > I think it could be interesting to provide a bom as explained in > maven > >>> > documentation: > >>> > > >>> > http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html > >>> > I'm looking to use dependency management with import scope that > point on > >>> > karaf and It will help me if you are providing a bom with only karaf > >>> > projects in the dependency management and in a separate pom all the > >>> third > >>> > parties. > >>> > > >>> > I use to specify my maven configuration like this and it's works fine > >>> and > >>> > save me time. > >>> > > >>> > Regards, > >>> > > >>> > Romain. > >>> > >> > > > > -- > > Apache Karaf <http://karaf.apache.org/> Committer & PMC > OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> > Committer & Project Lead > OPS4J Pax for Vaadin > <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project > Lead > blog <http://notizblog.nierbeck.de/> >
