On 8/1/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 8/1/06, Adam Winer <[EMAIL PROTECTED]> wrote:

> All that I'd like is that we have a Maven repository
> that is explicitly not a snapshot repository, because
> Maven treats snapshot repositories and release
> repositories differently.

By process of elimination, the Apache 'snapshot' repository turns into
the 'snapshot, test build, and release staging' repository.  Only
releases sanctioned by PMCs and destined for ibiblio can go in the
release repo, so everything else lands in the other one.

For example, Struts has a couple of releases in
m2-snapshot-repository.  These were beta quality releases that had
some issue preventing wider distribution.  I'm on the [EMAIL PROTECTED]
list, and no one has ever questioned our placing other-than-snapshots
in this repo.

There just isn't anywhere else to put them, unless you establish a
separate repo.  That's easy enough to do, and I know it *is* being
done-- MyFaces has a staging repository on myfaces.zones.a.o, but I
wouldn't recommend doing it one-off for trinidad.

I'm not following incubator-general closely, does it sound like
they're going to establish a separate Maven repository for incubator
artifacts?

I agree, it doesn't make a lick of sense it create a one-off
trinidad repos.  It would be a good thing to have a "don't push
to ibibilio but not snapshot" repository.  Incubator releases could
go there;  also things like the MyFaces sandbox could go there.
And the Struts beta releases could go there too.

It's not so bad just cramming everything that is
not real production Apache software into the snapshot
repos;  this would only be an incremental improvement,
but if there's going to be lots of call for non-snapshot
JARs in a snapshot repos, it'd be nice to have a real
place to put them.

-- Adam

Reply via email to