[
https://jira.codehaus.org/browse/MNG-5218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=286015#comment-286015
]
Ondrej Zizka commented on MNG-5218:
-----------------------------------
Petr, unfortunately, modules are usually not isolated - any time you specify a
<parent>, default <relativePath> is "..", and if it's missing, the build fails.
So reaching parent poms is perfectly valid built-in Maven behavior.
Now let me extend the idea - if you have a module, it's submodule, and
sub-sub-module, then during build of sub-sub-module, maven looks for the
../../pom.xml anyway. So reaching ancestor poms is perfectly valid built-in
Maven behavior.
Therefore, there isn't any problem with allowing to specify a property
containing a full path to that root module of a project (or generally any
ancestor module).
> Allow properties containing ${basedir} to retain same value in sub-modules.
> ---------------------------------------------------------------------------
>
> Key: MNG-5218
> URL: https://jira.codehaus.org/browse/MNG-5218
> Project: Maven 2 & 3
> Issue Type: Improvement
> Reporter: Ondrej Zizka
>
> Currently, if a property contains ${basedir}, it's value in a submodule
> contains submodule's base dir.
> I.e., each submodule has this value different.
> While it's handy for some cases (it allows nice recursive solution for some
> tasks),
> there's no way to have the property with ${basedir} set in the parent module
> and using it unchanged in submodules.
> That's quite crucial for e.g. complex testsuites.
> The current behavior is surely relied on in many projects, so I'd suggest
> something like:
> {code}
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
