In a project I worked on, we had a similar structure. Translated to Camel artifacts, it would result in the following: - camel pom: Defines generic properties, deployment profiles, plugin management, etc - new camel-oss pom i.e. oss BoM: has top-level 'camel' artifact as parent, defines properties and dependency management of all cots dependency artifacts. Optionally generate and attach a properties configuration containing only the oss versions using maven properties plugin, as I described in my previous mail. - camel-parent: import camel-oss in dependency management, thereby providing all dependency versions to children. Optionally read the properties file attached to the camel-oss pom to also provide the properties to children for whatever reason (limitation: only available after initialize phase).
Cheers, Riccardo On Wed, Aug 21, 2013 at 9:28 PM, James Carman <ja...@carmanconsulting.com>wrote: > With the "bom" approach, you don't use properties to define the > versions (you can but it seems unnecessary IMHO). All of the > dependency versions are defined in the parent pom in the > <dependencyManagement> section, as normal dependencies. > > On Wed, Aug 21, 2013 at 9:55 AM, Jon Anstey <jans...@gmail.com> wrote: > > When using import scope though you only get managed dependencies - no > > properties. Need to inherit a parent pom to get properties. > > > > > > On Wed, Aug 21, 2013 at 11:15 AM, James Strachan > > <james.strac...@gmail.com>wrote: > > > >> I wonder if we should experiment with a BOM file? > >> http://stackoverflow.com/questions/14874966/how-to-use-bom-iwith-maven > >> > >> then the camel project could import the BOM file and other projects > >> could share it too (without having to go the parent pom.xml route). > >> > >> > >> On 15 August 2013 12:26, Claus Ibsen <claus.ib...@gmail.com> wrote: > >> > Hi > >> > > >> > Today we have the parent/pom.xml file which has both all the versions > >> > of the 3rd party JARs we have as dependencies. And also a list of all > >> > the camel components and some other stuff. > >> > > >> > I wonder if we could have all the dependency versions in a single > >> > file, without all the other stuff. > >> > > >> > This would make it easier for ppl to see what are the version changes > >> > between any two Camel versions, but just diff the 2 files? > >> > > >> > And also we could just have such a link in the release notes so we > >> > dont have to manually keep all the versions upgrades in the release > >> > notes up to date as well. > >> > > >> > -- > >> > Claus Ibsen > >> > ----------------- > >> > Red Hat, Inc. > >> > Email: cib...@redhat.com > >> > Twitter: davsclaus > >> > Blog: http://davsclaus.com > >> > Author of Camel in Action: http://www.manning.com/ibsen > >> > >> > >> > >> -- > >> James > >> ------- > >> Red Hat > >> > >> Email: jstra...@redhat.com > >> Web: http://fusesource.com > >> Twitter: jstrachan, fusenews > >> Blog: http://macstrac.blogspot.com/ > >> > >> Open Source Integration > >> > > > > > > > > -- > > Cheers, > > Jon > > --------------- > > Red Hat, Inc. > > Email: jans...@redhat.com > > Web: http://redhat.com > > Twitter: jon_anstey > > Blog: http://janstey.blogspot.com > > Author of Camel in Action: http://manning.com/ibsen >
