On 3/15/07, Davanum Srinivas <[EMAIL PROTECTED]> 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)[EMAIL
PROTECTED]&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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
