[
https://jira.codehaus.org/browse/MNG-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=350260#comment-350260
]
Paul Benedict edited comment on MNG-1958 at 7/23/14 1:53 PM:
-------------------------------------------------------------
I don't see this as a good idea. There is no guarantee the "root" project even
exists in a sensible location -- it could exist solely in the local repository
and resolved at build time. Surely, you wouldn't want to reference that
location. I think you should keep your builds relative to "basedir" for
portability.
was (Author: paul4christ79):
I don't see this as a good idea. There is no guarantee the "root" project even
exists in a sensible location -- it could exist solely in the local repository
and resolved at build time. Surely, you wouldn't want to reference that
location. I think you should keep your builds relative to ${basedir} for
portability.
> we need a var that always points to the root directory in multi module builds
> -----------------------------------------------------------------------------
>
> Key: MNG-1958
> URL: https://jira.codehaus.org/browse/MNG-1958
> Project: Maven
> Issue Type: Improvement
> Components: Reactor and workspace
> Reporter: Mark Proctor
> Assignee: Jason van Zyl
> Fix For: 3.2.3
>
>
> $\{basedir} always points to the local module. There are cases, when having a
> local relative repository, when it would be usefull to have a var that always
> pointed to the root project, $\{rootdir}.
> In such a case you may want to think of having the names $\{rootdir}
> $\{moduledir}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
