|
||||||||
|
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)

I could not think of a use case where one is releasing, using those deprecated properties, and the POM was not under their control to change them. While backwards compat is awesome, it appears to add no benefit and those have been deprecated for a long time. I agree it is low value to support it and a very clear error message(s) is worth the time.