Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <NBBBJGEAGJAKLIDBKJOPMEALEPAD.noel@devtech.com>
MIME-Version: 1.0
From: "Noel J. Bergman" <noel@devtech.com>
To: <general@incubator.apache.org>
Subject: RE: maven-repository cont.
Date: Sun, 1 Jun 2008 23:33:55 -0400
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
In-Reply-To: <88f6e29a0806011145h489ab1e8r5c14979ee8564e00@mail.gmail.com>
Importance: Normal

Bernd Fondermann wrote:

> >  "While incubation status is not necessarily a reflection of the
> >   completeness or stability of the code, it does indicate that
> >   the project has yet to be fully endorsed by the ASF."

> Let's say, the Incubator publishes a release 'foo-incubating-0.9-src.zip'
of
> podling 'foo'. Say, the released code is stable and has everything we
would
> want from a release. Later, the project gets cancelled while in
incubation,
> for diversity reasons, lack of interest, whatever. So we have (a) a
regular
> release of (b) a failed incubating project.  The _release_ refers to the
> released code, while the podling failed, which the _disclaimer_ is good
for.

Simply put: Maven circumvents the disclaimer.  Users never see it, may never
be aware that they have such dependencies.  We're trying to address that
problem.

	--- Noel


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org