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
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
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.
What then are the options for handling this externalized configuration at build
time? At first glance, I'm thinking it requires a whole extra build
What then are the options for handling this externalized configuration at
build time?
At first glance, I'm thinking it requires a whole extra build project for
doing the testing
deployment, complete with src that includes a copy of the test configuration.
Sounds about right to me.
On 29/10/2012 10:33 AM, Davis, Chad wrote:
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.
What then are the options for handling this externalized configuration at build
time? At first glance, I'm thinking
