[JIRA] (JENKINS-56232) Maven Local Repository is always seen as relative when it should be absolute
Title: Message Title Cyrille Le Clerc updated JENKINS-56232 Jenkins / JENKINS-56232 Maven Local Repository is always seen as relative when it should be absolute Change By: Cyrille Le Clerc Status: In Review Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197795.1550744633000.15091.1559139120347%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56232) Maven Local Repository is always seen as relative when it should be absolute
Title: Message Title Cyrille Le Clerc commented on JENKINS-56232 Re: Maven Local Repository is always seen as relative when it should be absolute Fixed in 3.6.10 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56232) Maven Local Repository is always seen as relative when it should be absolute
Title: Message Title Lasse Lindqvist commented on JENKINS-56232 Re: Maven Local Repository is always seen as relative when it should be absolute The related commit is here: https://github.com/jenkinsci/pipeline-maven-plugin/commit/496eb784e2e9a0fd9e463922f6001848c2d5eda6 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56232) Maven Local Repository is always seen as relative when it should be absolute
Title: Message Title Cyrille Le Clerc updated JENKINS-56232 Jenkins / JENKINS-56232 Maven Local Repository is always seen as relative when it should be absolute Change By: Cyrille Le Clerc Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56232) Maven Local Repository is always seen as relative when it should be absolute
Title: Message Title Cyrille Le Clerc started work on JENKINS-56232 Change By: Cyrille Le Clerc Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56232) Maven Local Repository is always seen as relative when it should be absolute
Title: Message Title Cyrille Le Clerc assigned an issue to Cyrille Le Clerc Jenkins / JENKINS-56232 Maven Local Repository is always seen as relative when it should be absolute Change By: Cyrille Le Clerc Assignee: Alvaro Lobato Cyrille Le Clerc Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56232) Maven Local Repository is always seen as relative when it should be absolute
Title: Message Title
Lasse Lindqvist updated an issue
Jenkins / JENKINS-56232
Maven Local Repository is always seen as relative when it should be absolute
Change By:
Lasse Lindqvist
Using Jenkinsfile withwithMaven(mavenLocalRepo: '${user.home}/.m2/$EXECUTOR_NUMBER/repository')resolves the local repository path to{code:java}-Dmaven.repo.local=/home/jenkins/workspace/somerepository/${user.home}/.m2/2/repository: bad substitution{code}so user.home does not get resolved. This is fine if not possible now. But also usingwithMaven(mavenLocalRepo: '~/.m2/$EXECUTOR_NUMBER/repository')resolves the local repository path to{code:java}-Dmaven.repo.local=/home/jenkins/workspace/somerepository/~/.m2/2/repository : bad substitution {code}UsingwithMaven(mavenLocalRepo: '$WORKSPACE/../../.m2/$EXECUTOR_NUMBER/repository')can be used to escape from a single non-permanent workspace to use a common local repository, but this is not ideal.Concerned code seems to be here:https://github.com/jenkinsci/pipeline-maven-plugin/blob/pipeline-maven-3.6.7/jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/WithMavenStepExecution2.java#L662
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an
[JIRA] (JENKINS-56232) Maven Local Repository is always seen as relative when it should be absolute
Title: Message Title
Lasse Lindqvist created an issue
Jenkins / JENKINS-56232
Maven Local Repository is always seen as relative when it should be absolute
Issue Type:
Bug
Assignee:
Alvaro Lobato
Components:
pipeline-maven-plugin
Created:
2019-02-21 10:23
Environment:
Pipeline Maven Integration Plugin 3.6.7
Priority:
Minor
Reporter:
Lasse Lindqvist
Using Jenkinsfile with withMaven(mavenLocalRepo: '${user.home}/.m2/$EXECUTOR_NUMBER/repository') resolves the local repository path to
-Dmaven.repo.local=/home/jenkins/workspace/somerepository/${user.home}/.m2/2/repository: bad substitution
so user.home does not get resolved. This is fine if not possible now. But also using withMaven(mavenLocalRepo: '~/.m2/$EXECUTOR_NUMBER/repository') resolves the local repository path to
-Dmaven.repo.local=/home/jenkins/workspace/somerepository/~/.m2/2/repository: bad substitution
Using withMaven(mavenLocalRepo: '$WORKSPACE/../../.m2/$EXECUTOR_NUMBER/repository') can be used to escape from a single non-permanent workspace to use a common local repository, but this is not ideal. Concerned code seems to be here:
