Not sure ...
Maybe it's related to the fact that we use 3.1-SNAPSHOT for other
references and not ${pom.version} or ${project.version} ...
What if you add explicit dependencies on all the poms
(servicemix, servicemix-core, etc...) to specify version instead of
using transitive dependencies ?On 1/12/07, moraleslos <[EMAIL PROTECTED]> wrote:
I'm trying to prepare a release of my code (actually just want to tag it) using maven 2's release:prepare. My build is always failing during the dependency check since my code relies on SMX 3.1 SNAPSHOT-- particularly core, components, services and jbi. I made sure in my poms to only specify a particular snapshot version (so mvn will not think it to be "SNAPSHOT"), e.g. 3.1-incubating-20061219.083008-41, but for some reason its also downloading/depending on 3.1-incubating-SNAPSHOT, and that's where my build fails. Any ideas on how to work around this issue? Below is one of the dependencies specified in my POM which is failing: ************************************************** <dependency> <groupId>org.apache.servicemix</groupId> <artifactId>servicemix-services</artifactId> <version>3.1-incubating-20070112.083011-65</version> <scope>provided</scope> </dependency> ************************************************** Thanks in advance! -los -- View this message in context: http://www.nabble.com/mvn2-smx-snapshot-dependency-suggestion-tf2967061s12049.html#a8302070 Sent from the ServiceMix - User mailing list archive at Nabble.com.
-- Cheers, Guillaume Nodet ------------------------ Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
