Very good pointers, thanks a lot ! ----- Original Message ----- From: "Tim Shadel" <[EMAIL PROTECTED]> To: "Maven Users List" <[EMAIL PROTECTED]> Sent: Thursday, June 10, 2004 8:21 PM Subject: Re: Deploy a webap to multiple environments (test, pre-prod, prod)
> Have you looked through Vincent Massol's slides here? > > http://www.pivolis.com/pdf/Enterprise_Builds_V1.0.pdf > > http://www.pivolis.com/pdf/J2EE_projects_Maven_V1.1.pdf > > http://www.pivolis.com/pdf/Distributed_Agile_V1.0.pdf > > --Tim > > Laurent PETIT wrote: > > >Hello, > > > >I recently read a thread about this subject, but was not entirely convinced > >by the answer. > > > >I think this is a very common problem : you develop a webapp, and you have > >to deploy it on multiple configurations : generally one for each > >test-process environment : internal ( integration server ), in > >pre-production on the client network, and eventually in production on the > >client network. > > > >It is common that you then have to setup different levels for logs, > >different database schema names, different pathnames, ... generally in some > >well identified properties files. > > > >I saw an answer to this problem, which was to setup multiple anemic maven > >projects which will hold the properties differences. > > > > > >I'm not sure this is a "recommended best practice" for the problem ? > > > >What do you folks think about it ? > > > >What do you do in your own projects ? (even if it is not as "a beautiful > >solution" as it should be, what does *work* for you ?) > > > >Thanks in advance, > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
