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

Konrad Windszus commented on MASFRES-70:
----------------------------------------

It is currently unclear why the System property {{maven.repo.local}} being set 
in 
https://github.com/apache/maven-apache-resources/blob/5eab384b10e68b9764c6c66fa4c1672fbf49a94a/source-release/pom.xml#L140-L141
 is not considered, but instead the Jenkins internally used value is used 
(https://plugins.jenkins.io/pipeline-maven/#plugin-content-usage). Jenkins 
leverages the Maven CLI option:

bq. By using this option, Jenkins will tell Maven to use a custom path for the 
build as the local Maven repository by using -Dmaven.repo.local

This seems to take precedence over the system properties set for the 
maven-failsafe-plugin.

> ITs in ASF Jenkins use wrong artifact for testing
> -------------------------------------------------
>
>                 Key: MASFRES-70
>                 URL: https://issues.apache.org/jira/browse/MASFRES-70
>             Project: Apache Maven Resource Bundles
>          Issue Type: Improvement
>          Components: apache-source-release-assembly-descriptor
>    Affects Versions: apache-resources 1.5
>            Reporter: Konrad Windszus
>            Priority: Major
>
> In module {{source-release}} the ITs incorrectly use the workspace repository 
> location (.repository) instead of using the prepopulated repository 
> (containing the previously built artifact) from target/it-repo.
> This only happens in ASF Jenkins (while GitHub Actions use the correct local 
> repo in ITs).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to