[
https://jira.codehaus.org/browse/MNG-5218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=286029#comment-286029
]
John Casey commented on MNG-5218:
---------------------------------
The problem is that it would require complete overhaul of the way maven
computes the effective pom for use in a module build. Model inheritance is
collapsed, then interpolation takes place. So, this notion of resolve == here
vs. resolve == everytime would have no meaning. "Here" is literally the module
directory that inherits it.
What you might be talking about is traversing the parent structure that's on
disk to the lowest (highest) level, and setting a property to that directory.
I'm not sure it's really necessary to bake this into the core, though...you
could accomplish this via something like the buildnumber-maven-plugin.
> 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
