Cannot configure Legacy Artifact Path Resolution of Non-standard path

2008-04-08 Thread Michael Mallete
Hi guys,

I'm having troubles configuring legacy artifact path for maven-jaxb-plugin.
Artifact is located here:

http://download.java.net/maven/1/com.sun.tools.xjc.maven2/maven-plugins/

I believe, the M1 standard is to rather put maven plugins inside the
plugins directory instead of maven-plugins. Anyway, I tried configuring
it via admin:

Path: com.sun.tools.xjc.maven2/maven-plugins/maven-jaxb-plugin-1.1.jar
GroupId: com.sun.tools.xjc.maven2
ArtifactId: maven-jaxb-plugin
Version: 1.1
Classifier:
Type: maven-plugin

And get this on submit:

artifact reference does not match the initial path :
com.sun.tools.xjc.maven2/plugins/maven-jaxb-plugin-1.1.jar

Also, the auto complete feature does not correctly slice the input
initially:

ArtifactId: maven
Version: jaxb-plugin-1.1

I just manually deployed to archiva instead using the pom and the jar file
from this repo.

Thanx!

regards,
mykol


Re: Cannot configure Legacy Artifact Path Resolution of Non-standard path

2008-04-08 Thread Michael Mallete
hi nicolas,

here you go:

http://jira.codehaus.org/browse/MRM-768


On Tue, Apr 8, 2008 at 3:37 PM, nicolas de loof [EMAIL PROTECTED] wrote:

 legacy artifact path configuration is a way for archiva to support maven1
 clients (maven1 request URL is not fine-grained enough to safelly detect
 the
 artifactId / version / classifier).

 When you want to acces a legacy-layout repository using a proxy connector,
 you don't need to configure anything.


 Your issue is that archiva search the expected artifact in /plugins/ and
 not
 in /maven-plugins/

 In archiva source code ( AbstractLegacyRepositoryContent.java ) I can read
 :

typeToDirectoryMap.put( ArtifactExtensionMapping.MAVEN_PLUGIN,
 plugin );

 BUT when deploying a project to a legacy repo, the maven ArtifactHandler
 (in
 maven-artifact.jar) set :

  roleorg.apache.maven.artifact.handler.ArtifactHandler/role
  role-hintmaven-plugin/role-hint
  configuration
 typemaven-plugin/type
 extensionjar/extension


 IMHO, archiva tries to use the same type for two incompatible artifacts
 :
 maven1 plugins and maven2 ones. As requesting a maven2 plugin from a
 maven1
 repository is really not a common use case, this may not have been
 discovered yet.

 Please open an Issue for this.

 Nicolas.




 2008/4/8, Michael Mallete [EMAIL PROTECTED]:
 
  Hi guys,
 
  I'm having troubles configuring legacy artifact path for
  maven-jaxb-plugin.
  Artifact is located here:
 
  http://download.java.net/maven/1/com.sun.tools.xjc.maven2/maven-plugins/
 
  I believe, the M1 standard is to rather put maven plugins inside the
  plugins directory instead of maven-plugins. Anyway, I tried
  configuring
  it via admin:
 
  Path: com.sun.tools.xjc.maven2/maven-plugins/maven-jaxb-plugin-1.1.jar
  GroupId: com.sun.tools.xjc.maven2
  ArtifactId: maven-jaxb-plugin
  Version: 1.1
  Classifier:
  Type: maven-plugin
 
  And get this on submit:
 
  artifact reference does not match the initial path :
  com.sun.tools.xjc.maven2/plugins/maven-jaxb-plugin-1.1.jar
 
  Also, the auto complete feature does not correctly slice the input
  initially:
 
  ArtifactId: maven
  Version: jaxb-plugin-1.1
 
  I just manually deployed to archiva instead using the pom and the jar
 file
  from this repo.
 
  Thanx!
 
  regards,
  mykol