Reading the following thread brings forth this question ( Actually there was a thread on this few weeks back. But it wasnt very detailed ) :
We have this configuration file that contains machine/server specific information. Assuming my application is an ear, how do I do a build so that I dont have to do a build specific for each target hosts. 1. Should I bundle up the configuration file inside the ear file ? 2. Should I bundle up all configuration files for all possible servers and at deployment time set some kind of variable ( through teh app server admin console ), which resolves to a specific config file ? In general what is teh best practice for this --sony On Thu, Nov 19, 2009 at 6:24 PM, Wagner Santos <wagner.gsan...@gmail.com>wrote: > Thanks! It's work (with some modifications). > > ---------- > Wagner Santos > MSN/Gtalk: wagner.gsan...@gmail.com > Site: http://www.geracaoelias.blog.br > meadiciona:http://meadiciona.com/wagnergsantos/ > > > On Thu, Nov 19, 2009 at 1:00 AM, Wayne Fay <wayne...@gmail.com> wrote: > > > > I have a webapp and two servers and a localhost with diferents > databases > > > configs and I'm trying to do this: > > > > In general, you should use profiles for this kind of thing: > > > > > http://maven.apache.org/guides/mini/guide-building-for-different-environments.html > > > > Wayne > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > >
