Return-Path: 
 <issues-return-109782-apmail-maven-issues-archive=maven.apache.org@maven.apache.org>
X-Original-To: apmail-maven-issues-archive@minotaur.apache.org
Delivered-To: apmail-maven-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 9FDE918F91
	for <apmail-maven-issues-archive@minotaur.apache.org>;
 Wed, 10 Feb 2016 08:55:18 +0000 (UTC)
Received: (qmail 1050 invoked by uid 500); 10 Feb 2016 08:55:18 -0000
Delivered-To: apmail-maven-issues-archive@maven.apache.org
Received: (qmail 923 invoked by uid 500); 10 Feb 2016 08:55:18 -0000
Mailing-List: contact issues-help@maven.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@maven.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@maven.apache.org>
List-Post: <mailto:issues@maven.apache.org>
List-Id: <issues.maven.apache.org>
Reply-To: dev@maven.apache.org
Delivered-To: mailing list issues@maven.apache.org
Received: (qmail 694 invoked by uid 99); 10 Feb 2016 08:55:18 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Feb 2016 08:55:18 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 1AA782C1F5C
	for <issues@maven.apache.org>; Wed, 10 Feb 2016 08:55:18 +0000 (UTC)
Date: Wed, 10 Feb 2016 08:55:18 +0000 (UTC)
From: "Harald Wellmann (JIRA)" <jira@apache.org>
To: issues@maven.apache.org
Message-ID: <JIRA.12938119.1455093639000.13627.1455094518106@Atlassian.JIRA>
In-Reply-To: <JIRA.12938119.1455093639000@Atlassian.JIRA>
References: <JIRA.12938119.1455093639000@Atlassian.JIRA>
 <JIRA.12938119.1455093639478@arcas>
Subject: [jira] [Updated] (MNG-5973) maven.multiModuleProjectDirectory is
 not set
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


     [ https://issues.apache.org/jira/browse/MNG-5973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Harald Wellmann updated MNG-5973:
---------------------------------
    Description: 
h3. Scenario

I'm using $\{maven.multiModuleProjectDirectory\} as part of a property definition in my POM:

{noformat}
<properties>
  <sonar.jacoco.reportPath>$\{maven.multiModuleProjectDirectory\}/target/jacoco.exec</sonar.jacoco.reportPath>
</properties>
{noformat}

(Please ignore the backslashes - I can't find out how to properly escape the braces for JIRA.)

This works find when running Maven from the command line, but when building the same project on Jenkins, the variable is not set, there is no error message, and my build creates a directory called {{/path/to/workspace/$\{maven.multiModuleProjectDirectory\}/target}}.

h3. Analysis

It seems the property {{maven.multiModuleProjectDirectory}} is set in the {{bin/mvn}} shell script and not within the Java application. Since Jenkins does not use the shell script but has a special way of embedding Maven, this explains the effect.

Is there a way to let the Maven Java application compute the property instead of having it passed in? If not, can Maven check that the variable is set and fail fast otherwise?

At the very least, this special behaviour of {{maven.multiModuleProjectDirectory}} should be documented somewhere - up to now, I haven't found any user-visible reference to this property except a line in the release notes at the time it was introduced.

  was:
h3. Scenario

I'm using $\{maven.multiModuleProjectDirectory\} as part of a property definition in my POM:

{noformat}
<properties>
  <sonar.jacoco.reportPath>$\{maven.multiModuleProjectDirectory\}/target/jacoco.exec</sonar.jacoco.reportPath>
</properties>
{noformat}

This works find when running Maven from the command line, but when building the same project on Jenkins, the variable is not set, there is no error message, and my build creates a directory called {{/path/to/workspace/$\{maven.multiModuleProjectDirectory\}/target}}.

h3. Analysis

It seems the property {{maven.multiModuleProjectDirectory}} is set in the {{bin/mvn}} shell script and not within the Java application. Since Jenkins does not use the shell script but has a special way of embedding Maven, this explains the effect.

Is there a way to let the Maven Java application compute the property instead of having it passed in? If not, can Maven check that the variable is set and fail fast otherwise?

At the very least, this special behaviour of {{maven.multiModuleProjectDirectory}} should be documented somewhere - up to now, I haven't found any user-visible reference to this property except a line in the release notes at the time it was introduced.


> maven.multiModuleProjectDirectory is not set
> --------------------------------------------
>
>                 Key: MNG-5973
>                 URL: https://issues.apache.org/jira/browse/MNG-5973
>             Project: Maven
>          Issue Type: Bug
>          Components: Bootstrap & Build
>    Affects Versions: 3.3.9
>            Reporter: Harald Wellmann
>
> h3. Scenario
> I'm using $\{maven.multiModuleProjectDirectory\} as part of a property definition in my POM:
> {noformat}
> <properties>
>   <sonar.jacoco.reportPath>$\{maven.multiModuleProjectDirectory\}/target/jacoco.exec</sonar.jacoco.reportPath>
> </properties>
> {noformat}
> (Please ignore the backslashes - I can't find out how to properly escape the braces for JIRA.)
> This works find when running Maven from the command line, but when building the same project on Jenkins, the variable is not set, there is no error message, and my build creates a directory called {{/path/to/workspace/$\{maven.multiModuleProjectDirectory\}/target}}.
> h3. Analysis
> It seems the property {{maven.multiModuleProjectDirectory}} is set in the {{bin/mvn}} shell script and not within the Java application. Since Jenkins does not use the shell script but has a special way of embedding Maven, this explains the effect.
> Is there a way to let the Maven Java application compute the property instead of having it passed in? If not, can Maven check that the variable is set and fail fast otherwise?
> At the very least, this special behaviour of {{maven.multiModuleProjectDirectory}} should be documented somewhere - up to now, I haven't found any user-visible reference to this property except a line in the release notes at the time it was introduced.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)