You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2008/07/22 18:20:28 UTC
[jira] Created: (MNG-3675) Add accessor for lifecycles list to
LifecycleExecutor/DefaultLifecycleExecutor
Add accessor for lifecycles list to LifecycleExecutor/DefaultLifecycleExecutor
------------------------------------------------------------------------------
Key: MNG-3675
URL: http://jira.codehaus.org/browse/MNG-3675
Project: Maven 2
Issue Type: New Feature
Components: Plugins and Lifecycle
Affects Versions: 2.0.9
Reporter: John Casey
Fix For: 2.0.10
This will enable plugins like the enforcer to calculate advanced information about where a plugin is coming from (whether from the default lifecycle listing, the lifecycle mappings from the packaging, or the POM itself), and perform certain types of audits.
--
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: (MNG-3675) Add accessor for lifecycles list to
LifecycleExecutor/DefaultLifecycleExecutor
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey closed MNG-3675.
---------------------------
Assignee: John Casey
Resolution: Fixed
> Add accessor for lifecycles list to LifecycleExecutor/DefaultLifecycleExecutor
> ------------------------------------------------------------------------------
>
> Key: MNG-3675
> URL: http://jira.codehaus.org/browse/MNG-3675
> Project: Maven 2
> Issue Type: New Feature
> Components: Plugins and Lifecycle
> Affects Versions: 2.0.9
> Reporter: John Casey
> Assignee: John Casey
> Fix For: 2.0.10
>
>
> This will enable plugins like the enforcer to calculate advanced information about where a plugin is coming from (whether from the default lifecycle listing, the lifecycle mappings from the packaging, or the POM itself), and perform certain types of audits.
--
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-3675) Add accessor for lifecycles list to
LifecycleExecutor/DefaultLifecycleExecutor
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey updated MNG-3675:
----------------------------
Fix Version/s: 2.0.10
> Add accessor for lifecycles list to LifecycleExecutor/DefaultLifecycleExecutor
> ------------------------------------------------------------------------------
>
> Key: MNG-3675
> URL: http://jira.codehaus.org/browse/MNG-3675
> Project: Maven 2
> Issue Type: New Feature
> Components: Plugins and Lifecycle
> Affects Versions: 2.0.9
> Reporter: John Casey
> Fix For: 2.0.10
>
>
> This will enable plugins like the enforcer to calculate advanced information about where a plugin is coming from (whether from the default lifecycle listing, the lifecycle mappings from the packaging, or the POM itself), and perform certain types of audits.
--
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