Return-Path: 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 839491855B for ; Wed, 10 Feb 2016 11:21:19 +0000 (UTC) Received: (qmail 12505 invoked by uid 500); 10 Feb 2016 11:21:18 -0000 Delivered-To: apmail-maven-issues-archive@maven.apache.org Received: (qmail 12435 invoked by uid 500); 10 Feb 2016 11:21:18 -0000 Mailing-List: contact issues-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@maven.apache.org Delivered-To: mailing list issues@maven.apache.org Received: (qmail 12349 invoked by uid 99); 10 Feb 2016 11:21: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 11:21:18 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 1C7D42C14F6 for ; Wed, 10 Feb 2016 11:21:18 +0000 (UTC) Date: Wed, 10 Feb 2016 11:21:18 +0000 (UTC) From: "Michael Osipov (JIRA)" To: issues@maven.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (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:comment-tabpanel&focusedCommentId=15140650#comment-15140650 ] Michael Osipov commented on MNG-5973: ------------------------------------- I am highly in favor moving discovery logic into maven itself, let the booter script be dumb. I would avoid duplicate fork Unix and Windows. > 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} > > $\{maven.multiModuleProjectDirectory\}/target/jacoco.exec > > {noformat} > (Please ignore the backslashes - I can't find out how to properly escape the braces for JIRA.) > This works fine 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)