You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@archiva.apache.org by Nicolas DE LOOF <ni...@capgemini.com> on 2006/10/18 15:44:58 UTC
Filtered proxy ?
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.
Re: Filtered proxy ?
Posted by Nicolas DE LOOF <ni...@capgemini.com>.
Seems the same issue.
ejb and ejb-clients types are allready configured in maven-artifact
configuration, so they should work (or there is another isue)
How could archiva handle "non standard" artifacts without requirement
for a new Archiva release ? For example, people may want to create some
"it-tests" jars. Could Archiva update it's plexus configuration at
runtime to add such custom types ?
Nico.
Arnaud HERITIER a écrit :
> http://jira.codehaus.org/browse/MRM-210 is related to this problem
>
> cheers
>
> Arnaud
>
> On 10/19/06, Nicolas DE LOOF <ni...@capgemini.com> wrote:
>>
>>
>> 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.
>>
>>
>
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.
Re: Filtered proxy ?
Posted by Arnaud HERITIER <ah...@gmail.com>.
http://jira.codehaus.org/browse/MRM-210 is related to this problem
cheers
Arnaud
On 10/19/06, Nicolas DE LOOF <ni...@capgemini.com> wrote:
>
>
> 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.
>
>
Re: Filtered proxy ?
Posted by Nicolas DE LOOF <ni...@capgemini.com>.
I updated my archiva webapp (it runs under tomcat) to include a
DefaultArtifactHandler component for "plugin" type in
WEB-INF/classes/META-INF/plexus/components.xml.
I now can download maven1 plugins now.
I don't know if this DefaultArtifactHandler may be define in
maven-artifact project or in archiva as this is only required to support
Maven1 artifacts, that is out of maven2 scope.
This doesn't solve the issue of
http://repo1.maven.org/maven2/maven/maven-pmd-plugin/1.9/
The maven2 repo contains a pom, a source-jar but no artifact jar.
Is archiva used for converting maven1 repository to maven2 or is this a
"MPA" issue ?
Nico.
Brett Porter a écrit :
> They should be able to be added.
>
> - Brett
>
> On 19/10/2006, at 9:11 PM, Nicolas DE LOOF wrote:
>
>>
>> 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.
>
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.
Re: Filtered proxy ?
Posted by Brett Porter <br...@apache.org>.
They should be able to be added.
- Brett
On 19/10/2006, at 9:11 PM, Nicolas DE LOOF wrote:
>
> 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.
Re: Filtered proxy ?
Posted by Nicolas DE LOOF <ni...@capgemini.com>.
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.
Re: Filtered proxy ?
Posted by Emmanuel Venisse <em...@venisse.net>.
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.
>
>
>
>