Return-Path: Delivered-To: apmail-maven-continuum-users-archive@www.apache.org Received: (qmail 83842 invoked from network); 16 Jun 2006 16:49:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 16 Jun 2006 16:49:27 -0000 Received: (qmail 48915 invoked by uid 500); 16 Jun 2006 16:49:26 -0000 Delivered-To: apmail-maven-continuum-users-archive@maven.apache.org Received: (qmail 48896 invoked by uid 500); 16 Jun 2006 16:49:25 -0000 Mailing-List: contact continuum-users-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: continuum-users@maven.apache.org Delivered-To: mailing list continuum-users@maven.apache.org Received: (qmail 48885 invoked by uid 99); 16 Jun 2006 16:49:25 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Jun 2006 09:49:25 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [62.193.206.9] (HELO webmail9.amenworld.com) (62.193.206.9) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 16 Jun 2006 09:49:24 -0700 Received: (qmail 23671 invoked from network); 16 Jun 2006 16:49:10 -0000 Received: from 74.189.97-84.rev.gaoland.net (HELO ?127.0.0.1?) (84.97.189.74) by 0 with SMTP; 16 Jun 2006 16:49:10 -0000 Message-ID: <4492E0F9.7000704@venisse.net> Date: Fri, 16 Jun 2006 18:48:57 +0200 From: Emmanuel Venisse User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: continuum-users@maven.apache.org Subject: Re: Automatically deploy snapshot bulds to remote repo References: <4902069.post@talk.nabble.com> <4492D511.5070006@venisse.net> <4903614.post@talk.nabble.com> In-Reply-To: <4903614.post@talk.nabble.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N if you don't have scm activity on a project that don't have in dev, continuum won't build it so it won't deploy artifacts. Emmanuel ArneD a �crit : > Thank you, Emmanuel. > > > Emmanuel Venisse wrote: >> yes, goals to use is "clean deploy", but continuum don't know what is a >> project in dev and a >> released project. Generally, when we release a project, the code is tagged >> and the code in trunk is >> updated to an incremented snapshot version. >> > > "clean deploy" works well if you always have a snapshot version under > development. But that's not the case for every project. Sometimes you > release a version, and do not have plans for a future release yet. You do > not know, will the next rel. be a major or a minor release? Wiill there be a > next release at all? etc. > > At the moment, I only see one solution, but I do not like it very much: > - Only keep "snapshot" versions in Continuum. > - Set build goals to "clean deploy" > - Make sure that Continuum only deploys snapshot versions by defining only > the snapshot repository in the distributionManagement section of the pom. > The release repository would be defined within a profile section that has to > explicitly be enabled, e.g. by parameter -Drelease=true. > > That way the deployment of the release version can only be done manually, > when the user explicitly sets the -Drelease=true parameter. If, by mistake, > a release version is in Continuum, the build will fail because of the > missing distributionManagement information. > > Do you have a better idea? > > Thanks again > Arne > > -- > View this message in context: http://www.nabble.com/Automatically-deploy-snapshot-bulds-to-remote-repo-t1798808.html#a4903614 > Sent from the Continuum - Users forum at Nabble.com. > > > >