I wrote a plugin that looks at a combination of profiles (localdev+generalstackinfo+stack+machine type combo) that generates a property file which is used by ant (which is what we're using for deployments). You do this once and then manage the settings inside the pre-generated property file.
This is a recent change as we were doing what you're talking about (generating multiple zip files for all different environments). Our build was taking ~3 hours. The property file method takes roughly 26 min (as there's no generation. The hard part is propagating developer settings that are valid through to production, you can't use filters because they take precedence over profiles and when two disparate projects connect to the same db (for example), where do you put that setting? You can't just put it in profiles.xml otherwise you have a duplicate from project to project. -----Original Message----- From: Paul Davis [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 03, 2008 2:22 PM To: Maven Users List Subject: Re: Building for different environments - how do _you_ do it? 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? > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
