> 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. Alternatively you can build one single WAR with all possible configurations stored within, and then use some environment variable which tells your WAR or Appserver which config file to load at runtime. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
