karaf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Romain Gilles <romain.gil...@gmail.com>
Subject Re: Karaf should provide a maven BOM
Date Tue, 29 May 2012 16:03:28 GMT
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

Do you see what I mean?


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 <romain.gilles@gmail.com<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.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message