Agrea about java-sources, was just for testing. This is an anoying issue as some maven1 core plugins (plugin-plugin and scm-plugin) refer to jaxen-1.0-FCS-full, "full" beeing a classifier in m2 repo.
I understand you don't want to break for the N'th time the maven1 legacy handling. Could we just consider some "exception-list" in the legacy to Artifact discovery ? A property-file based solution would allow archiva admin to solve such issues with fiew impacts on archiva. Nico. 2007/11/13, Joakim Erdfelt <[EMAIL PROTECTED]>: > > The path "org.apache.commons/jars/commons-io-1.3.2-sources.jar" is in > the wrong place. > That source jar should be in > "org.apache.commons/java-sources/commons-io-1.3.2-sources.jar" > > Example: org.apache.camel/java-sources/camel-script-1.1.0-sources.jar > > Again, m1 repos do not support classifiers. > The only reason this specific case works is that there is a special case > specific mapping for ... > (type) "java-source" to (extension) "-sources.jar" > > The current m1 file repo on people.apache.or has 1479 source jars in the > proper place. and 107 in the wrong place. > If you need classifiers, use maven 2 (that's where it was really > introduced) > > - Joakim > > nicolas de loof wrote: > > That's right, I just forgot those ones :-/ > > > > Requesting org.apache.commons/jars/commons-io-1.3.2-sources.jar also > fails > > and is translated to > > org/apache/commons/commons-io/1.3.2-sources/commons-io-1.3.2-sources.jar > > > > > > But maybe this is NOT an issue : in maven1 world there is no classifier, > and > > my backport should be put in "groupId/backports/artifact-backport.jar", > the > > same way -sources.jar are put into "/java-sources/". > > > > Nico. > > > > > > 2007/11/13, Brett Porter <[EMAIL PROTECTED]>: > > > >> Anything with source or javadoc :) > >> > >> - Brett > >> > >> On 13/11/2007, at 9:33 AM, nicolas de loof wrote: > >> > >> > >>> MRM-593 > >>> > >>> Do you know any artifact in central that uses a classifier ? I'd > >>> like to > >>> make the test on a non-SNAPSHOT artifact. Struts does not publish > >>> it's "j4" > >>> backported artifacts. > >>> > >>> Nico. > >>> > >>> 2007/11/13, Brett Porter <[EMAIL PROTECTED]>: > >>> > >>>> Thanks again Nicolas - I'm sure this is easily fixed, so it would be > >>>> worth dropping in JIRA. > >>>> > >>>> - Brett > >>>> > >>>> On 13/11/2007, at 9:20 AM, nicolas de loof wrote: > >>>> > >>>> > >>>>> I have a lib that is built by maven2. It also has a retrotranslator > >>>>> version, > >>>>> with classifier "-backport", as part of the build process. > >>>>> > >>>>> When I deploy a SNAPSHOT of this lib, I get : > >>>>> > >>>>> [INFO] [deploy:deploy] > >>>>> [INFO] Retrieving previous build number from platina > >>>>> Uploading: ..../jmonit-1.0-alpha-1-SNAPSHOT.jar > >>>>> 78K uploaded > >>>>> ... > >>>>> Uploading: ..../jmonit-1.0-alpha-1-SNAPSHOT-backport.jar > >>>>> 47K uploaded > >>>>> > >>>>> > >>>>> > >>>>> When I try to get this lib from archiva, I get a 404, as the m1 path > >>>>> "org.jmonit/jars/jmonit-1.0-alpha-1-SNAPSHOT-backport.jar" > >>>>> gets converted to > >>>>> " > >>>>> org/jmonit/jmonit/1.0-alpha-1-SNAPSHOT-backport/jmonit-1.0-alpha-1- > >>>>> SNAPSHOT-backport.jar<http://sai1rennes:8888/repository/org/jmonit/ > >>>>> jmonit/1.0-alpha-1-SNAPSHOT-backport/jmonit-1.0-alpha-1-SNAPSHOT- > >>>>> backport.jar> > >>>>> " > >>>>> and not > >>>>> org/jmonit/jmonit/1.0-alpha-1-SNAPSHOT/jmonit-1.0-alpha-1-SNAPSHOT- > >>>>> backport.jar<http://sai1rennes:8888/repository/org/jmonit/jmonit/ > >>>>> 1.0-alpha-1-SNAPSHOT-backport/jmonit-1.0-alpha-1-SNAPSHOT- > >>>>> backport.jar> > >>>>> > >>>>> --> The classifier is not recognized. > >>>>> Not tested with other dependencies, but I'm not sure we have good > >>>>> support > >>>>> for classifiers as part of m1 requests. > >>>>> > >>>>> Nico. > >>>>> > >>>> -- > >>>> Brett Porter - [EMAIL PROTECTED] > >>>> Blog: http://www.devzuz.org/blogs/bporter/ > >>>> > >>>> > >>>> > >> -- > >> Brett Porter - [EMAIL PROTECTED] > >> Blog: http://www.devzuz.org/blogs/bporter/ > >> > >> > >> > > > > > >
