> I think I understand that it's very bad have my build produce an alternative > version of the WAR artifact for testing.
It is not a best practice, as far as most of us here are concerned. Best practice says to use the exact same (unchanged) artifact for QA and PROD. > I know that I could use a maven profile, triggered in the build job I use to > deploy > the war to the testing server, to filter the spring config for the testing > settings. No b/c you'd end up with a different war for QA/testing than you'd use for PROD. Thus this is not the best approach. > Do I need to restructure the way I do my whole build, externalizing the > config to > another artifact? This is one (good) way to do it. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
