maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Casey (JIRA)" <j...@codehaus.org>
Subject [jira] Created: (MNG-2806) Provide a means of replacing one mojo binding with another, without knowing the location of the first binding in the lifecycle
Date Thu, 01 Feb 2007 21:53:44 GMT
Provide a means of replacing one mojo binding with another, without knowing the location of
the first binding in the lifecycle
------------------------------------------------------------------------------------------------------------------------------

                 Key: MNG-2806
                 URL: http://jira.codehaus.org/browse/MNG-2806
             Project: Maven 2
          Issue Type: New Feature
          Components: POM
    Affects Versions: 2.0.4
            Reporter: John Casey


Lifecycle phase-bindings that are inherited from parent POMs or packaging-mappings are invisible
to the user, without sometimes extensive research into the POM lineage and/or the extension
artifact source that brings in the packaging-mapping.

For end users in a large development environment, it should be possible to replace an inherited
mojo binding with one specified in the local POM, without needing to know what phase that
binding is attached to. It is possible to see the full mojo ID and execution ID for a replacement
target in the debug output of a build, but phase transitions are not logged...which makes
researching the phase-location of a mojo binding quite difficult. Replacement should be available
at either the execution level, or the mojo level within a specified execution.

If replacing a mojo in the lifecycle mapping given by the project's packaging, the executionId
for the replacement should be 'default'.

This feature should be accompanied by a new mojo in the help plugin which can print out the
effective build steps in that project's lifecycle, to help with debugging replacements, etc.

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

        

Mime
View raw message