MRM-211
I looked into code and I think this is an issue with maven2
DefaultArtifactHandler configuration, that has no configuration for
"plugin" type.
Would this require to update maven2 artifact project, or can archiva
plexus configuration be set to "add" some ArtifactHandlers ?
Nico.
Emmanuel Venisse a écrit :
Seems to be a bug. Please, file an issue.
Emmanuel
Nicolas DE LOOF a écrit :
Yet another question :
How to handle maven1 plugins using Archiva as a proxy ?
Example : 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
It also searchs the Artifact as
"maven/maven-pmd-plugin/1.9/maven-pmd-plugin-1.9.plugin" (from logs)
Sounds like a little bug.
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.
What's wrong ?
This message contains information that may be privileged or
confidential and is the property of the Capgemini Group. It is
intended only for the person to whom it is addressed. If you are not
the intended recipient, you are not authorized to read, print,
retain, copy, disseminate, distribute, or use this message or any
part thereof. If you receive this message in error, please notify
the sender immediately and delete all copies of this message.
This message contains information that may be privileged or confidential and is
the property of the Capgemini Group. It is intended only for the person to whom
it is addressed. If you are not the intended recipient, you are not authorized
to read, print, retain, copy, disseminate, distribute, or use this message or
any part thereof. If you receive this message in error, please notify the
sender immediately and delete all copies of this message.
