[ http://jira.codehaus.org/browse/MNG-729?page=comments#action_44394 ]
Kenney Westerhof commented on MNG-729: -------------------------------------- This component isn't added to the HandlerManager's list of available Handlers, because it uses a List(?) to store the Handlers. The component should already be discovered before the HandlerManager is configured (looked-up), to be added to that list. A modification of the HandlerManager to look up components for unknown role-hints etc. could be made. It was done for the CompilerManager too. Comments? > Ability to additional ArtifactHandlers using external components.xml > -------------------------------------------------------------------- > > Key: MNG-729 > URL: http://jira.codehaus.org/browse/MNG-729 > Project: Maven 2 > Type: Bug > Components: maven-artifact > Versions: 2.0-beta-1 > Environment: xp > Reporter: Dan Tran > Fix For: 2.0-beta-1 > > > I have a need to add a new ArtifactHandler using my own components.xml. It > turns out the the setting is ignored unless I > merge my xml to > maven-artifact/src/main/resources/META-INF/plexus/components.xml and > bootstrap m2 to take affect. > Here is an example of my components declaration > <component> > <role>org.apache.maven.artifact.handler.ArtifactHandler</role> > <role-hint>native</role-hint> > > <implementation>org.apache.maven.artifact.handler.DefaultArtifactHandler</implementation> > <configuration> > <type>dll</type> > <extension>dll</extension> > <packaging>native</packaging> > </configuration> > </component> -- 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]
