We also have to check if the getLocalRepo() method is correctly used in
all itests.
This method checks if the maven.repo.local system property is set and
uses it, else it falls back to org.ops4j.pax.url.mvn.localRepository.
AFAIR, Jenkins profile provides the maven.repo.local system property to
point on its local repository (where the SNAPSHOTs have been built).
Regards
JB
On 06/13/2014 02:06 PM, Jean-Baptiste Onofré wrote:
Hi Christian,
I think the problem is in testunit 2.0.0-SNAPSHOT. It seems that we
remove some SNAPSHOTs resolution/injection of mavenBundle().
It allows to have the itests running with all SNAPSHOTs dependencies.
I think it should be fixed in testunit 2.0.0-SNAPSHOT.
Regards
JB
On 06/13/2014 10:39 AM, Christian Schneider wrote:
The normal aries build as well as the deploy build seem to be stable
again.
See
https://builds.apache.org/view/A-D/view/Aries2/job/Aries/
The build with snapshot dependencies seems to continually fail.
https://builds.apache.org/view/A-D/view/Aries2/job/AriesWithSnapshotDependencies/
The build fails during the application integration tests with a compile
error.
Unfortunately I do not fully understand what the failing build does
exactly. Can someone explain how this build works and perhaps give some
advice what is going wrong at the moment?
I would like to do a build on my own system that replicates the same
errors but have no idea how to do this.
Maybe this build simply does not work anymore with the new integration
tests as I now use .versionAsInProject in pax exam while I think the old
tests used a different mechanism to determine the version of
dependencies.
Christian
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
