[JIRA] (JENKINS-56232) Maven Local Repository is always seen as relative when it should be absolute

[lasse.k.lindqv...@gmail.com (JIRA)]

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: 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 email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.