You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@archiva.apache.org by nicolas de loof <ni...@gmail.com> on 2007/11/13 15:20:30 UTC
small issue with maven1 (legacy) request resolution
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.
Re: small issue with maven1 (legacy) request resolution
Posted by Joakim Erdfelt <jo...@erdfelt.com>.
(haven't read the rest of the thread yet)
the m1 repository format does not support classifiers.
never had, never will, and frankly, it can't ever support it as the
format is too ambiguous to detect classifier.
- Joakim
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.
>
>
Re: small issue with maven1 (legacy) request resolution
Posted by nicolas de loof <ni...@gmail.com>.
.. but anyway, would it be usable in a m1 project ?
Having a dependency with a non-standard type will not be resolved by maven1
to ".jar" extension
2007/11/13, nicolas de loof <ni...@gmail.com>:
>
> That would be a better description of my issue :
>
> There is no way to access from maven1 some artifacts that use the
> m2-specific "classifier" concept. Using <type>classifier</type> would create
> valid m1 requests but requires to configure some custom type -> extensions
> mappings in archiva.
>
> Nico.
>
> 2007/11/13, Brett Porter <br...@apache.org>:
> >
> > Good point - in fact Joakim had mentioned this already and I gave the
> > same explanation. Coffee helps me remember :)
> >
> > So you're really looking for a feature request to make the m1 type
> > mappings extensible?
> >
> > - Brett
> >
> > On 13/11/2007, at 9:44 AM, 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 < brett@apache.org>:
> > >>
> > >> 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 <brett@apache.org >:
> > >>>>
> > >>>> 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 - brett@apache.org
> > >>>> Blog: http://www.devzuz.org/blogs/bporter/
> > >>>>
> > >>>>
> > >>
> > >> --
> > >> Brett Porter - brett@apache.org
> > >> Blog: http://www.devzuz.org/blogs/bporter/
> > >>
> > >>
> >
> > --
> > Brett Porter - brett@apache.org
> > Blog: http://www.devzuz.org/blogs/bporter/
> >
> >
>
Re: small issue with maven1 (legacy) request resolution
Posted by nicolas de loof <ni...@gmail.com>.
That would be a better description of my issue :
There is no way to access from maven1 some artifacts that use the
m2-specific "classifier" concept. Using <type>classifier</type> would create
valid m1 requests but requires to configure some custom type -> extensions
mappings in archiva.
Nico.
2007/11/13, Brett Porter <br...@apache.org>:
>
> Good point - in fact Joakim had mentioned this already and I gave the
> same explanation. Coffee helps me remember :)
>
> So you're really looking for a feature request to make the m1 type
> mappings extensible?
>
> - Brett
>
> On 13/11/2007, at 9:44 AM, 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 <br...@apache.org>:
> >>
> >> 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 <br...@apache.org>:
> >>>>
> >>>> 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 - brett@apache.org
> >>>> Blog: http://www.devzuz.org/blogs/bporter/
> >>>>
> >>>>
> >>
> >> --
> >> Brett Porter - brett@apache.org
> >> Blog: http://www.devzuz.org/blogs/bporter/
> >>
> >>
>
> --
> Brett Porter - brett@apache.org
> Blog: http://www.devzuz.org/blogs/bporter/
>
>
Re: small issue with maven1 (legacy) request resolution
Posted by Brett Porter <br...@apache.org>.
Good point - in fact Joakim had mentioned this already and I gave the
same explanation. Coffee helps me remember :)
So you're really looking for a feature request to make the m1 type
mappings extensible?
- Brett
On 13/11/2007, at 9:44 AM, 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 <br...@apache.org>:
>>
>> 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 <br...@apache.org>:
>>>>
>>>> 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 - brett@apache.org
>>>> Blog: http://www.devzuz.org/blogs/bporter/
>>>>
>>>>
>>
>> --
>> Brett Porter - brett@apache.org
>> Blog: http://www.devzuz.org/blogs/bporter/
>>
>>
--
Brett Porter - brett@apache.org
Blog: http://www.devzuz.org/blogs/bporter/
Re: small issue with maven1 (legacy) request resolution
Posted by nicolas de loof <ni...@gmail.com>.
I just attached a patch to MRM-594
This simply converts PathParsers to plexus components and add support for
some exceptions in the LegacyPathParser path 2 artifact conversion, based on
properties :
path -> groupId:artifactId:version:classifier:type
The resolution of this issue requires some way to manage those properties.
Maybe store them in archiva.xml ? Or in the Database ?
A full user-friendly resolution of this issue will require some web UI
management. I've never used struts2/webwork so can hardly help for this.
Nico.
2007/11/14, nicolas de loof <ni...@gmail.com>:
>
> 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 <jo...@erdfelt.com>:
> >
> > 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 <brett@apache.org >:
> > >
> > >> 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 <br...@apache.org>:
> > >>>
> > >>>> 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 - brett@apache.org
> > >>>> Blog: http://www.devzuz.org/blogs/bporter/
> > >>>>
> > >>>>
> > >>>>
> > >> --
> > >> Brett Porter - brett@apache.org
> > >> Blog: http://www.devzuz.org/blogs/bporter/
> > >>
> > >>
> > >>
> > >
> > >
> >
> >
>
Re: small issue with maven1 (legacy) request resolution
Posted by nicolas de loof <ni...@gmail.com>.
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 <jo...@erdfelt.com>:
>
> 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 <br...@apache.org>:
> >
> >> 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 <br...@apache.org>:
> >>>
> >>>> 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 - brett@apache.org
> >>>> Blog: http://www.devzuz.org/blogs/bporter/
> >>>>
> >>>>
> >>>>
> >> --
> >> Brett Porter - brett@apache.org
> >> Blog: http://www.devzuz.org/blogs/bporter/
> >>
> >>
> >>
> >
> >
>
>
Re: small issue with maven1 (legacy) request resolution
Posted by Joakim Erdfelt <jo...@erdfelt.com>.
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 <br...@apache.org>:
>
>> 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 <br...@apache.org>:
>>>
>>>> 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 - brett@apache.org
>>>> Blog: http://www.devzuz.org/blogs/bporter/
>>>>
>>>>
>>>>
>> --
>> Brett Porter - brett@apache.org
>> Blog: http://www.devzuz.org/blogs/bporter/
>>
>>
>>
>
>
Re: small issue with maven1 (legacy) request resolution
Posted by nicolas de loof <ni...@gmail.com>.
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 <br...@apache.org>:
>
> 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 <br...@apache.org>:
> >>
> >> 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 - brett@apache.org
> >> Blog: http://www.devzuz.org/blogs/bporter/
> >>
> >>
>
> --
> Brett Porter - brett@apache.org
> Blog: http://www.devzuz.org/blogs/bporter/
>
>
Re: small issue with maven1 (legacy) request resolution
Posted by Brett Porter <br...@apache.org>.
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 <br...@apache.org>:
>>
>> 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 - brett@apache.org
>> Blog: http://www.devzuz.org/blogs/bporter/
>>
>>
--
Brett Porter - brett@apache.org
Blog: http://www.devzuz.org/blogs/bporter/
Re: small issue with maven1 (legacy) request resolution
Posted by nicolas de loof <ni...@gmail.com>.
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 <br...@apache.org>:
>
> 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 - brett@apache.org
> Blog: http://www.devzuz.org/blogs/bporter/
>
>
Re: small issue with maven1 (legacy) request resolution
Posted by Brett Porter <br...@apache.org>.
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 - brett@apache.org
Blog: http://www.devzuz.org/blogs/bporter/