camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Matèrne (jhm) <apa...@materne.de>
Subject AW: [IDEA] - Having a parent maven pom.xml for only the dependency versions
Date Sat, 17 Aug 2013 07:30:47 GMT
> > What do you propose the "list of all the camel components and some
> > other stuff" should go?
> >
> 
> They should stay where they are. Its just all the versions that gets
> moved into its own file, so the file ONLY has the versions. And that
> makes the diff much easier.

Do you mean to externalize the complete dependency (groupid, artefactid,
version) or just the version (and using properties in the pom)?

Jan

<pom>
   <dependencies>
       <includeDependencies/>
   </dependencies>
</pom>

<pom>
   <loadVersionProperties/>
   <dependencies>
       <dependency>
           <groupdId>junit</groupId>
           <artefactId>junit</artefactId>
           <version>${dependency.junit.version}</version>
...


Mime
View raw message