OK.. I just got the answer to my question 2a on this thread... (The rest are still unanswered).
mvn package -X is the most useful command I found to get at the depenceny tree. From there.. it was just a matter of excluding the extra jars. I wish there was a top level exclusion (maybe in the <dependencyManagement> node where global exclusions could be specified. Thanks Pankaj Christian Goetze-3 wrote: > > Tandon, Pankaj wrote: > >> >> >>So the questions are: >>1. How can we control what get's into WEB-INF/lib. We tried all the >>scopes mentioned, but that did not help. >> > I believe that the scope that should work is "provided". The problem is > that I don't know if maven is smart enough to remove a provided > dependency from the transitive closure. I would call that a bug if it > didn't. > > -- > cg > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/dependencies-are-bloated-in-M2-tf3182336s177.html#a8836160 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
