[
http://jira.codehaus.org/browse/MNG-3057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey updated MNG-3057:
----------------------------
Fix Version/s: (was: 2.1.0)
2.2.0-M1
Remaining Estimate: 0 minutes
Original Estimate: 0 minutes
We need to do more design work/discussion on this point, since interpolating
versions before deployment must happen selectively, if at all. Additionally, if
the POM has packaging == "pom" it may be an organizational POM, which could
conceivably mean that versions made up of multiple expressions could be meant
to allow those parts to vary in child POMs and be interpreted correctly. If
that were true, then interpolating these versions on deployment of the org POM
would violate that expectation.
This seems related to the practice of using things like ${wagonVersion} in POMs
where multiple related dependencies are specified in a parent POM. In most
cases, these versions are specified in an application's parent POM, which means
they should NOT vary in child POMs...so making them concrete on deployment
could actually be a good thing. But I'm not sure we've got the use cases
covered well enough to make this change.
> properties not expanded in generated POMs when building A/B/C nested projects
> -----------------------------------------------------------------------------
>
> Key: MNG-3057
> URL: http://jira.codehaus.org/browse/MNG-3057
> Project: Maven 2
> Issue Type: Bug
> Components: Inheritance and Interpolation
> Affects Versions: 2.0.7
> Reporter: George Armhold
> Assignee: John Casey
> Fix For: 2.2.0-M1
>
> Attachments: example.tar.gz, generated-poms.tar.gz,
> InstallMojo.java.patch, InstallMojo.java.patch,
> InstallMojo.quoteReplacement.patch, maven-install-parent.patch
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Using Maven version: 2.0.8-SNAPSHOT, svn r547427.
> I checked out and built 2.0.8 because I was interested in Jason van Zyl's
> patch for MNG-2619- "building from the middle pom of a
> (parent,child,grandchild) heirarchy fails". The fix works for the most part,
> but there still seems to be a problem with the poms that get generated during
> the install goal. The poms that get installed into .m2/repository do not
> have properties interpolated. If I run maven like:
> $ mvn install -Dglobal-version=1.0.0
> I get poms with the string "${global-version}" embedded in the resulting poms
> rather than what I specify on the command line (or in settings.xml). The
> build works properly aside from this, and if I do "mvn help:effective-pom"
> the properties are correctly interpolated.
> I've attached a tarfile with an example A/B/C build structure that exhibits
> this behavior, as well as the generated poms.
> Many thanks for your attention.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
