On Thu, Sep 18, 2008 at 9:33 AM, Aaron Mulder
<[EMAIL PROTECTED]> wrote:
> But I've also seen with the properties used with dependencyManagement
> -- particularly with something like Spring or Camel that has tons of
> JARs:
>
> <properties>
> <spring.version>2.5.5</spring.version>
> </properties>
> ...
> <dependencyManagement>
> <dependency>
> <artifactId>spring-foo</artifactId>
> <version>${spring.version}</version>
> ...
> <dependency>
> <artifactId>spring-bar</artifactId>
> <version>${spring.version}</version>
> ...
>
> Does that kind of usage have the same issue you described where if
> some other dependency declares "spring.version" to be 2.5.3 then there
> would be some confusion over which version to use?
I guess I should have been more clear in my reply. What Aaron is
stating above was my assumption. That is, continue to use the
properties but also use the dependencyManagement element in the pom.
Bruce
--
perl -e 'print unpack("u30","D0G)[EMAIL
PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache ActiveMQ - http://activemq.org/
Apache Camel - http://activemq.org/camel/
Apache ServiceMix - http://servicemix.org/
Blog: http://bruceblog.org/
