www-repository mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gert Vanthienen <gert.vanthie...@gmail.com>
Subject Re: Merge two staging repos
Date Fri, 18 Dec 2009 19:10:37 GMT
Brian, Damian,

Thanks for looking into this and explaining about the how/why of nexus
staging repositories!

Regards,

Gert Vanthienen
------------------------
Open Source SOA: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/



2009/12/18 Brian Fox <brianf@sonatype.com>:
> 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 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)
>> 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 simply
>> perform actions on them together, when you close one, close the other, drop
>> one, drop the other etc.
>>
>> Hope that helps
>>
>> Damian
>>
>> On Thu, Dec 17, 2009 at 9:01 PM, Gert Vanthienen <gert.vanthienen@gmail.com>
>> 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-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/
>>
>>
>

Mime
View raw message