maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <j...@codehaus.org>
Subject [jira] Closed: (MCOMPILER-147) The usage page should use pluginManagement for configuring the plugin
Date Mon, 29 Aug 2011 19:21:35 GMT

     [ https://jira.codehaus.org/browse/MCOMPILER-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robert Scholte closed MCOMPILER-147.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.4
         Assignee: Robert Scholte

Patch applied, fixed in [rev. 1162949|http://svn.apache.org/viewvc?rev=1162949&view=rev].
Thanks!

> The usage page should use pluginManagement for configuring the plugin
> ---------------------------------------------------------------------
>
>                 Key: MCOMPILER-147
>                 URL: https://jira.codehaus.org/browse/MCOMPILER-147
>             Project: Maven 2.x Compiler Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.3.2
>         Environment: n/a
>            Reporter: Anders Hammar
>            Assignee: Robert Scholte
>            Priority: Minor
>             Fix For: 2.4
>
>         Attachments: m-compiler-p_site-usage.patch
>
>
> IMO, when configuring plugins (especially those bound to the lifecycle through the packaging)
the pluginManagement section should be used. Like when specifying the version.
> The current usage page does not say so.
> The attached patch updates thsi page to use pluginManagent. Also, I added a note about
Maven 3.0 complaining if you don't specify the version (as related question has been brought
up on the users mailing list twice with a few weeks).
> Also, a typos with regards to the goals of the plugin on the usage page was also fixed.

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

        

Mime
View raw message