Maven 2 & 3

Make build process info read-only to mojos, and provide mechanism for explicit out-params for mojos to declare

Details

  • Complexity:
    Expert
  • Number of attachments :
    0

Description

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.

Issue Links

This issue relates to:
MNG-193 symmetry for outputs of a plugin Major Open

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Brett Porter added a comment -

John - did you think this is important for 2.1?

Show
Brett Porter added a comment - John - did you think this is important for 2.1?
Hide
Permalink
Jason van Zyl added a comment -

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.

Show
Jason van Zyl added a comment - 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.

People

Vote (1)
Watch (1)

Dates

  • Created:
    Updated:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.