aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Holly Cummins (JIRA)" <>
Subject [jira] [Created] (ARIES-850) Build break: Pax tests ignore
Date Tue, 08 May 2012 21:01:50 GMT
Holly Cummins created ARIES-850:

             Summary: Build break: Pax tests ignore
                 Key: ARIES-850
             Project: Aries
          Issue Type: Bug
            Reporter: Holly Cummins
            Assignee: Holly Cummins
            Priority: Critical

Builds have started failing from 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] [equinox/3.5.0] [equinox/3.5.0] [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)-] 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:!default.jspa
For more information on JIRA, see:


View raw message