Mailing-List: contact camel-user-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: camel-user@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of willem.jiang@gmail.com
 designates 209.85.142.185 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:x-enigmail-version:content-type
         :content-transfer-encoding;
        b=UPZh5yfGmq8z7ho+5Qyi+Cj2WV7zwCM8fBp+iX7Z7IJA5fsHX/rkN9RQcvJ/yLqulk
         /Ww/TDaib/pSdFXvdYQMHed1+G/lS+yksg8rpX2TB16j2EdQBSduR3gdXltMsybORO3g
         jHPcjMKUQXYM/S484LEFZ4gSXGc0mB4tVJtjk=
Message-ID: <4940B215.2030002@gmail.com>
Date: Thu, 11 Dec 2008 14:24:21 +0800
From: Willem Jiang <willem.jiang@gmail.com>
User-Agent: Thunderbird 2.0.0.18 (Windows/20081105)
MIME-Version: 1.0
To: camel-user@activemq.apache.org
Subject: Re: Clean build of 1.5.x does not work
References: <4940AD1B.5020501@gmail.com>
In-Reply-To: <4940AD1B.5020501@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Hi,

org.apache.activemq:activemq-camel:jar:5.2.0 depends on camel 1.5.0.
So we don't have the cycle dependency in camel-jms.

Did you build the camel 1.5.x branch from the root ?

Willem

Ivan Dubrov wrote:
> Hi,
> 
> Currently Apache Camel 1.5.x branch could not be built in a clean
> environment. The build fails with
> 
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
> 
> Missing:
> ----------
> 1) org.apache.camel:camel-jms:jar:1.5.1-SNAPSHOT
> 
>   Try downloading the file manually from the project website.
> 
>   Then, install it using the command:
>       mvn install:install-file -DgroupId=org.apache.camel
> -DartifactId=camel-jms -Dversion=1.5.1-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file
> 
>   Alternatively, if you host your own repository you can deploy the file
> there:
>       mvn deploy:deploy-file -DgroupId=org.apache.camel
> -DartifactId=camel-jms -Dversion=1.5.1-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
> 
>   Path to dependency:
>       1) org.apache.camel:camel-jms:bundle:1.5.1-SNAPSHOT
>       2) org.apache.activemq:activemq-camel:jar:5.2.0
>       3) org.apache.camel:camel-jms:jar:1.5.1-SNAPSHOT
> 
> ----------
> 1 required artifact is missing.
> 
> for artifact:
>   org.apache.camel:camel-jms:bundle:1.5.1-SNAPSHOT
> 
> from the specified remote repositories:
>   apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository),
>   guiceyfruit.release
> (http://guiceyfruit.googlecode.com/svn/repo/releases/),
>   central (http://repo1.maven.org/maven2)
> 
> 
> The workaround is to add an exclusion to the activemq-camel dependency
> in the camel-jms component pom.xml:
> 
> 
>     <dependency>
>       <groupId>org.apache.activemq</groupId>
>       <artifactId>activemq-camel</artifactId>
>       <scope>test</scope>
>       <exclusions>
>         <exclusion>
>           <groupId>org.springframework</groupId>
>           <artifactId>spring</artifactId>
>         </exclusion>
>       </exclusions>
>     </dependency>
> 
> 
> Should I create JIRA issue for this?
>