[
https://issues.apache.org/jira/browse/SUREFIRE-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17160150#comment-17160150
]
Tibor Digana edited comment on SUREFIRE-1819 at 7/17/20, 7:08 PM:
------------------------------------------------------------------
[~jorsol]
It is under the control of Maven and not the Surefire. If it was this problem
then we would have such problems in the Apache. It is hardly probable case.
Anyway investigate your logs, run the tests with debug level {{mvn -X test}}
and see all the paths for the *classpaths* and you should see the expected
paths pointing to the artifacts in your local repo.
was (Author: tibor17):
[~jorsol]
It is under the control of Maven and not the Surefire. If it was this problem
then we would have such problems in the Apache. It is hardly probable case.
Anyway investigate your lost, run the tests with debug level {{mvn -X test}}
and see all the paths for the *classpaths* and you should see the expected
paths pointing to the artifacts in your local repo.
> MAVEN_OPTS=-Dmaven.repo.local env variable not used when running tests
> ----------------------------------------------------------------------
>
> Key: SUREFIRE-1819
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1819
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Affects Versions: 3.0.0-M5
> Reporter: Jorge Solorzano
> Priority: Major
>
> The local repo configuration using:
>
> {color:#569cd6}MAVEN_OPTS{color}={color:#ce9178}-Dmaven.repo.local=$CI_PROJECT_DIR/.m2/repository{color}
>
> Is not working when running the tests, it downloads all the dependencies
> again in the $HOME directory.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
