Mailing-List: contact dev-help@aries.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aries.apache.org
Date: Thu, 10 May 2012 13:39:48 +0000 (UTC)
From: "Holly Cummins (JIRA)" <jira@apache.org>
To: dev@aries.apache.org
Message-ID: 
 <787186283.49257.1336657188568.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1445660892.41063.1336510910516.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (ARIES-850) Build break: Pax tests ignore
 maven.repo.local settings
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/ARIES-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13272325#comment-13272325 ] 

Holly Cummins commented on ARIES-850:
-------------------------------------

Although I had to work it out by trial and error, rather than from the documentation, it looks like local repositories are actually supported, but they're configured with the org.ops4j.pax.url.mvn.localRepository property, rather than maven.repo.local. I started to implement Andreas's idea and realised that the the maven.repo.local system property isn't actually in the JVMs spawned for the tests. So all I actually had to do was convert the maven.repo.local property to the org.ops4j.pax.url.mvn.localRepository one, and then make sure to propagate that property to all spawned JVMs.
                
> Build break: Pax tests ignore maven.repo.local settings
> -------------------------------------------------------
>
>                 Key: ARIES-850
>                 URL: https://issues.apache.org/jira/browse/ARIES-850
>             Project: Aries
>          Issue Type: Bug
>            Reporter: Holly Cummins
>            Assignee: Holly Cummins
>            Priority: Critical
>
> Builds have started failing from https://builds.apache.org/job/Aries/1442. The following tests are failing:
> org.apache.aries.blueprint.itests.BlueprintContainer2BTCustomizerTest.test [equinox/3.5.0]
> org.apache.aries.blueprint.itests.BlueprintContainerBTCustomizerTest.test [equinox/3.5.1]
> org.apache.aries.samples.blog.itests.JdbcBlogSampleWithEbaTest.test [equinox/3.5.0]
> org.apache.aries.samples.blog.itests.JpaBlogSampleWithEbaTest.test [equinox/3.5.0]
> org.apache.aries.samples.blog.itests.QuiesceBlogSampleWithEbaTest.test [equinox/3.5.0]
> org.apache.aries.sample.twitter.itest.TwitterTest.testTwitter [equinox/3.5.0]
> While this is related to ARIES-489, the move to 1.0.0, that JIRA only exposed an existing problem. 6 tests are failing with errors similar to the following:
> [RMI TCP Connection(1)-67.195.138.8] DEBUG org.ops4j.pax.url.mvn.internal.Connection -   Could not download [Version [1.0.0-SNAPSHOT] from URL [file:/home/jenkins/.m2/repository/org/apache/aries/samples/twitter/org.apache.aries.samples.twitter.eba/1.0.0-SNAPSHOT/org.apache.aries.samples.twitter.eba-1.0.0-SNAPSHOT.eba]]
> The eba has been built, but it's installed in a different maven repo:
> [INFO] Installing /home/jenkins/jenkins-slave/workspace/Aries/aries/samples/twitter/twitter-eba/target/org.apache.aries.samples.twitter.eba-1.0.0-SNAPSHOT.eba to /home/jenkins/jenkins-slave/maven-repositories/0/org/apache/aries/samples/twitter/org.apache.aries.samples.twitter.eba/1.0.0-
> We launch the builds with -B -f /home/jenkins/jenkins-slave/workspace/Aries/aries/pom.xml -Dmaven.repo.local=/home/jenkins/jenkins-slave/maven-repositories/0 -U -cpu -e -B clean install but the maven.repo.local setting is ignored by some of the tests.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira