On Sat, Aug 17, 2013 at 9:30 AM, Jan Matèrne (jhm) <[email protected]> wrote:
>> > 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>
> ...
>
Yeah only the versions (we already have today in the parent/pom.xml)
in the <properties> should be externalized in its own file. So we have
both the parent/pom.xml and another file with the versions.
(Though not sure how to do that in Maven. But would assume its possible)
eg in parent/pom.xml we have 200+ versions and a bunch of other stuff.
<properties>
<!-- dependency versions -->
<abdera-version>1.1.3</abdera-version>
<!-- Note that activemq dependency is only used for testing! -->
<activemq-version>5.8.0</activemq-version>
<ahc-version>1.7.19</ahc-version>
<ant-bundle-version>1.7.0_6</ant-bundle-version>
--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: [email protected]
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
