Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
Received-SPF: pass (herse.apache.org: domain of davanum@gmail.com designates
 64.233.184.236 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=VoLzP6ZVtjROrLxkzP+EYBXfr8Tn4PO0TZJ5dwE8eRM6TzaKoTJPirrn+/kwup7ZAaNS+CotA6klo2bjjB/V/A6FgNwwC6MB1i5JVpC9QIqWTz6UlM0EXMnnyCjhmeFK5OkaSo00wVoY63V0kqkxcjfTaCS30BqaB6BPj/CwG6k=
Message-ID: <19e0530f0703151019m410d350cy808b56910ade3d7b@mail.gmail.com>
Date: Thu, 15 Mar 2007 13:19:51 -0400
From: "Davanum Srinivas" <davanum@gmail.com>
Reply-To: dims@apache.org
To: general@incubator.apache.org
Subject: Re: Killing the incubator m2 repository
In-Reply-To: <7b3355cb0703151011p72ab31afke7e869d74fd6c651@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <NBBBJGEAGJAKLIDBKJOPCEIPNIAC.noel@devtech.com>
	 <200703151127.37050.daniel.kulp@iona.com>
	 <19e0530f0703150833n3cfe8928xd5516285811fc2be@mail.gmail.com>
	 <200703151200.03582.daniel.kulp@iona.com>
	 <19e0530f0703150911u783d8b77i42c5818fe08c20b2@mail.gmail.com>
	 <7b3355cb0703150945n35a61aecwf28c41aa247a123e@mail.gmail.com>
	 <19e0530f0703150950q4bf7d632x50b0b9b2e45ef431@mail.gmail.com>
	 <7b3355cb0703151011p72ab31afke7e869d74fd6c651@mail.gmail.com>

Bruce,

can you show me a single podling web site where they provide guidance
on how exactly to use the podling artifacts? and hence "overcome the
ill-documentation" caused by the incubator process. Anyone who has
even barely touched m2 knows how to add a new repo to his pom.xml so
this is a non-issue.

-- dims

On 3/15/07, Bruce Snyder <bruce.snyder@gmail.com> wrote:
> On 3/15/07, Davanum Srinivas <davanum@gmail.com> wrote:
> > Because projects get killed/nuked as they don't have enough legs to
> > stand on literally. You are assuming that every project makes it. It
> > doesn't. We have to let people know that they are making a conscious
> > choice by making it difficult.
>
> I'm not assuming anything. Users are well aware that projects reside
> in the Incubator - especially with 'incubating' in the project
> version. I even think Niclas's suggestion to also put 'incubator' in
> the package name is a good idea because it would force the Maven
> groupId element to be org.apache.incubator.<project>.
>
> I still don't understand the benefit of an Incubator policy that force
> users to overcome ill-documented (or even undocumented) hurdles like
> the Maven repo policy. Whenever I explain it to someone (and I have to
> do this a lot) they ask me why it's so difficult and non-standard. I
> explain the rationale behind the policy and they tell me it's just an
> unnecessary pain - that they're clearly aware the project resides in
> the Incubator.
>
> Bruce
> --
> perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
> );'
>
> Apache Geronimo - http://geronimo.apache.org/
> Apache ActiveMQ - http://activemq.org/
> Apache ServiceMix - http://servicemix.org/
> Castor - http://castor.org/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>


-- 
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers

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