www-repository mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Damian Bradicich <dbradic...@sonatype.com>
Subject Re: Merge two staging repos
Date Fri, 18 Dec 2009 14:18:03 GMT
Hi Gert, I dug into this and found why the 2 staging repos were created.
First a little detail, we use 3 criteria to define which staging repo
artifacts will go into:

#1: userId or remote request
#2: ip address of remote request
#3: user agent of remote request

In your case the userId and ip address were the same for both staging repos,
but seems some part of your build used a different user agent, thus causing
a new staging repo to get created

Apache-Maven/2.2 (Java 1.6.0_16; Linux 2.6.31-16-generic)
Apache-Maven/2.2 (Java 1.5.0_18; Linux 2.6.31-16-generic)

Note that you cannot merge these staging repositories ( actually there is
really no need to merge these staging repositories together), you can simply
perform actions on them together, when you close one, close the other, drop
one, drop the other etc.

Hope that helps


On Thu, Dec 17, 2009 at 9:01 PM, Gert Vanthienen

> L.S.,
> While doing a fairly large set of releases this evening, I noticed
> that the artifacts have been put in two separate staging repos:
> -
> https://repository.apache.org/content/repositories/orgapacheservicemix-058/
> -
> https://repository.apache.org/content/repositories/orgapacheservicemix-061/
> Not entirely sure what caused the creation of the second staging repo
> (user id and ip address didn't change).  Is it possible to somehow
> merge these two staging repos into a single staging repo?  For now, I
> haven't closed the staging repos because I guess it would definitely
> be impossible once they're closed.
> Regards,
> Gert Vanthienen
> ------------------------
> Open Source SOA: http://fusesource.com
> Blog: http://gertvanthienen.blogspot.com/

View raw message