Hey Raymond,
The STS (and other OSGi tests in general) should use Maven Local repository, it
is propagated
by maven-surefire-plugin (snippet below for sts-itests/pom.xml):
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<configuration>
<systemPropertyVariables>
<maven.repo.local>${maven.repo.local}</maven.repo.local>
</systemPropertyVariables>
</configuration>
</plugin>
You could also see the maven.repo.local is being set during the build:
21:12:22 [CXF-JDK11-PR] $ /home/jenkins/tools/maven/latest3/bin/mvn -f
pom.xml
-Dmaven.repo.local=/home/jenkins/jenkins-agent/workspace/CXF/CXF-JDK11-PR/.repository
install -Djava.awt.headless=true -fae -B
So it seems like tests may fail for different reasons, will try to look shortly
why.
Thanks.
Best Regards,
Andriy Redko
RA> Additionally, I can run the same tests locally without failure.
RA> On Sat, May 7, 2022 at 9:51 PM Raymond Augé <[email protected]>
RA> wrote:
>> Hey everyone,
>> I'm experiencing a failure in a test [1] which I cannot explain.
>> I'm wondering if it's possible that PaxExam is somehow loading the karaf
>> feature in question from the Apache snapshot repo instead of the locally
>> built one? If you look in the PR the Karaf feature contains the dependency
>> the test claims is missing.
>> thanks for your help,
>> Ray
>> [1] https://ci-builds.apache.org/job/CXF/job/CXF-JDK11-PR/104/testReport/
