+1 for using the dependency management.
We could make sure the version of bundle in features.xml are same with
the assembled version in this way.
Willem
Guillaume Nodet wrote:
Yeah, i think the problem I've seen may be more a maven problem
related to properties rather than dependency management.
In smx4/features, we build a features descriptor, which is a resource
built using maven filtered resource mechanism.
This file includes references the dependencies versions using properties.
Later in the build, this file is used to create a maven 2 repository
by looking at the artifacts in the features descriptor.
In some builds, I ended up with the wrong version of the artifact in
the repository, but thinking a bit more, it seems to be related to a
dependency having a different value for the property, rather than a
wrong dependency management.
Not sure if I'm very clear, but it seems that the problem comes more
from the features-maven-plugin which does not use maven dependencies
rather than from our poms. I guess the generation of the features
descriptor should use the dependency management from maven too instead
of the more simple resource filtering mechanism ...
On Thu, Sep 18, 2008 at 5:50 PM, Bruce Snyder <[EMAIL PROTECTED]> wrote:
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/
