On Wed, Oct 27, 2010 at 11:41 AM, Anders Hammar <[email protected]> wrote:
> You either need to separate the configuration from the binaries, or have > different artifacts. > The configuration is separated from the binaries for the most part. however some artifacts (like a war file) have environment specific class path names in them. But an integral part of our build process is to generate the config files read by the binary artifacts at runtime. Add to that some of the "almost source" files like wsdl endup having server names embedded in them (compliments of oracle). But what do you mean by different artifacts? Its not practical to have the build create artifacts for every environment due to our parallel releases process. if Im testing the 3.0 release in the QA2 environment, thats all I want to build. Creating artifacts for an environment that will never be used is a waste of time and resources. > > Your current solution does not work if you do deploys to a repo and adhere > to the very important Maven rule that a release may NEVER be altered. > Unfortunately I cant change that. The only thing that doesnt change between environments is the source code.
