[jira] Updated: (MNG-1569) Make build process info read-only to mojos, and provide mechanism for explicit out-params for mojos to declare

["Jason van Zyl (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MNG-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason van Zyl updated MNG-1569:
-------------------------------

    Fix Version/s:     (was: 3.x)
                   3.1.alpha1

This will be one of the key deprecations to make during 3.0 as it will likely affect several plugins that are twiddling with what should be immutable information.

> Make build process info read-only to mojos, and provide mechanism for explicit out-params for mojos to declare
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-1569
>                 URL: http://jira.codehaus.org/browse/MNG-1569
>             Project: Maven 2 & 3
>          Issue Type: New Feature
>          Components: Design, Patterns & Best Practices
>    Affects Versions: 2.0
>            Reporter: John Casey
>            Priority: Trivial
>             Fix For: 3.1.alpha1
>
>
> We need to have the ability to look at a mojo descriptor and see how it will change the build environment. This requires two things:
> 1. Cut off the loophole allowing unauthorized mutation of build state by making build state read-only to the mojo
> 2. Provide an API/annotation-set to allow explicit export of values from a mojo, where they will be incorporated into the build state.
> This should enable things like determining whether a mojo generates sources, or collecting the source directories (even generated ones) by scanning the plugins configured for the build.

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