On 1:59 PM, Jeffrey Janner wrote:
-Original Message-
From: Terence M. Bandoian [mailto:tere...@tmbsw.com]
Sent: Saturday, February 18, 2012 5:14 PM
To: Tomcat Users List
Subject: Re: generic deployment question
On 1:59 PM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE
> -Original Message-
> From: Terence M. Bandoian [mailto:tere...@tmbsw.com]
> Sent: Saturday, February 18, 2012 5:14 PM
> To: Tomcat Users List
> Subject: Re: generic deployment question
>
> On 1:59 PM, Christopher Schultz wrote:
> > -BEGIN PGP SIGNED
2012/2/17 Jeffrey Janner :
> Assume latest Tomcat 6.x for current deployment, and 7.x for future
> deployments.
>
> I host an app for a couple of dozen customers. Naturally, upgrade time can
> be a bit of a pain, and I'd like to simplify things.
> Assuming that all the customer-specific informat
On 1:59 PM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeffrey,
On 2/17/12 10:45 AM, Jeffrey Janner wrote:
Thanks. I was under the impression that Tomcat normally explodes
the war files when you drop them into the webapps folder, though I
know you can disable th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeffrey,
On 2/17/12 10:45 AM, Jeffrey Janner wrote:
> Thanks. I was under the impression that Tomcat normally explodes
> the war files when you drop them into the webapps folder, though I
> know you can disable that feature.
I was suggesting that yo
> -Original Message-
> From: Pid [mailto:p...@pidster.com]
> Sent: Friday, February 17, 2012 2:49 AM
> To: Tomcat Users List
> Subject: Re: generic deployment question
>
> On 16/02/2012 21:12, Jeffrey Janner wrote:
> > Assume latest Tomcat 6.x for current dep
> -Original Message-
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Sent: Friday, February 17, 2012 9:36 AM
> To: Tomcat Users List
> Subject: Re: generic deployment question
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Je
> -Original Message-
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Sent: Friday, February 17, 2012 9:42 AM
> To: Tomcat Users List
> Subject: Re: generic deployment question
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Jef
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeffrey,
On 2/17/12 10:39 AM, Jeffrey Janner wrote:
> That's actually the current deployment mechanism that I'm wanting
> to get changed. Unfortunately right now, there are some
> application related config files buried under the WEB-INF directory
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeffrey,
On 2/17/12 10:36 AM, Christopher Schultz wrote:
> Jeffrey,
>
> On 2/16/12 4:12 PM, Jeffrey Janner wrote:
>> I host an app for a couple of dozen customers. Naturally,
>> upgrade time can be a bit of a pain, and I'd like to simplify
>> things
> -Original Message-
> From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com]
> Sent: Friday, February 17, 2012 9:22 AM
> To: Tomcat Users List
> Subject: RE: generic deployment question
>
> > From: Jeffrey Janner [mailto:jeffrey.jan...@polydyne.com]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeffrey,
On 2/16/12 4:12 PM, Jeffrey Janner wrote:
> I host an app for a couple of dozen customers. Naturally, upgrade
> time can be a bit of a pain, and I'd like to simplify things.
> Assuming that all the customer-specific information (DB connect
> From: Jeffrey Janner [mailto:jeffrey.jan...@polydyne.com]
> Subject: RE: generic deployment question
> But, really, I just wanted to know if my original suggestion
> would cause issues with Tomcat.
As Pid stated, it might work, but it's not a guaranteed deployment mechanis
> -Original Message-
> From: André Warnier [mailto:a...@ice-sa.com]
> Sent: Thursday, February 16, 2012 3:32 PM
> To: Tomcat Users List
> Subject: Re: generic deployment question
>
> Jeffrey Janner wrote:
> > Assume latest Tomcat 6.x for current dep
On 16/02/2012 21:12, Jeffrey Janner wrote:
> Assume latest Tomcat 6.x for current deployment, and 7.x for future
> deployments.
>
> I host an app for a couple of dozen customers. Naturally, upgrade time can
> be a bit of a pain, and I'd like to simplify things.
> Assuming that all the customer-
Jeffrey Janner wrote:
Assume latest Tomcat 6.x for current deployment, and 7.x for future deployments.
I host an app for a couple of dozen customers. Naturally, upgrade time can be
a bit of a pain,
why ?
and I'd like to simplify things.
Assuming that all the customer-specific information
Assume latest Tomcat 6.x for current deployment, and 7.x for future deployments.
I host an app for a couple of dozen customers. Naturally, upgrade time can be
a bit of a pain, and I'd like to simplify things.
Assuming that all the customer-specific information (DB connection info, logger
info,
17 matches
Mail list logo
