You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dennis Lundberg (JIRA)" <ji...@codehaus.org> on 2008/07/07 12:32:27 UTC

[jira] Created: (MPLUGIN-124) The generated documentation for a Mojo should show if it is a build plugin or a reporting plugin

The generated documentation for a Mojo should show if it is a build plugin or a reporting plugin
------------------------------------------------------------------------------------------------

                 Key: MPLUGIN-124
                 URL: http://jira.codehaus.org/browse/MPLUGIN-124
             Project: Maven 2.x Plugin Tools
          Issue Type: Improvement
          Components: Plugin Plugin
    Affects Versions: 2.4.2
            Reporter: Dennis Lundberg


This came up on the user list:

{quote}
Isn't strange to have to define the maven-site-plugin inside <build> just to
specify the version ?
Why maven 2 can't take into account the version declare inside <reporting> ?
It seems to more natural isn't it ?
{quote}

http://www.nabble.com/Re%3A--ANN--Maven-Site-Plugin-2.0-beta-7-Released-p18311450.html

-- 
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] Closed: (MPLUGIN-124) The generated documentation for a Mojo should show if it is a build plugin or a reporting plugin

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

Benson Margulies closed MPLUGIN-124.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.9

Added @requiresReport to the output, I think that about does this.

> The generated documentation for a Mojo should show if it is a build plugin or a reporting plugin
> ------------------------------------------------------------------------------------------------
>
>                 Key: MPLUGIN-124
>                 URL: https://jira.codehaus.org/browse/MPLUGIN-124
>             Project: Maven 2.x Plugin Tools
>          Issue Type: Improvement
>          Components: Plugin Plugin
>    Affects Versions: 2.4.2
>            Reporter: Dennis Lundberg
>             Fix For: 2.9
>
>
> This came up on the user list:
> {quote}
> Isn't strange to have to define the maven-site-plugin inside <build> just to
> specify the version ?
> Why maven 2 can't take into account the version declare inside <reporting> ?
> It seems to more natural isn't it ?
> {quote}
> http://www.nabble.com/Re%3A--ANN--Maven-Site-Plugin-2.0-beta-7-Released-p18311450.html

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

        

[jira] Commented: (MPLUGIN-124) The generated documentation for a Mojo should show if it is a build plugin or a reporting plugin

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

Benson Margulies commented on MPLUGIN-124:
------------------------------------------

It's easy to add text for 'requiresReports'. I can't see how to go about, however, taking notice of those plugins that work both ways.

> The generated documentation for a Mojo should show if it is a build plugin or a reporting plugin
> ------------------------------------------------------------------------------------------------
>
>                 Key: MPLUGIN-124
>                 URL: https://jira.codehaus.org/browse/MPLUGIN-124
>             Project: Maven 2.x Plugin Tools
>          Issue Type: Improvement
>          Components: Plugin Plugin
>    Affects Versions: 2.4.2
>            Reporter: Dennis Lundberg
>
> This came up on the user list:
> {quote}
> Isn't strange to have to define the maven-site-plugin inside <build> just to
> specify the version ?
> Why maven 2 can't take into account the version declare inside <reporting> ?
> It seems to more natural isn't it ?
> {quote}
> http://www.nabble.com/Re%3A--ANN--Maven-Site-Plugin-2.0-beta-7-Released-p18311450.html

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

        

[jira] Commented: (MPLUGIN-124) The generated documentation for a Mojo should show if it is a build plugin or a reporting plugin

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

Vincent Siveton commented on MPLUGIN-124:
-----------------------------------------

The code already displays a notice if the plugin is a report. By default, all plugins are build plugins.
See http://maven.apache.org/plugin-tools/maven-plugin-tools-api/xref/org/apache/maven/tools/plugin/generator/PluginXdocGenerator.html#207

> The generated documentation for a Mojo should show if it is a build plugin or a reporting plugin
> ------------------------------------------------------------------------------------------------
>
>                 Key: MPLUGIN-124
>                 URL: http://jira.codehaus.org/browse/MPLUGIN-124
>             Project: Maven 2.x Plugin Tools
>          Issue Type: Improvement
>          Components: Plugin Plugin
>    Affects Versions: 2.4.2
>            Reporter: Dennis Lundberg
>
> This came up on the user list:
> {quote}
> Isn't strange to have to define the maven-site-plugin inside <build> just to
> specify the version ?
> Why maven 2 can't take into account the version declare inside <reporting> ?
> It seems to more natural isn't it ?
> {quote}
> http://www.nabble.com/Re%3A--ANN--Maven-Site-Plugin-2.0-beta-7-Released-p18311450.html

-- 
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-124) The generated documentation for a Mojo should show if it is a build plugin or a reporting plugin

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

Benson Margulies commented on MPLUGIN-124:
------------------------------------------

Note that the description in here bears no particular relation to the title. I did some work based on the title and have closed this out. The text talks about a long-decided issue.

> The generated documentation for a Mojo should show if it is a build plugin or a reporting plugin
> ------------------------------------------------------------------------------------------------
>
>                 Key: MPLUGIN-124
>                 URL: https://jira.codehaus.org/browse/MPLUGIN-124
>             Project: Maven 2.x Plugin Tools
>          Issue Type: Improvement
>          Components: Plugin Plugin
>    Affects Versions: 2.4.2
>            Reporter: Dennis Lundberg
>             Fix For: 2.9
>
>
> This came up on the user list:
> {quote}
> Isn't strange to have to define the maven-site-plugin inside <build> just to
> specify the version ?
> Why maven 2 can't take into account the version declare inside <reporting> ?
> It seems to more natural isn't it ?
> {quote}
> http://www.nabble.com/Re%3A--ANN--Maven-Site-Plugin-2.0-beta-7-Released-p18311450.html

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