From dev-return-6864-apmail-continuum-dev-archive=continuum.apache.org@continuum.apache.org Tue Apr 08 12:01:20 2008 Return-Path: Delivered-To: apmail-continuum-dev-archive@www.apache.org Received: (qmail 78932 invoked from network); 8 Apr 2008 12:01:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 8 Apr 2008 12:01:20 -0000 Received: (qmail 85203 invoked by uid 500); 8 Apr 2008 12:01:21 -0000 Delivered-To: apmail-continuum-dev-archive@continuum.apache.org Received: (qmail 85052 invoked by uid 500); 8 Apr 2008 12:01:20 -0000 Mailing-List: contact dev-help@continuum.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@continuum.apache.org Delivered-To: mailing list dev@continuum.apache.org Received: (qmail 85043 invoked by uid 99); 8 Apr 2008 12:01:20 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Apr 2008 05:01:20 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [210.50.30.235] (HELO mx05.syd.iprimus.net.au) (210.50.30.235) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Apr 2008 12:00:27 +0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ar4AAFr7+kc6sgja/2dsb2JhbAAIrB0 X-IronPort-AV: E=Sophos;i="4.25,623,1199624400"; d="scan'208";a="106995686" Received: from 218.080.dsl.syd.iprimus.net.au (HELO [192.168.237.213]) ([58.178.8.218]) by smtp05.syd.iprimus.net.au with ESMTP; 08 Apr 2008 22:00:42 +1000 Message-Id: <7784E365-0F9E-4986-873E-F23C6ED49033@apache.org> From: Brett Porter To: dev@continuum.apache.org In-Reply-To: <47FB3B8E.8070609@fjas.no> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Subject: Re: Why is the release functionality provided on the projectGroup level only? Date: Tue, 8 Apr 2008 22:00:35 +1000 References: <47FB3B8E.8070609@fjas.no> X-Mailer: Apple Mail (2.919.2) X-Virus-Checked: Checked by ClamAV on apache.org On 08/04/2008, at 7:31 PM, Erik Drolshammer wrote: > Hi! > Why is the release functionality provided on the projectGroup level > only? > There is a release button on every individual project too - what behaviour were you expecting? > Drivers when choosing a groupIds > * groupId + artifactID should be equal to the java package > > * The directory structure of the project must match the java package > > * The groupId should thus follow SUN's Naming Conventions . (So do > not use camelCase!) > > * When adding a project in Continuum the groupId is used to put the > projects into projectGroups. > ** It is convenient to use projectGroups so simplify management of > build definitions. > ** The release functionality is provided on the projectGroup level, > so all projects in the same projectGroup are released together. > > ^ Does this correspond to the current best practices? Apart from the last statement, yes, I believe so. > > > Look for example at maven-plugins. They will all (by sorting by > groupId) be put in the same projectGroup. Imho, it is not likely > that all the plugins will be released together. Correct - you would release them using the individual one. However groups are usually formed by a reactor of more closely related builds. In truth, plugins doesn't follow the best practice because their trunk and tags are at a different level to the release. - Brett > > > -- > Regards > Erik Drolshammer > -- Brett Porter brett@apache.org http://blogs.exist.com/bporter/