Mailing-List: contact repository-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: repository@apache.org
Received-SPF: pass (asf.osuosl.org: domain of flamefew@gmail.com designates
 64.233.166.179 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=PHotqGDOO4g1POf4V/xN9Pry7NHcsShG0xr3+C3A4hvq/TEWcBw1MpzGnt7nz0ug4qHzgDEugqtoPnVZ2BW5MNKkKbIZRU2oKs94o9zlZTlPEYncx0dmdrITpkmvlMThaM3SkgxrZXNNJd4SEuEaopDKzFLFel+HAtiLtHoM19c=
Message-ID: <31cc37360604041601g15a15f2fqd3194cc1bdb0b0@mail.gmail.com>
Date: Tue, 4 Apr 2006 16:01:47 -0700
From: "Henri Yandell" <flamefew@gmail.com>
To: repository@apache.org
Subject: Re: sources + javadocs
In-Reply-To: <Pine.GSO.4.44.0604042359110.346-100000@castor.cs.uu.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <31cc37360604041458q1da1216h1a8b249a99789099@mail.gmail.com>
	 <Pine.GSO.4.44.0604042359110.346-100000@castor.cs.uu.nl>

On 4/4/06, Henk P. Penning <henkp@cs.uu.nl> wrote:
> On Tue, 4 Apr 2006, Henri Yandell wrote:
>
> > Date: Tue, 4 Apr 2006 14:58:11 -0700
> > From: Henri Yandell <flamefew@gmail.com>
> > To: repository@apache.org
> > Subject: Re: sources + javadocs
> >
> > On 4/4/06, Henk P. Penning <henkp@cs.uu.nl> wrote:
> > > On Tue, 4 Apr 2006, Henri Yandell wrote:
> > >
> > > > Date: Tue, 4 Apr 2006 13:56:25 -0700
> > > > From: Henri Yandell <flamefew@gmail.com>
> > > > To: repository@apache.org
> > > > Subject: sources + javadocs
> > > >
> > > > It's all the rage to deploy sources and javadocs to your repos nowa=
days.
> > > >
> > > > Anyone mind if I go ahead and see how much I can script in the curr=
ent
> > > > repos such that the sources and javadocs are pulled out of the .zip
> > > > files in the archive and sucked over into the maven repo?
> > >
> > > Hen,
> > >
> > >   The rules in maven-repository/README.txt :
> > >
> > >     - only deploy releases voted on by the PMC
> >
> > Out of interest, are we meant to remove ones that weren't voted on?
>
>   I don't know too much about this rule. It is a general principle
>   for the ASF regarding '/dist/'.
>
> > >     - sign all artifacts and POMs (currently, this is a manual step)
> > >     - never deploy snapshots or development releases to this reposito=
ry
> > >     - ensure that if a release is deleted from /dist/, it is removed =
from
> > >       here completely also (excluding archiving)
> >
> > Which would be a bad thing from a user point of view (I assume the
> > rsync is deleting at ibiblio if we delete).
>
>   No. IIRC ibiblio offered a mirror under condition they wouldn't
>   have to delete.

Right, thought that was something they were hot on.

>   Please take this point (automatic cleanup) very serious.
>
>   The java-repository is a big mess and this shouldn't be repeated
>   in the maven-repository. Writing scripts to install stuff is easy ;
>   writing stuff that cleans up is not so easy.
>
>   First solve the not-so-easy part, before you solve the easy part.

I thought the solution was supposed to be easy. Move it out of dist.

>   The idea for maven-repository was to have cleanup-hooks :
>   a pointer from the artifact to the source in 'dist/' ;
>   when the source goes out, the artifact can be removed.
>   I haven't seen that idea gone into practice yet, despite
>   good intentions and promises.

Does the pointer even need to remain? The chief problem is that the
ibiblio sync would delete it (I thought). So would need to stop the
--delete if it's happening (or whatever the flag is).

>   Take a look at java-repository ; what percentage of the stuff
>   there is obsolete (given its also in archive.apache.org/dist) ?

Two problems with this question:

1) Nothing in there is obsolete. It has a different use case than the
rest of dist/.
2) Nothing in there is in archive.apache.org/dist (afaik). One has jar
files, the other tends to be zips/tar.gzs.

What's the cause of the need to move to archive - mirroring or disk
location? If just mirroring, can we just filter out those directories
from being mirrored? (no idea if Maven/Ant would want this, but I
don't know of any current reason to mirror them).

Hen