[ https://issues.apache.org/jira/browse/MWRAPPER-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17862689#comment-17862689 ]
RĂ©da Housni Alaoui edited comment on MWRAPPER-133 at 7/3/24 8:07 AM: --------------------------------------------------------------------- For the record, the workaround described in https://issues.apache.org/jira/browse/MWRAPPER-133?focusedCommentId=17845700&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17845700 generated a new issue with the latest Maven wrapper: {{--batch-mode}} flag (added by default by pipeline maven integration in {{MAVEN_CONFIG}} ) ends up in {{MAVEN_ARGS}}, which makes the build fail. was (Author: ralaoui): For the record, the workaround described in https://issues.apache.org/jira/browse/MWRAPPER-133?focusedCommentId=17845700&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17845700 generated a new issue with the latest Maven wrapper: {{--batch-mode}} flag ends up in {{MAVEN_ARGS}}, which makes the build fail. > MAVEN_CONFIG populated by Jenkins Maven Pipeline is no longer read, > ------------------------------------------------------------------- > > Key: MWRAPPER-133 > URL: https://issues.apache.org/jira/browse/MWRAPPER-133 > Project: Maven Wrapper > Issue Type: Bug > Components: Maven Wrapper Scripts > Affects Versions: 3.3.0 > Reporter: Rocher Suchard > Priority: Major > > Hello, > Due to an update by Renovate in one of our project, I've seen some error > related to internal dependencies not being picked up by Maven : while we were > using a custom settings, it did not use it and was using Central instead of > our Artifactory. > Upon analysis, it seems that Maven Pipeline define a MAVEN_CONFIG > environnement variable here : > https://github.com/jenkinsci/pipeline-maven-plugin/blob/8cfaff9c021c971d19e5469c553a86d954c05387/pipeline-maven/src/main/java/org/jenkinsci/plugins/pipeline/maven/WithMavenStepExecution2.java#L400 > The MAVEN_CONFIG variables was used in our Maven 3.2.0 Wrapper script and > I've played around with the default value and type: > {code:bash} > $ mvn wrapper:3.3.0:wrapper -Dmaven=3.9.6 > # use scripts-only > $ grep -r MAVEN_CONFIG mvnw mvnw.cmd .mvn/ > # nothing > $ mvn wrapper:3.2.0:wrapper -Dmaven=3.9.6 > # use bin > $ grep -r MAVEN_CONFIG mvnw mvnw.cmd .mvn/ > mvnw:MAVEN_CMD_LINE_ARGS="$MAVEN_CONFIG $*" > mvnw: ${WRAPPER_LAUNCHER} $MAVEN_CONFIG "$@" > mvnw.cmd: %WRAPPER_LAUNCHER% %MAVEN_CONFIG% % > $ mvn wrapper:3.3.0:wrapper -Dmaven=3.9.6 -Dtype=bin > ... > [INFO] Unpacked bin type wrapper distribution > org.apache.maven.wrapper:maven-wrapper-distribution:zip:bin:3.3.0 > [INFO] Configuring .mvn/wrapper/maven-wrapper.properties to use Maven 3.9.6 > and download from https://repo.maven.apache.org/maven2 > ... > $ grep -r MAVEN_CONFIG mvnw mvnw.cmd .mvn/ > mvnw:MAVEN_CMD_LINE_ARGS="$MAVEN_CONFIG $*" > mvnw: ${WRAPPER_LAUNCHER} $MAVEN_CONFIG "$@" > mvnw.cmd: %WRAPPER_LAUNCHER% %MAVEN_CONFIG% %* > {code} > Is there a way to do the same for the script-only if this is to be the > default ? -- This message was sent by Atlassian Jira (v8.20.10#820010)