Hi Ron, I've been reading quite some of your posts in the forum, and it actually changed my mind about deployment configuration. Enlightening indeed.
I would now try to favor a single artifact deployment that could be configured externally - say JNDi, this really makes sense. That said, I don't want to compromise on the ease of deployment. Up to now our customer just had to drop the war in it's app server, and that was it. Plus, we were app server agnostic, we could deploy on whichever server WITHOUT ANY configuration. Trying to figure a way to combine both requirement, here is what I'm imagining, and I'd like to hear your opinion on this, whether it makes sense and if it's possible with JNDI. 1) If we use JNDI to configure the WAR on runtime, and if we want to have a 'dropping war only' deployment, the only option is to include all the needed JNDI configuration IN the war. Is this at all possible? 2) there need to be a way to select the adapted JNDI configuration: I'm thinking environment variable here, it'd certainly be the simplest configuration on top of installing the app server. What do you think? cheers -- View this message in context: http://maven.40175.n5.nabble.com/maven-failsafe-plugin-Running-integration-test-with-its-own-profile-tp3367473p3375605.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
