Return-Path: 
 <user-return-16457-apmail-geronimo-user-archive=geronimo.apache.org@geronimo.apache.org>
X-Original-To: apmail-geronimo-user-archive@www.apache.org
Delivered-To: apmail-geronimo-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id E1B35C4D4
	for <apmail-geronimo-user-archive@www.apache.org>;
 Tue, 18 Jun 2013 11:22:24 +0000 (UTC)
Received: (qmail 54570 invoked by uid 500); 18 Jun 2013 11:22:24 -0000
Delivered-To: apmail-geronimo-user-archive@geronimo.apache.org
Received: (qmail 54202 invoked by uid 500); 18 Jun 2013 11:22:16 -0000
Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:user-help@geronimo.apache.org>
list-unsubscribe: <mailto:user-unsubscribe@geronimo.apache.org>
List-Post: <mailto:user@geronimo.apache.org>
Reply-To: user@geronimo.apache.org
List-Id: <user.geronimo.apache.org>
Delivered-To: mailing list user@geronimo.apache.org
Received: (qmail 54175 invoked by uid 99); 18 Jun 2013 11:22:14 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Jun 2013 11:22:14 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of markawareham@gmail.com
 designates 209.85.217.169 as permitted sender)
Received: from [209.85.217.169] (HELO mail-lb0-f169.google.com)
 (209.85.217.169)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Jun 2013 11:22:09 +0000
Received: by mail-lb0-f169.google.com with SMTP id d10so3491218lbj.0
        for <user@geronimo.apache.org>; Tue, 18 Jun 2013 04:21:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=RvIZicMpa5DIkRXSQgUoyr0i/KhUNUCDzprdslTXQzc=;
        b=JIJ2oUBF0W+pymZrauWCb0m5HVTicVXOi7RTDS+2T35h0LRNy8u5SJYrVhrt8WmylI
         gHzouUX+yHf/fwbWIzomnc45MFDutpDLtzS6vcGl9inhUZYcXtJ91lLZ1U6S6flzM/VA
         KQgvvxBCIxSND+Ht02SmzhIQJkhlcwNSLhhjYr1EEfOwXF3QikaTwP9hQeXMSJZR3KNb
         eca+5aKeI4jKGUfXMFc5lXChCPyQR3TkX1Mlq2M4hzQ8iYek98va/Uedm18VEO9w8QWz
         xg3kFfuAyktSA6IZhrhr7XJJy+LUxqsZxxupDXgvaYPn6w3Bx+Go39fWBZTaW3PAcqEk
         iboQ==
MIME-Version: 1.0
X-Received: by 10.112.157.226 with SMTP id wp2mr855131lbb.65.1371554507620;
 Tue, 18 Jun 2013 04:21:47 -0700 (PDT)
Received: by 10.112.33.70 with HTTP; Tue, 18 Jun 2013 04:21:47 -0700 (PDT)
Date: Tue, 18 Jun 2013 12:21:47 +0100
Message-ID: 
 <CAGp62eNedB0XYQY1C9y4EF4Zkzt7i5Hc+nMo22pLzOoTJzatYg@mail.gmail.com>
Subject: Setting up 2.1 for development
From: Mark Wareham <markawareham@gmail.com>
To: user@geronimo.apache.org
Content-Type: multipart/alternative; boundary=001a11c347723786e604df6beb97
X-Virus-Checked: Checked by ClamAV on apache.org

--001a11c347723786e604df6beb97
Content-Type: text/plain; charset=ISO-8859-1

Is it possible to set up Geronimo 2.1 to run without the need to republish
when a JSP is changed?

In my eclipse server overview the option "no re-deployment when only JSP
files are updated" is blanked out. I have also tried setting development to
true in {geronimo home}\var\catalina\conf\config.xml

I am stuck with the current version (for now) and have lots of JSP/CSS
changes to make. Frequently publishing to test eats up a lot of time as
each publish takes a long time. I would like to somehow avoid having to
publish for these type of changes.

Thanks, Mark.

--001a11c347723786e604df6beb97
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div>Is it possible to set up Geronimo 2.1 to ru=
n without the need to republish when a JSP is changed?<br><br></div>In my e=
clipse server overview the option &quot;no re-deployment when only JSP file=
s are updated&quot; is blanked out. I have also tried setting development t=
o true in {geronimo home}\var\catalina\conf\config.xml<br>
<br></div>I am stuck with the current version (for now) and have lots of JS=
P/CSS changes to make. Frequently publishing to test eats up a lot of time =
as each publish takes a long time. I would like to somehow avoid having to =
publish for these type of changes.<br>
<br></div>Thanks, Mark.<br></div>

--001a11c347723786e604df6beb97--