Hi Tobias,

Can you try this.
Open the pom.xml on smx3\trunk\samples\bridge and comment the line like
this,  <!--module>bridge-sa-itest</module-->.
Try to rebuild. It was successful on my part.


Regards,
Jay Malaluan



----- Original Message ----
From: Tobias Israel <[EMAIL PROTECTED]>
To: [email protected]
Sent: Friday, June 6, 2008 5:15:18 PM
Subject: Re: Unable to build ServiceMix 3 trunk


Hi Freeman,

did an update but the problem remains when executing mvn
-Dmaven.test.skip=true -Pstep2 install it'll run into that unresolved
activemq dependency.

Regards
Tobias



Freeman Fang wrote:
> 
> Hi Tobias,
> 
> Could you update code and try again.
> 
> The activemq 5.0 need this missing dependency, since a release depend on 
> an snapshot version is not a good practice, activemq 5.1 already fix it.
> Guillaume yesterday already update activemq used in servicemix from 5.0 
> to 5.1 so this problem should gone. [1] track this issue
> 
> [1]http://issues.apache.org/activemq/browse/SM-1381
> 
> Regards
> Freeman
> 
> Tobias Israel wrote:
>> Hi,
>>
>> due to the following missing artifact, I'm not able to build the
>> ServiceMix
>> 3 trunk:
>>
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] BUILD ERROR
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Failed to resolve artifact.
>>
>> Missing:
>> ----------
>> 1) org.apache.activemq:activeio-core:test-jar:tests:3.1-SNAPSHOT
>>
>> ...
>>
>>   Path to dependency:
>>         1)
>> org.apache.servicemix.samples.bridge:bridge-sa-itest:itest:3.3-SNAPSHOT
>>         2) org.apache.activemq:activemq-core:jar:5.0.0
>>         3) org.apache.activemq:activeio-core:test-jar:tests:3.1-SNAPSHOT
>>
>> Are there any known problems with the activemq artifacts referenced?
>>
>> Thanks Tobias
>>  
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Unable-to-build-ServiceMix-3-trunk-tp17685862p17687921.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.


      

Reply via email to