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, -- Laurent PETIT --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
