Oh... I figured out a clue to the problem. I've been using jetty (6.0.0rc0) to test out my webapp. Jetty only loads the jars I want into its webapp classloader. I found out that the jars that were getting into the generated war at war:war were jetty's dependencies! So by having the jetty plugin, it sort of surreptitiously put jars into my dependencies. I didn't know a plugin could do that unless I invoked it. I'll raise this with them... but can a maven expert say wether this is potentially a maven bug... since I'd never expect a plugin's jars to end up in my war. -- View this message in context: http://www.nabble.com/war-including-excluded-transitive-jars-tf1960799.html#a5379305 Sent from the Maven - Users forum at Nabble.com.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
