The best thing is to NOT create a different build for different environments.
When environment specific stuff is needed (EARs and WARs) look up the info from JNDI and put that configuration on the server. Then if something needs to change, you don't need to create a new build. If you have to do it, you could probably create a profile for each environment setting a variable. Then the files specific to that environment could be "filtered" based on the value of that variable. You'd just specify the profile to use when creating the build. On Tue, Jun 3, 2008 at 11:14 AM, EJ Ciramella <[EMAIL PROTECTED]> wrote: > So how are other people building for both dev and other environments? > > > > For example, how does one support multiple environments like the > following: > > > > 1 - Dev integration > > 2 - QA stack 1 > > 3 - QA stack 2 > > 4 - QA stack 3 > > 5 - Staging > > 6 - Prod > > 7 - local developer builds > > > > How do other people support variables that can be the same from local > builds through production but support the option to change them at the > last minute? Are people building multiple version of say an ear > deployment to support all the different environments? > >
