[
http://jira.codehaus.org/browse/MNG-2774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey closed MNG-2774.
---------------------------
Resolution: Fixed
> Provide a mechanism for "pre-scanning" POM lineage for build extensions,
> before project-building or lifecycle execution
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: MNG-2774
> URL: http://jira.codehaus.org/browse/MNG-2774
> Project: Maven 2
> Issue Type: New Feature
> Components: General
> Affects Versions: 2.0.4
> Reporter: John Casey
> Fix For: 2.1-alpha-1
>
>
> Currently, build extensions cannot affect the way the project gets built,
> including the profile activators that are used. There is no way to introduce
> a custom profile activator, or to introduce a custom artifact resolver before
> the project is built.
> To some extent, this is a chicken-egg problem of resolving POMs before you
> customize the resolution process. However, once we load the build extensions,
> any new resolvers, profile activators, etc. should be available to the rest
> of the build process.
--
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
