I appreciate the feedback, but I am struggling to follow, clearly I don't understand "the maven way".
I am new to maven, based on the documentation and the specification it seems like profiles are used to create different versions of a deployment package. Why would profiles be there if not for that purpose? More importantly, why would maven have such a rich properties and resource filtering feature set if the maven way is to externalize all this information? Maven is suppose to be a build tool, but you are telling me I shouldn't put build configuration data in it. It seems like you guys are saying only to use the dependency management/repository aspect of it. Would love some clarification. thanks -- View this message in context: http://maven.40175.n5.nabble.com/using-build-profiles-for-WAR-plugin-tp5525954p5528742.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]
