[
https://jira.codehaus.org/browse/MNG-5218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=286049#comment-286049
]
Ondrej Zizka commented on MNG-5218:
-----------------------------------
{quote}
... not exactly true - if it's missing, Maven resolves it (using parent GAV)
from repo.
{quote}
IMO it first triesto resolve, if not found, it looks in .. - or the other way
around, I don't know, but try it yourself:
1) Have a module in .../root and a submodule in .../root/foo/bar
2) Set a parent in .../root/foo/bar to the root module
3) Look what will maven print. It's looking for a module in the parent dir.
Nevertheless, we may argue how nice it would be to have totally decoupled
modules, but the reality is that having heavily linked modules is the only way
to craft complex builds in Maven, especially the integration test part.
So the point is:
* There is a real need of passing some module's location to the submodules,
which can't be currently satisfied;
* There is no easy way to implement it - as per John's comment
* A workaound might be implemented as a plugin crawling the dirs upwards.
> 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
