You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Edwin Punzalan (JIRA)" <ji...@codehaus.org> on 2005/09/22 13:09:11 UTC

[jira] Created: (MNG-961) When a mojo is extending another mojo, the parameters of the extending mojo is lost

When a mojo is extending another mojo, the parameters of the extending mojo is lost
-----------------------------------------------------------------------------------

         Key: MNG-961
         URL: http://jira.codehaus.org/browse/MNG-961
     Project: Maven 2
        Type: Bug
  Components: maven-core  
 Reporter: Edwin Punzalan
     Fix For: 2.0-beta-2


When mojoB extends mojoA, looking at plugin.xml from the generated plugin jar:

  -- mojoB inherits all mojo parameters from mojoA, (not a bug)
  -- mojoB's self-declared mojo parameters are missing (this is the bug)

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


[jira] Closed: (MNG-961) When a mojo is extending another mojo, the parameters of the extending mojo is lost

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-961?page=all ]
     
Brett Porter closed MNG-961:
----------------------------

      Assign To: Brett Porter
     Resolution: Cannot Reproduce
    Fix Version:     (was: 2.0-beta-3)

javadoc tag was missing "*"

ie,
/*
 * ...
 */

which isn't parsed.

> When a mojo is extending another mojo, the parameters of the extending mojo is lost
> -----------------------------------------------------------------------------------
>
>          Key: MNG-961
>          URL: http://jira.codehaus.org/browse/MNG-961
>      Project: Maven 2
>         Type: Bug
>   Components: maven-core
>     Reporter: Edwin Punzalan
>     Assignee: Brett Porter

>
>
> When mojoB extends mojoA, looking at plugin.xml from the generated plugin jar:
>   -- mojoB inherits all mojo parameters from mojoA, (not a bug)
>   -- mojoB's self-declared mojo parameters are missing (this is the bug)

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


[jira] Commented: (MNG-961) When a mojo is extending another mojo, the parameters of the extending mojo is lost

Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNG-961?page=comments#action_47215 ] 

John Casey commented on MNG-961:
--------------------------------

Are mojoA and mojoB in different artifacts? This should affect the release plugin and many others as well, if they're in the same artifact. There is an abstract release mojo which declares parameters using javadoc notation, and a derivative prepare release mojo that declares additional parameters...I believe this is still working.

Can you provide more detail?

> When a mojo is extending another mojo, the parameters of the extending mojo is lost
> -----------------------------------------------------------------------------------
>
>          Key: MNG-961
>          URL: http://jira.codehaus.org/browse/MNG-961
>      Project: Maven 2
>         Type: Bug
>   Components: maven-core
>     Reporter: Edwin Punzalan
>      Fix For: 2.0-beta-3

>
>
> When mojoB extends mojoA, looking at plugin.xml from the generated plugin jar:
>   -- mojoB inherits all mojo parameters from mojoA, (not a bug)
>   -- mojoB's self-declared mojo parameters are missing (this is the bug)

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


[jira] Commented: (MNG-961) When a mojo is extending another mojo, the parameters of the extending mojo is lost

Posted by "Edwin Punzalan (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNG-961?page=comments#action_47218 ] 

Edwin Punzalan commented on MNG-961:
------------------------------------

mojoA and mojoB are within one artifact.  You can take a look at the dev-activity mojo of changelog plugin.  The developers parameter of the dev-activity mojo does not get populated with the values from the project pom.  I removed the @parameter annotation for now bec i was able to create a work-around.

> When a mojo is extending another mojo, the parameters of the extending mojo is lost
> -----------------------------------------------------------------------------------
>
>          Key: MNG-961
>          URL: http://jira.codehaus.org/browse/MNG-961
>      Project: Maven 2
>         Type: Bug
>   Components: maven-core
>     Reporter: Edwin Punzalan
>      Fix For: 2.0-beta-3

>
>
> When mojoB extends mojoA, looking at plugin.xml from the generated plugin jar:
>   -- mojoB inherits all mojo parameters from mojoA, (not a bug)
>   -- mojoB's self-declared mojo parameters are missing (this is the bug)

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


[jira] Commented: (MNG-961) When a mojo is extending another mojo, the parameters of the extending mojo is lost

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNG-961?page=comments#action_46915 ] 

Brett Porter commented on MNG-961:
----------------------------------

this is exhibited by the dev/file-activity plugins

> When a mojo is extending another mojo, the parameters of the extending mojo is lost
> -----------------------------------------------------------------------------------
>
>          Key: MNG-961
>          URL: http://jira.codehaus.org/browse/MNG-961
>      Project: Maven 2
>         Type: Bug
>   Components: maven-core
>     Reporter: Edwin Punzalan
>      Fix For: 2.0-beta-2

>
>
> When mojoB extends mojoA, looking at plugin.xml from the generated plugin jar:
>   -- mojoB inherits all mojo parameters from mojoA, (not a bug)
>   -- mojoB's self-declared mojo parameters are missing (this is the bug)

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org