[ http://jira.codehaus.org/browse/MRM-211?page=comments#action_78024 ] 
            
nicolas de loof commented on MRM-211:
-------------------------------------

I simply added 
"
    <component>
      <role>org.apache.maven.artifact.handler.ArtifactHandler</role>
      <role-hint>plugin</role-hint>
      
<implementation>org.apache.maven.artifact.handler.DefaultArtifactHandler</implementation>
      <configuration>
        <type>plugin</type>
        <extension>jar</extension>
        <language>java</language>
        <addedToClasspath>true</addedToClasspath>
      </configuration>
    </component>        
"

In WEB-INF/classes/META-INF/plexus/components.xml and it works now.

Do we have to upgrade maven-artifact for this or can we consider this "maven 1 
support" feature to be only in archiva scope ?

> Cannot use Archiva to get Maven1 Plugins
> ----------------------------------------
>
>                 Key: MRM-211
>                 URL: http://jira.codehaus.org/browse/MRM-211
>             Project: Archiva
>          Issue Type: Bug
>          Components: remote proxy
>            Reporter: nicolas de loof
>            Priority: Minor
>
> I request maven PMD plugin 1.9 using maven1
> Archiva looks into http://repo1.maven.org/maven2/maven/maven-pmd-plugin/1.9/ 
> and get the POM -> OK
> It then searchs the Artifact as 
> "maven/maven-pmd-plugin/1.9/maven-pmd-plugin-1.9.plugin" -> NOK
> Even looking at maven/maven-pmd-plugin/1.9/maven-pmd-plugin-1.9.jar fails : 
> the artifact doesn't exist ! It has a POM and a sources-jar but no binary 
> artifact. Maybe a m1-to-m2 repo-converter error ?

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

        

Reply via email to