[
https://jira.codehaus.org/browse/MNG-5218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=286044#comment-286044
]
Petr Kozelka commented on MNG-5218:
-----------------------------------
@Ondrej:
{quote}
default <relativePath> is "..", and if it's missing, the build fails
{quote}
... not exactly true - if it's missing, Maven resolves it (using parent GAV)
from repo.
You are right that people sometimes make their modules non-isolated, because
sometimes it is so comfortable, much more than doing it via extra artifacts...
but it is not the default.
I always discourage this technique, because it removes one good thing I like
about Maven - strictly and simply expressed build prerequisities.
It also has issues in teams where modules have strict responsibility split (I
change a file in my module and break someone else's module, although the output
artifact is unchanged)
> 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
