[
https://jira.codehaus.org/browse/MPLUGIN-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph Walton closed MPLUGIN-211.
---------------------------------
Resolution: Not A Bug
Apologies for the mistake - this was a migration from Anno Mojo to
maven-plugin-tools-annotations, not from Javadoc. There's no need to duplicate
their behaviour.
> @Mojo annotations aren't inherited
> ----------------------------------
>
> Key: MPLUGIN-211
> URL: https://jira.codehaus.org/browse/MPLUGIN-211
> Project: Maven 2.x Plugin Tools
> Issue Type: Bug
> Components: maven-plugin-tools-annotations
> Affects Versions: 3.0
> Reporter: Joseph Walton
> Priority: Trivial
>
> We have a project where a mojo defined in one plugin module is inherited from
> in another. With Javadoc-style markup, the child class is also declared as an
> mojo. With @Mojo, the child class needs to re-declare @Mojo in order to be
> included in the plugin definition.
> I'm reporting this as 'trivial' priority. I've fixed it by copying those
> @Mojo annotations across.
> I wouldn't have a problem with WONTFIXing this. I think the new behaviour is
> clearer, and I'm not convinced that the previous behaviour was intentional or
> desirable. However, it is still a change.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
