Return-Path: X-Original-To: apmail-tomcat-users-archive@www.apache.org Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1056482F2 for ; Mon, 8 Aug 2011 09:16:39 +0000 (UTC) Received: (qmail 85022 invoked by uid 500); 8 Aug 2011 09:16:34 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 84611 invoked by uid 500); 8 Aug 2011 09:16:21 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 84598 invoked by uid 99); 8 Aug 2011 09:16:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Aug 2011 09:16:18 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of pid@pidster.com designates 74.125.82.41 as permitted sender) Received: from [74.125.82.41] (HELO mail-ww0-f41.google.com) (74.125.82.41) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Aug 2011 09:16:11 +0000 Received: by wwj26 with SMTP id 26so1903967wwj.0 for ; Mon, 08 Aug 2011 02:15:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pidster.com; s=google; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:x-enigmail-version:openpgp :content-type:content-transfer-encoding; bh=sVQ4Zrr8nsL3tTBoGpxVCqTHHuxVfYVtzoNK26iC3sk=; b=Ui2q+jfSEtWO/wmj2U2QoAd5omeWqSWBB9Zdu7CM6CfL2jhI1fdd+E1sMu3l9t+53i qrFbzxO+diwkwa3Xj7CLPjlLoQPnTS1Amoj+LkO4BRvFIlCgHdKteg4K/rLQrNRwF+IZ a9JgrhvPMK4Mu4QPCxnDWh6qtL6Jk19X3ynJw= Received: by 10.216.1.9 with SMTP id 9mr2177428wec.2.1312794949569; Mon, 08 Aug 2011 02:15:49 -0700 (PDT) Received: from Asura.local (cpc10-lewi14-2-0-cust355.2-4.cable.virginmedia.com [82.4.249.100]) by mx.google.com with ESMTPS id b47sm1255667wed.46.2011.08.08.02.15.47 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 08 Aug 2011 02:15:48 -0700 (PDT) Message-ID: <4E3FA945.10307@pidster.com> Date: Mon, 08 Aug 2011 10:15:49 +0100 From: Pid Organization: Pidster Inc User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:5.0) Gecko/20110624 Thunderbird/5.0 MIME-Version: 1.0 To: Tomcat Users List Subject: Re: Deploying ROOT Context for variable .war filename References: <32216447.post@talk.nabble.com> In-Reply-To: <32216447.post@talk.nabble.com> X-Enigmail-Version: 1.2 OpenPGP: id=62590808 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 08/08/2011 09:56, jenskreidler wrote: > > Hi tomcat-users, > > using tomcat 7, is it possible to mount the ROOT context path for a .war > file, where the .war file will have a variable file name, i.e. building a > .war by a continuous integration server. > For example, you get a myapp-3.2.0-20110809-build254.war, next day a > myapp-3.2.0-20110810-build255.war and so on. > I'd like to convene with this ci-build ordering, the war file naming scheme > and to automatic deploy the newest .war every night at the tomcat's ROOT > context. > > Thanks in advance, > > jenskreidler > Use: ROOT##version.war Where 'version' is an orderable string. p --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org