You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@archiva.apache.org by Benoit Decherf <de...@yahoo-inc.com> on 2008/04/16 10:55:16 UTC

Error uploading artifact (MRM-753)

Hi,

We are blocked by this issue.
This is blocker because if it fails while uploading a jar file, then the 
pom is already in the repo and the metadata.xml is already updated. It 
makes the others components that depend on it to fails.

Is there any workaround ?

The stacktrace shows that it come from the security module (redback). Is 
it possible to desactivate it ?

Benoit

Re: Error uploading artifact (MRM-753)

Posted by Arnaud HERITIER <ah...@gmail.com>.
Brett proposed to try if the change in wagon for archiva 1.1 will change this.
I'll try to free some hours to test it, because it is a very very anoying bug.
The repository doesn't have all data and our CI server fails without a
real reason.

Arnaud

On Wed, Apr 16, 2008 at 10:55 AM, Benoit Decherf <de...@yahoo-inc.com> wrote:
> Hi,
>
>  We are blocked by this issue.
>  This is blocker because if it fails while uploading a jar file, then the
> pom is already in the repo and the metadata.xml is already updated. It makes
> the others components that depend on it to fails.
>
>  Is there any workaround ?
>
>  The stacktrace shows that it come from the security module (redback). Is it
> possible to desactivate it ?
>
>  Benoit
>



-- 
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................