[
https://jira.codehaus.org/browse/MNG-5218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=285955#comment-285955
]
Petr Kozelka commented on MNG-5218:
-----------------------------------
thanks I didn't know ...
still, I believe that using this can lead to much less usable builds, for the
reasons I wrote before.
One more thing I didn't mention before: your suggestion is well defined when
the parent is reachable via relativePath(s).
But that is not always the case. What should "productDistribution" contain in
this case ? Or should it fail ?
In general, I think that the build works best when every module is standalone
and isolated, in the sense that it does not directly access files belonging to
any other module.
Which is - as I guess - opposite of what your suggestion tries to achieve...
> 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
