How to use the same staging repo

[Lukasz Lenart <lu...@googlemail.com>]

Hi,

Is is possible to use the same staging repository instead each time
creating new one?

Each time I launch mvn release:perform a new staging repository is
created. If during release:perform an error occur I must drop the
repository and new one will be created when I relaunch the
release:perform command. Maybe there is a switch to point to the same
repository again?


Thanks in advance
-- 
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
Kapituła Javarsovia 2010 http://javarsovia.pl

Re: How to use the same staging repo

[Brian Fox <br...@sonatype.com>]

In that case, if you don't close the existing repo, it will allow new
artifacts from the same user, ip and group (struts) so you should be able to
do what you're looking for. Once you close it though, it's sealed.

On Thu, Jul 15, 2010 at 12:53 PM, Lukasz Lenart <
lukasz.lenart@googlemail.com> wrote:

> 2010/7/15 Brian Fox <br...@sonatype.com>:
> > Having a separate repository is the intent, each time you stage, the
> > contents are different and it's immutable on purpose. Why do you want to
> > change the content but not change the repo?
>
> The content is the same or should be. Maybe by example will be better.
>
> I'm preparing a Struts 2 release which contains many modules like
> core, plugins, archetypes and so on. Quite often during release
> process something goes wrong, test didn't pass (but during release
> preparation passed), some strange access denied to file system,
> network issues and so on. Each time I must start process over again
> and upload all the parts that already were good and in the staging
> repository. But when I start over, a new staging repository is
> created, this didn't allow to me prepare the release in small chunks.
>
> With my current network connection it takes around 2h to upload all
> the elements.
>
>
> Regards
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
> Kapituła Javarsovia 2010 http://javarsovia.pl
>

Re: How to use the same staging repo

[Lukasz Lenart <lu...@googlemail.com>]

2010/7/15 Brian Fox <br...@sonatype.com>:
> Having a separate repository is the intent, each time you stage, the
> contents are different and it's immutable on purpose. Why do you want to
> change the content but not change the repo?

The content is the same or should be. Maybe by example will be better.

I'm preparing a Struts 2 release which contains many modules like
core, plugins, archetypes and so on. Quite often during release
process something goes wrong, test didn't pass (but during release
preparation passed), some strange access denied to file system,
network issues and so on. Each time I must start process over again
and upload all the parts that already were good and in the staging
repository. But when I start over, a new staging repository is
created, this didn't allow to me prepare the release in small chunks.

With my current network connection it takes around 2h to upload all
the elements.


Regards
-- 
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
Kapituła Javarsovia 2010 http://javarsovia.pl

Re: How to use the same staging repo

[Brian Fox <br...@sonatype.com>]

Having a separate repository is the intent, each time you stage, the
contents are different and it's immutable on purpose. Why do you want to
change the content but not change the repo?

On Thu, Jul 15, 2010 at 5:07 AM, Lukasz Lenart <lukasz.lenart@googlemail.com
> wrote:

> Hi,
>
> Is is possible to use the same staging repository instead each time
> creating new one?
>
> Each time I launch mvn release:perform a new staging repository is
> created. If during release:perform an error occur I must drop the
> repository and new one will be created when I relaunch the
> release:perform command. Maybe there is a switch to point to the same
> repository again?
>
>
> Thanks in advance
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
> Kapituła Javarsovia 2010 http://javarsovia.pl
>