|
||||||||
|
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 |
||||||||
- [mojo-dev] [jira] (MVERSIONS-200) When child poms ... Gareth Moorst (JIRA)
- [mojo-dev] [jira] (MVERSIONS-200) When child ... Stephen Connolly (JIRA)
- [mojo-dev] [jira] (MVERSIONS-200) When child ... Stephen Connolly (JIRA)
- [mojo-dev] [jira] (MVERSIONS-200) When child ... Stephen Connolly (JIRA)
- [mojo-dev] [jira] (MVERSIONS-200) When child ... Stephen Connolly (JIRA)
- [mojo-dev] [jira] (MVERSIONS-200) When child ... Anders Hammar (JIRA)
- [mojo-dev] [jira] (MVERSIONS-200) When child ... Jeff Jensen (JIRA)
- [mojo-dev] [jira] (MVERSIONS-200) When child ... Gareth Moorst (JIRA)
- [mojo-dev] [jira] (MVERSIONS-200) When child ... Jeff Jensen (JIRA)
- [mojo-dev] [jira] (MVERSIONS-200) When child ... Gareth Moorst (JIRA)

So the work-around is to use the correct properties.
I am unsure whether to add support for those deprecated properties into the plugin, as I don't particularly want to encourage bad behaviour. I will canvas the rest of the Mojo & Maven developers for their opinions