[JIRA] (JENKINS-42179) withMaven doesn't discover the released artifacts when executing "mvn release"

[cleclerc@cloudbees.com (JIRA)]

Cyrille Le Clerc created an issue

Jenkins / JENKINS-42179 withMaven doesn't discover the released artifacts when executing "mvn release" Issue Type: Bug Assignee: Cyrille Le Clerc Components: pipeline-maven-plugin Created: 2017/Feb/19 5:12 PM Priority: Minor Reporter: Cyrille Le Clerc "withMaven()" doesn't discover the released artifacts generated by "mvn release:prepare release:perform". It's because the Maven Event Spy is passed by a "-Dmaven.ext.class.path=" parameter of the "mvn" invocation and the "sub" call of "mvn" doesn't inherit of the variable. We should instead pass "-Dmaven.ext.class.path=" and "-Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder=..." using the "JAVA_TOOL_OPTIONS" environment variable. Add Comment

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)

[scm_issue_link@java.net (JIRA)]

SCM/JIRA link daemon commented on JENKINS-42179

Re: withMaven doesn't discover the released artifacts when executing "mvn release" Code changed in jenkins User: Alvaro Lobato Path: jenkins-plugin/pom.xml jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/WithMavenStepExecution.java http://jenkins-ci.org/commit/pipeline-maven-plugin/50291c9c7878f5899065731c14d446f7e1d7546c Log: Merge pull request #19 from cyrille-leclerc/JENKINS-42179 JENKINS-42179 use the JAVA_TOOL_OPTIONS environment variable to pass `-Dmaven.ext.class.path` Compare: https://github.com/jenkinsci/pipeline-maven-plugin/compare/fa0f35294292...50291c9c7878

Add Comment

[scm_issue_link@java.net (JIRA)]

SCM/JIRA link daemon commented on JENKINS-42179

Re: withMaven doesn't discover the released artifacts when executing "mvn release"

Code changed in jenkins User: Cyrille Le Clerc Path: jenkins-plugin/pom.xml jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/WithMavenStepExecution.java http://jenkins-ci.org/commit/pipeline-maven-plugin/3952f7fb1071a4dd5025dab853ac54de56dc7166 Log:

JENKINS-42179 use the JAVA_TOOL_OPTIONS environment variable to pass `-Dmaven.ext.class.path`

Add Comment

[cleclerc@cloudbees.com (JIRA)]

Cyrille Le Clerc resolved as Fixed

Jenkins / JENKINS-42179

withMaven doesn't discover the released artifacts when executing "mvn release"

Change By: Cyrille Le Clerc Status: Open Resolved Resolution: Fixed

Add Comment

[cleclerc@cloudbees.com (JIRA)]

Cyrille Le Clerc commented on JENKINS-42179

Re: withMaven doesn't discover the released artifacts when executing "mvn release" The JVMs started in a withMaven() {...} wrapping step are now emitting an unpleasant "Picked up JAVA_TOOL_OPTIONS" but the problem is fixed for the moment. We could discuss with the Maven community to find a better solution. [INFO] Picked up JAVA_TOOL_OPTIONS: -Dmaven.ext.class.path="/home/ubuntu/jenkins-aws-home/workspace/plugins/pipeline-maven-plugin/multi-module-maven-project/release@tmp/withMavenec593a03/pipeline-maven-spy.jar" -Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder="/home/ubuntu/jenkins-aws-home/workspace/plugins/pipeline-maven-plugin/multi-module-maven-project/release@tmp/withMavenec593a03"

Add Comment

[cleclerc@cloudbees.com (JIRA)]

Cyrille Le Clerc edited a comment on JENKINS-42179

Re: withMaven doesn't discover the released artifacts when executing "mvn release"

The JVMs started in a "{{withMaven(){...\}}}" wrapping step are now emitting an unpleasant "{{Picked up JAVA_TOOL_OPTIONS}}" but the problem is fixed for the moment. We could discuss with the Maven community to find a better solution.

{noformat} [INFO] Picked up JAVA_TOOL_OPTIONS: -Dmaven.ext.class.path="/home/ubuntu/jenkins-aws-home/workspace/plugins/pipeline-maven-plugin/multi-module-maven-project/release@tmp/withMavenec593a03/pipeline-maven-spy.jar" -Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder="/home/ubuntu/jenkins-aws-home/workspace/plugins/pipeline-maven-plugin/multi-module-maven-project/release@tmp/withMavenec593a03" {noformat}

Add Comment

[cleclerc@cloudbees.com (JIRA)]

[cleclerc@cloudbees.com (JIRA)]

[robin.jansohn@zf.com (JIRA)]

Robin Jansohn commented on JENKINS-42179

Re: withMaven doesn't discover the released artifacts when executing "mvn release"

Is there any way to suppress this output? One of our tests starts a separate java process and expects no output to appear...

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[robin.jansohn@zf.com (JIRA)]

Robin Jansohn commented on JENKINS-42179

Re: withMaven doesn't discover the released artifacts when executing "mvn release"

Is there any way to suppress this output? One of our tests starts a separate java process and expects no output to appear...

EDIT: I fixed it by explicitly setting JAVA_TOOL_OPTIONS to empty value for that separate process.

Add Comment

[robin.jansohn@zf.com (JIRA)]

Robin Jansohn updated an issue

Jenkins / JENKINS-42179

withMaven doesn't discover the released artifacts when executing "mvn release"

Change By: Robin Jansohn Comment:

Is there any way to suppress this output? One of our tests starts a separate java process and expects no output to appear...

Add Comment

[cleclerc@cloudbees.com (JIRA)]

Cyrille Le Clerc commented on JENKINS-42179

Re: withMaven doesn't discover the released artifacts when executing "mvn release" Robin Jansohn thanks for the update. We currently don't see a solution to operate without using JAVA_TOOLS_OPTIONS to pass parameters to forked maven processes (e.g. when performing "mvn release:prepare release:perform")

Add Comment