[mojo-dev] [jira] (MVERSIONS-200) When child poms refer to each other using parent versions, using versions:set leads to a null pointer exception

[Gareth Moorst (JIRA)]

Gareth Moorst commented on MVERSIONS-200 When child poms refer to each other using parent versions, using versions:set leads to a null pointer exception Thanks for the links Jeff. Neither of those pages say anything about ${parent.xxx} properties being deprecated. In fact, the wiki link says To access the parent version: ${parent.version} so it seems that parent.xxx properties are still supported. From the Maven 3 build log, this isn't the case, but it would be nice if it was made clear somewhere. The point being, when using Maven 2 (we have no choice about this) how do you tell which properties are ok, and which ones constitute bad behaviour?

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira

--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email