Mailing-List: contact archiva-users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: archiva-users@maven.apache.org
Received-SPF: pass (athena.apache.org: domain of nicolas.deloof@gmail.com
 designates 64.233.182.190 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth;
        b=fYzEAyIQhNggnrev4QXbikSjsgB/Z2Fz9B3CGHu/V11U5BnS34HJtS3tNM2KgSjIVKWA4jo5zagCcWXUNw9NxFfboZv5OdN+THMO0BMkRrg5oBjR/P+3+p/eqxHR9HozhXfei89mr9fyosURn945NHia4o2uwOm7xJEpJ6DF41g=
Message-ID: <4c39e3030804080037p5215b5b0wdd670423fb1a2c08@mail.gmail.com>
Date: Tue, 8 Apr 2008 09:37:52 +0200
From: "nicolas de loof" <nicolas@apache.org>
Sender: nicolas.deloof@gmail.com
To: archiva-users@maven.apache.org
Subject: Re: Cannot configure Legacy Artifact Path Resolution of Non-standard
 path
In-Reply-To: <2ade7f6e0804080020n13530f77v7a56ce61c4698de0@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_3273_13923089.1207640272643"
References: <2ade7f6e0804080020n13530f77v7a56ce61c4698de0@mail.gmail.com>

------=_Part_3273_13923089.1207640272643
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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 :

      <role>org.apache.maven.artifact.handler.ArtifactHandler</role>
      <role-hint>maven-plugin</role-hint>
      <configuration>
         <type>maven-plugin</type>
         <extension>jar</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 <mrmallete@gmail.com>:
>
> 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
>

------=_Part_3273_13923089.1207640272643--