Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
It's often desirable to create a new mojo by extending an existing mojo and changing its behavior. For example, one might imagine a NetBeans plugin packager that extends from JarMojo and adds extra stuff into the jar.
Today, if I extends a mojo from another plugin, the plugin:descriptor goal fails to create a proper META-INF/maven/plugin.xml — it doesn't list any of the injections that need to happen for the base class.
Attachments
Issue Links
- is depended upon by
-
MPLUGIN-192 Plugin report does not work for MOJOs inheriting from other MOJOs
- Closed
- is duplicated by
-
MPLUGIN-163 Mojo parameters defined in abstract-mojo class not set, when concrete/abstract mojo class in different JARs
- Closed
-
MPLUGIN-164 Extending a Mojo Class and used in a new Mojo Project, parameter fields in the parent mojo are not set, this disables reuse of existing mojo project.
- Closed
- is related to
-
MPLUGIN-189 add java 5 annotations support to mark Mojo sources
- Closed