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

Adding extra support in a plugin to handle a deprecated thing adds very little value IMHO. It's a good thing to fix this in your project! But, possibly a better error message would help the user to understand what is going wrong?