Mailing-List: contact repository-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: repository@apache.org
Received-SPF: pass (nike.apache.org: local policy)
From: "Snitkovsky, Martin" <martin.snitkovsky@hp.com>
To: Brian Fox <brianf@sonatype.com>
CC: "repository@apache.org" <repository@apache.org>, John Casey
	<jdcasey@commonjava.org>, "Baram, Eliezer" <ebaram@hp.com>,
	"wink-dev@incubator.apache.org" <wink-dev@incubator.apache.org>
Date: Tue, 28 Jul 2009 04:33:27 +0000
Subject: RE: Nexus repository clean-up [Wink project]
Thread-Topic: Nexus repository clean-up [Wink project]
Thread-Index: AcoO7uMbXfjiROWjQiOikfoD9sjmvAATYtgw
Message-ID: 
 <2C60AA1B234AC84D8486DC6BA56275FC4980BB21B6@GVW1163EXB.americas.hpqcorp.net>
References: 
 <2C60AA1B234AC84D8486DC6BA56275FC498030E808@GVW1163EXB.americas.hpqcorp.net>
 	<4A65EB74.3090006@commonjava.org>
 <2C60AA1B234AC84D8486DC6BA56275FC49803AB684@GVW1163EXB.americas.hpqcorp.net>
 	<eb0f802d0907230719o16cbcf7cx5fa923539f2ec818@mail.gmail.com>
 	<eb0f802d0907241052g7fc9248and5df09ce63b12138@mail.gmail.com>
 	<e9b1dfc0907261449s49826eaelf97dc479ef01f396@mail.gmail.com>
 	<2C60AA1B234AC84D8486DC6BA56275FC4980BB1D2A@GVW1163EXB.americas.hpqcorp.net>
 <e9b1dfc0907271217u2b3c6cne543d94ff8b65657@mail.gmail.com>
In-Reply-To: <e9b1dfc0907271217u2b3c6cne543d94ff8b65657@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Thanks Brian, I will do this.=20


-----Original Message-----
From: Brian Fox [mailto:brianf@sonatype.com]=20
Sent: Monday, July 27, 2009 10:17 PM
To: Snitkovsky, Martin
Cc: repository@apache.org; John Casey; Baram, Eliezer
Subject: Re: Nexus repository clean-up [Wink project]

Ok now I see the problem. Apache Wink is not officially configured to
use the new repository. The various build machines have permissions to
deploy snapshots, but if the project is not setup, naturally none of
the committers have any extra permissions.

To get converted, you need to file a subtask here:
https://issues.apache.org/jira/browse/INFRA-1896

On Mon, Jul 27, 2009 at 1:53 AM, Snitkovsky,
Martin<martin.snitkovsky@hp.com> wrote:
> Hi Brian,
> Sorry for not being specific - what I needed was an ability to manually r=
emove old snapshots.
> Btw - I failed to remove old snapshots via Nexus Repository Manager =A0(l=
ogged in with my people.apache.org credentials)
> =A0 =A0 =A0my user is 'martins' =A0- just in case you need it to grant re=
move permissions.
>
> Thanks for your help.
>
> --Martin.
>
> -----Original Message-----
> From: Brian Fox [mailto:brianf@sonatype.com]
> Sent: Monday, July 27, 2009 12:49 AM
> To: repository@apache.org
> Cc: Snitkovsky, Martin; John Casey; Baram, Eliezer
> Subject: Re: Nexus repository clean-up [Wink project]
>
> Are my emails getting through at all?
>
> On Fri, Jul 24, 2009 at 1:52 PM, Brian Fox<brianf@infinity.nu> wrote:
>> Ping?
>>
>> On Thu, Jul 23, 2009 at 10:19 AM, Brian Fox<brianf@infinity.nu> wrote:
>>> Hi Martin,
>>> Can you be more specific?
>>>
>>> First, no release artifacts can ever be removed from the repository.
>>> This is a tenet of Maven..and frankly even if they were removed from
>>> the Apache repo, they will not be removed from Central or all the
>>> mirrors of it.
>>>
>>> That leaves only snapshots. The snapshots hosted in the nexus
>>> repository are cleaned up when: 1) there are more than two copies
>>> older than 5 days or 2) when a release of the same version is
>>> performed. (ie 1.0-SNAPSHOTS are removed when the system sees 1.0 is
>>> released).
>>>
>>> All committers on a given project have the permissions to remove
>>> snapshots if they want, but only admins have permissions to remove
>>> release artifacts.
>>>
>>> So given that you can already manage snapshots, and removing releases
>>> is a non-starter, is there something else we need to allow that I'm
>>> missing?
>>>
>>> --Brian
>>>
>>>
>>> On Wed, Jul 22, 2009 at 3:56 AM, Snitkovsky,
>>> Martin<martin.snitkovsky@hp.com> wrote:
>>>> Hi John/Brian,
>>>> We still have issues with repository clean-up.
>>>> We have changed project version name, which created all new set of art=
ifacts. All old artifacts are not relevant anymore and should be removed fr=
om repository.
>>>>
>>>> I understand that there is some kind of auto-cleanup aimed to remove o=
ld artifacts, but I don't know when it runs and what is cleaned.
>>>>
>>>> Is it possible/acceptable to provide us credentials for removing irrel=
evant artifacts, or only you guys are responsible for such actions.
>>>>
>>>> Thanks
>>>> Martin
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: John Casey [mailto:jdcasey@commonjava.org]
>>>> Sent: Tuesday, July 21, 2009 7:23 PM
>>>> To: Snitkovsky, Martin
>>>> Subject: Re: Nexus repository clean-up [Wink project]
>>>>
>>>> I brought this up to Brian and he mentioned that he's been trying to
>>>> reach you on the repository@ mailing list about this for some time, wi=
th
>>>> no response.
>>>>
>>>> I guess if this is still something you'd like to solve, let's move the
>>>> discussion over there.
>>>>
>>>> Thanks,
>>>>
>>>> -john
>>>>
>>>> Snitkovsky, Martin wrote:
>>>>> Hi,
>>>>>
>>>>> I am a member in Apache Wink project. We are using Apache Nexus
>>>>> repository https://repository.apache.org
>>>>>
>>>>> to =A0deploy Wink artifacts.
>>>>>
>>>>>
>>>>>
>>>>> =A0From time to time, i would like to perform repository clean-up =A0=
(e.g.
>>>>> remove old artifacts, corrupted files) and I am wondering what is
>>>>> acceptable procedure for this.
>>>>>
>>>>>
>>>>>
>>>>> */ /*Wink home page: http://cwiki.apache.org/confluence/display/WINK/=
Index
>>>>>
>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Martin
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>