Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0-beta-1
-
Fix Version/s: 2.0-beta-1
-
Component/s: Artifacts and Repositories
-
Labels:None
-
Environment:xp
-
Complexity:Intermediate
Description
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>
Issue Links
- relates to
-
MNG-4654
Maven erroneously selects artifact handler contributed by extension plugin for use with project main artifact based on the handler's packaging rather than type
-
This component isn't added to the HandlerManager's list of available Handlers,
to store the Handlers. The component should already be discovered before
because it uses a List
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?