[
http://jira.codehaus.org/browse/MNG-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=130377#action_130377
]
Marco Lessard commented on MNG-2756:
------------------------------------
Using maven 2.0.8, we still have the problem with the <parent> tag.
<parent>
<groupId>com.mycompany.odp</groupId>
<artifactId>ocs-core</artifactId>
<version>${ocs.release.version}</version>
</parent>
Properties in "project.parent.version" do NOT get substituted but properties in
"project.version" do.
We are on the process of migrating our 900 artifacts project to maven. Most of
those artifacts will share the same release version and inherit from the same
parent, so it is out of question to do a "search and replace".
Looks like a substitution bug to me.
For the moment, it is a show stopper for us that blocks the migration of our
900 artifacts.
> parent resolution is done first before property interpolation
> -------------------------------------------------------------
>
> Key: MNG-2756
> URL: http://jira.codehaus.org/browse/MNG-2756
> Project: Maven 2
> Issue Type: Bug
> Components: Inheritance and Interpolation
> Affects Versions: 2.0.x, 2.1
> Reporter: Franz Allan Valencia See
> Fix For: 2.0.x
>
> Attachments: parent-filtering.zip
>
>
> Possible problems
> * using properties in the parent tag
> * using proeprties in the repositories tag with the parent being unknown
> except to that repo
> Attach is a sample project whose child project does not get built.
--
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
