[ http://jira.codehaus.org/browse/MRM-211?page=comments#action_78023 ] nicolas de loof commented on MRM-211: -------------------------------------
As far as I understand Maven2 API, this issue requires to register to DefaultArtifactHandlerManager the expected handler Map with "jar" extensions for "plugin" type (and some others). The components.xml from Maven2 project "maven-artifact" does register custom extension for types * ejb * test-jar * maven-plugin (maven2 plugin) * java-source * javadoc * ejb-client Nothing about maven1 plugin > 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
