Depending on how complex your "multiple distributions" are, you may discover yourself starting to do more Maven scripting to solve these issues.. Because maven can embed ant tasks, you can use the various filter/replace tasks to change the context parameters at build time. So you can run a filter to edit the hibernate config files.
You may also instead just decide to document all the things that need to change, and do it by hand everytime you move to a new environment.. While icky, it may be the simplest solution... Eric > -----Original Message----- > From: Laurent PETIT [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 10, 2004 8:25 AM > To: Maven Users List > Subject: Re: multiple distributions with filtered properties > > > ----- Original Message ----- > From: "Brett Porter" <[EMAIL PROTECTED]> > >[...] > > > Did I mention that I strongly recommend sourcing the configuration from > outside > > of the distribution? :) > > Re-hello, Brett ! > > > Could you please explain what "sourcing the configuration from outside of > the distribution" means for you ? > > What kind of concrete solution do you apply ? > > - Different maven projects holding the server configuration scripts ? > > - a projects configuration document intended for the admins of > the servers, > and assuming that they are responsible to finish the > parameterization of the > web application ? > > - ... ? > > Thanks in advance, > > -- > Laurent > > > --------------------------------------------------------------------- > 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]
