From users-return-8101-apmail-continuum-users-archive=continuum.apache.org@continuum.apache.org Wed Jun 30 04:18:24 2010 Return-Path: Delivered-To: apmail-continuum-users-archive@www.apache.org Received: (qmail 33928 invoked from network); 30 Jun 2010 04:18:24 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 30 Jun 2010 04:18:24 -0000 Received: (qmail 19753 invoked by uid 500); 30 Jun 2010 04:18:23 -0000 Delivered-To: apmail-continuum-users-archive@continuum.apache.org Received: (qmail 19356 invoked by uid 500); 30 Jun 2010 04:18:21 -0000 Mailing-List: contact users-help@continuum.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@continuum.apache.org Delivered-To: mailing list users@continuum.apache.org Received: (qmail 19348 invoked by uid 99); 30 Jun 2010 04:18:19 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Jun 2010 04:18:19 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,SPF_HELO_PASS,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Jun 2010 04:18:12 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1OTokA-000181-T0 for users@continuum.apache.org; Tue, 29 Jun 2010 21:17:50 -0700 Message-ID: <29030739.post@talk.nabble.com> Date: Tue, 29 Jun 2010 21:17:50 -0700 (PDT) From: sk07 To: users@continuum.apache.org Subject: Re: how to set continuum build fresh In-Reply-To: <29030380.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: s.sindhukumar07@gmail.com References: <29020722.post@talk.nabble.com> <29030380.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org Wendy Smoak-3 wrote: > > On Tue, Jun 29, 2010 at 3:02 AM, sk07 wrote: > >> say i build a war file from a trunk for a project n name it as Project >> 1-snapshot version 1. n the project go live. when there is enhancement, >> developer make necessary changes n update the svn repo. now, for next >> release i can trigger to build the file again. how to keep existing war >> file >> build via continuum and new war file which will get build by triggering >> the >> build button in continuum? is the a way where i can make a new project >> name, >> example Project 1 - snapshot 2 in continuum? getting same project with >> different version (diff war file)? or the only way is i manually moved >> the >> existing war file to a folder, only then trigger build via continuum? > > It sounds like you are not yet deploying your artifacts to a remote > repository. That's where you normally store releases when using > Maven. Take a look at Apache Archiva for a repository manager (but > you can start with a simple filesystem.) At a minimum, set > in your project pom and change the build > definition to "clean deploy". > > There is also a release process built into Maven and Continuum that > will tag your svn repository and change the version numbers for you. > > Is the requirement really to put the old releases under version > control (in svn) or just to keep them around? > > -- > Wendy > > Hi Wendy, Thanks for the reply. I'm using the build.xml, ant engine. In that case, I need to ask the developer to configure the build.xml (configuration file which buil the war file) to have define the filesystem to the war can be stored in version? And I do not want to change it to clean deploy, because deployment will be done by my superior. All I want is continuumm build and keep the war in versions (in historical order, maybe the last including the later war file). The reason being is we can revert back to old war, by deploying the old war file if needed. Dont think wants to tag the svn because that would be hassle for developer. Any idea how to do this? Thanks Wendy. Rgrds, sk ------------------------------------------------------------------------------------------------------ right now whenever i trigger build.xml to build war file the war get build at the following directory /usr/local/apache-tomcat-6.0.18-1/bin/data/working-directory its creates folder by number (1,2) under the working-directory folder and war being stored there. however, each time when i trigger, a new war being created and the folder (numbering) get incremented but the previous folder is missing, guess it overwrites. example, when 1st trigger the war file stored in folder '1', 2nd time triggering it, it will then created folder '2' with war file in it but I believe the previous folder '1' gets removed or deleted in the process because i dont see it anymore after triggerring it 2nd time. please advide. thanks. rgrds, sk -- View this message in context: http://old.nabble.com/how-to-set-continuum-build-fresh-%3Ccheck-out-frm-svn%3E-tp29020722p29030739.html Sent from the Continuum - Users mailing list archive at Nabble.com.