I'm using Cargo to deploy my WAR to a testing server. The idea is that the CI build will push the app over to a testing server. When deployed to this testing environment, my Spring configuration wires mock business objects into the app. The spring config resides inside my WAR. It's unclear to me how I should handle the creation of this testing version of the spring config . . .
I think I understand that it's very bad have my build produce an alternative version of the WAR artifact for testing. 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. The obvious drawback here seems to be the fact that the same maven artifact, my war, would sometimes have testing config inside it and sometimes the real config. How do I get around this? Do I need to restructure the way I do my whole build, externalizing the config to another artifact? Is there someway to just safeguard against the testing artifact escaping into the real world ( i.e. a maven repo ) where it could be confused with the real one? Should I make two versions of the WAR from my build? --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
