[ http://jira.codehaus.org/browse/MNG-598?page=comments#action_43356 ]
Brett Porter commented on MNG-598:
----------------------------------
We don't want to have to resolve and search all
the plugins to find a missing dependency type. For this, we can add
<extensions>true|false</extensions> to the <plugin/> element, eg:
<plugin>
<groupId>org.codehaus.plexus</groupId>
<artifactId>plexus-maven-plugin</artifactId>
<extensions>true</extensions>
<configuration>
...
</configuration>
</plugin>
This will indicate to the plugin manager to pre-load those plugins, and
to search it for any plexus components. When the lifecycle executor is
looking for a packaging handler, it will have to search those plugin
containers also.
> new type handlers cannot be added outside of maven-core
> -------------------------------------------------------
>
> Key: MNG-598
> URL: http://jira.codehaus.org/browse/MNG-598
> Project: Maven 2
> Type: Bug
> Reporter: Brett Porter
> Assignee: Brett Porter
> Priority: Blocker
> Fix For: 2.0-beta-1
>
>
> adding type handlers in your own plugin will not put them into the map that
> the lifecycle executor is using. the maps need to be merged.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
