Mailing-List: contact repository-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: repository@apache.org
Received-SPF: unknown (athena.apache.org: error in processing during lookup of
 brianf@sonatype.com)
MIME-Version: 1.0
In-Reply-To: <abb1877f0912180618h5a115dc5i12b84acfb32efaa7@mail.gmail.com>
References: <67a6ab030912171801w25bc2ccds60e899182e75578@mail.gmail.com>
	 <abb1877f0912180618h5a115dc5i12b84acfb32efaa7@mail.gmail.com>
Date: Fri, 18 Dec 2009 09:21:51 -0500
Message-ID: <e9b1dfc0912180621v613f1612o658bda94bf7493c2@mail.gmail.com>
Subject: Re: Merge two staging repos
From: Brian Fox <brianf@sonatype.com>
To: repository <repository@apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

It looks like you have two separate builds here? (it's the only
explanation for you having multiple user agents) Each build should be
staged independently anyway, at least that was the original intent, to
capture the output from a single mvn execution into a separate repo.
It is possible to  work around that and stage things together, but
keeping them separate is generally easier. Note that all staging repos
are added to the same staging group so you don't have to add multiple
repos to your system for testing (if that's a concern)

On Fri, Dec 18, 2009 at 9:18 AM, Damian Bradicich
<dbradicich@sonatype.com> wrote:
> 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=A0which 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 rep=
os,
> but seems some part of your build used a different user agent, thus causi=
ng
> a new staging repo to get created
>
> Apache-Maven/2.2 (Java 1.6.0_16; Linux 2.6.31-16-generic)
> maven-artifact/2.2.1
> Apache-Maven/2.2 (Java 1.5.0_18; Linux 2.6.31-16-generic)
> maven-artifact/2.2.1
>
> Note that you cannot merge these staging repositories ( actually there is
> really no need to merge these staging repositories together), you can sim=
ply
> perform actions on them together, when you close one, close the other, dr=
op
> one, drop the other etc.
>
> Hope that helps
>
> Damian
>
> On Thu, Dec 17, 2009 at 9:01 PM, Gert Vanthienen <gert.vanthienen@gmail.c=
om>
> wrote:
>>
>> 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-0=
58/
>> -
>> https://repository.apache.org/content/repositories/orgapacheservicemix-0=
61/
>>
>> Not entirely sure what caused the creation of the second staging repo
>> (user id and ip address didn't change). =A0Is it possible to somehow
>> merge these two staging repos into a single staging repo? =A0For 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/
>
>