You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Kohsuke Kawaguchi (JIRA)" <ji...@codehaus.org> on 2007/01/23 02:41:16 UTC

[jira] Created: (MNG-2789) Inter-plugin Mojo inheritance

Inter-plugin Mojo inheritance
-----------------------------

                 Key: MNG-2789
                 URL: http://jira.codehaus.org/browse/MNG-2789
             Project: Maven 2
          Issue Type: Improvement
          Components: Plugin Creation Tools
            Reporter: Kohsuke Kawaguchi


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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (MNG-2789) Inter-plugin Mojo inheritance

Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason van Zyl updated MNG-2789:
-------------------------------

    Fix Version/s:     (was: Reviewed Pending Version Assignment)
                   2.1.x

> Inter-plugin Mojo inheritance
> -----------------------------
>
>                 Key: MNG-2789
>                 URL: http://jira.codehaus.org/browse/MNG-2789
>             Project: Maven 2
>          Issue Type: Improvement
>          Components: Plugin Creation Tools
>            Reporter: Kohsuke Kawaguchi
>             Fix For: 2.1.x
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Moved: (MPLUGIN-56) Inter-plugin Mojo inheritance

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MPLUGIN-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter moved MNG-2789 to MPLUGIN-56:
------------------------------------------

    Fix Version/s:     (was: 2.1)
      Component/s:     (was: Plugin Creation Tools)
              Key: MPLUGIN-56  (was: MNG-2789)
          Project: Maven 2.x Plugin Tools  (was: Maven 2)

> Inter-plugin Mojo inheritance
> -----------------------------
>
>                 Key: MPLUGIN-56
>                 URL: http://jira.codehaus.org/browse/MPLUGIN-56
>             Project: Maven 2.x Plugin Tools
>          Issue Type: Improvement
>            Reporter: Kohsuke Kawaguchi
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (MPLUGIN-56) Inter-plugin Mojo inheritance

Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MPLUGIN-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144537#action_144537 ] 

Benjamin Bentmann commented on MPLUGIN-56:
------------------------------------------

Vincent, this issue is about inheritance between mojos from *different* plugins which is not possibly right now as it would require to scan the sources of another plugin's dependencies to get all the javadoc annotations of the inherited stuff.

> Inter-plugin Mojo inheritance
> -----------------------------
>
>                 Key: MPLUGIN-56
>                 URL: http://jira.codehaus.org/browse/MPLUGIN-56
>             Project: Maven 2.x Plugin Tools
>          Issue Type: Improvement
>            Reporter: Kohsuke Kawaguchi
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (MPLUGIN-56) Inter-plugin Mojo inheritance

Posted by "Benson Margulies (JIRA)" <ji...@codehaus.org>.
    [ https://jira.codehaus.org/browse/MPLUGIN-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=277649#comment-277649 ] 

Benson Margulies commented on MPLUGIN-56:
-----------------------------------------

How about a release of qdox?

> Inter-plugin Mojo inheritance
> -----------------------------
>
>                 Key: MPLUGIN-56
>                 URL: https://jira.codehaus.org/browse/MPLUGIN-56
>             Project: Maven 2.x Plugin Tools
>          Issue Type: Improvement
>            Reporter: Kohsuke Kawaguchi
>
> 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.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (MPLUGIN-56) Inter-plugin Mojo inheritance

Posted by "Vincent Siveton (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MPLUGIN-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144534#action_144534 ] 

Vincent Siveton commented on MPLUGIN-56:
----------------------------------------

I think this issue was already fix somewhere... See generated documentation.

http://maven.apache.org/plugins/maven-javadoc-plugin-2.5/javadoc-mojo.html 
{noformat}
    * Requires a Maven 2.0 project to be executed.
    * Requires dependency resolution of artifacts in scope: compile.
    * Since version: 2.0.
    * Invokes the execution of the lifecycle phase generate-sources prior to executing itself.
{noformat}

http://maven.apache.org/plugins/maven-javadoc-plugin-2.5/aggregate-mojo.html
{noformat}
    * Requires a Maven 2.0 project to be executed.
    * Executes as an aggregator plugin.
    * Requires dependency resolution of artifacts in scope: compile.
    * Since version: 2.5.
    * Invokes the execution of the lifecycle phase generate-sources prior to executing itself.
{noformat}

> Inter-plugin Mojo inheritance
> -----------------------------
>
>                 Key: MPLUGIN-56
>                 URL: http://jira.codehaus.org/browse/MPLUGIN-56
>             Project: Maven 2.x Plugin Tools
>          Issue Type: Improvement
>            Reporter: Kohsuke Kawaguchi
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (MPLUGIN-56) Inter-plugin Mojo inheritance

Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
    [ https://jira.codehaus.org/browse/MPLUGIN-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=277703#comment-277703 ] 

Robert Scholte commented on MPLUGIN-56:
---------------------------------------

I'm almost done with my preparations for QDox-2.0-alpha's. This can't be fixed with QDox-1.x, because I of its loadmechanism, which was rewritten for 2.0.
I''ll pick us this issue once QDox-2.0 is released.

> Inter-plugin Mojo inheritance
> -----------------------------
>
>                 Key: MPLUGIN-56
>                 URL: https://jira.codehaus.org/browse/MPLUGIN-56
>             Project: Maven 2.x Plugin Tools
>          Issue Type: Improvement
>            Reporter: Kohsuke Kawaguchi
>
> 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.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira