You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Paul Benedict (JIRA)" <ji...@codehaus.org> on 2014/07/03 17:33:11 UTC
[jira] (MNG-1569) Make build process info read-only to mojos, and
provide mechanism for explicit out-params for mojos to declare
[ https://jira.codehaus.org/browse/MNG-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Benedict updated MNG-1569:
-------------------------------
Fix Version/s: (was: Issues to be reviewed for 4.x)
> Make build process info read-only to mojos, and provide mechanism for explicit out-params for mojos to declare
> --------------------------------------------------------------------------------------------------------------
>
> Key: MNG-1569
> URL: https://jira.codehaus.org/browse/MNG-1569
> Project: Maven
> Issue Type: New Feature
> Components: Design, Patterns & Best Practices
> Affects Versions: 2.0
> Reporter: John Casey
> Priority: Trivial
>
> 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 was sent by Atlassian JIRA
(v6.1.6#6162)