Return-Path: Delivered-To: apmail-incubator-general-archive@www.apache.org Received: (qmail 7634 invoked from network); 30 Aug 2006 16:51:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 30 Aug 2006 16:51:53 -0000 Received: (qmail 58356 invoked by uid 500); 30 Aug 2006 16:51:51 -0000 Delivered-To: apmail-incubator-general-archive@incubator.apache.org Received: (qmail 58232 invoked by uid 500); 30 Aug 2006 16:51:50 -0000 Mailing-List: contact general-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@incubator.apache.org Delivered-To: mailing list general@incubator.apache.org Received: (qmail 58215 invoked by uid 99); 30 Aug 2006 16:51:50 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Aug 2006 09:51:50 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [204.127.200.84] (HELO sccrmhc14.comcast.net) (204.127.200.84) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Aug 2006 09:51:49 -0700 Received: from [192.168.3.100] (c-71-205-191-164.hsd1.mi.comcast.net[71.205.191.164]) by comcast.net (sccrmhc14) with ESMTP id <2006083016512701400kpnlde>; Wed, 30 Aug 2006 16:51:27 +0000 Message-ID: <44F5C24E.60305@envoisolutions.com> Date: Wed, 30 Aug 2006 12:52:30 -0400 From: Dan Diephouse User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: general@incubator.apache.org Subject: Re: [policy] incubating projects and maven repositories v1.0 References: <44F5B858.9020100@envoisolutions.com> <19e0530f0608300935g55a3ae3bm11252cf66ee22c5e@mail.gmail.com> In-Reply-To: <19e0530f0608300935g55a3ae3bm11252cf66ee22c5e@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Why? Davanum Srinivas wrote: > If it comes to a VOTE, i'd vote -1 on automatic syncing of incubator > artifacts to maven central repo. > > -- dims > > On 8/30/06, Dan Diephouse wrote: >> Jason van Zyl wrote: >> > Hi, >> > >> > It looks like people objected to creating another mailing list for >> > policy so I just used [policy] as Robert did in a previous message. >> > >> > Henri has setup Maven repositories for the incubator and there is a >> > document which is an attempt to describe the current setup here: >> > >> > http://www.apache.org/dev/repository-faq.html >> > >> > I think that everyone agrees that a separate repository for incubating >> > projects is a good idea as >> > >> > 1) you can clearly see what incubator artifacts have been created >> > 2) we can perform analysis and create reports for incubator artifacts >> > easily (using Archiva, the maven repository manager) >> > 3) separating the administration duties of the incubator repository is >> > a good idea I think. This might involve a different instance of >> > Archiva and/or different people looking after the respective >> repositories >> > >> > I haven't looked at all the projects using Maven in the incubator but >> > cxf, the one I'm most involved with, looks like its settling on >> > versions like: >> > >> > 2.0-incubator-SNAPSHOT >> > >> > So the repository is clearly separated, and from a dependency element >> > in a Maven POM you can clearly see it's an incubator version. >> > >> > There was discussion that incubator repository would not be sync'd to >> > the central repository but I don't really see much point in this. A >> > few folks with incubating projects have voiced concerns that they >> > don't want to see their projects be taken out of circulation in the >> > central repository because they are incubating. If each and every >> > incubating project has a version for each artifact like that above >> > then it will be fairly clear that it's from the incubator. Moreso then >> > if you just had a repository definition pointing at the incubator >> > repository. >> > >> > Also someone may make an repository request to place an incubator >> > artifact in the central repository and at this point a policy mandated >> > here would conflict with someone's right to redistribute artifacts >> > created in the incubator. I don't really want to get into the business >> > of policing repository requests. I think it is in the best interests >> > of the incubating projects to have the incubator repository sync'd to >> > Maven's central repository. The source of artifacts for incubating >> > projects is clear from the version so I don't think there will be any >> > confusion by consumers of these artifacts and as such I don't really >> > see any downside to allowing the sync to Maven's central repository. >> > >> > Thoughts? >> > >> > Jason van Zyl >> > jason@maven.org >> >> +1. >> >> - Dan >> >> -- >> Dan Diephouse >> Envoi Solutions >> http://envoisolutions.com >> http://netzooid.com/blog >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org >> For additional commands, e-mail: general-help@incubator.apache.org >> >> > > -- Dan Diephouse Envoi Solutions http://envoisolutions.com http://netzooid.com/blog --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.org