That resolved the issue
On 2/28/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > If you set the scope of the Struts artifact to "provided", do you still > get > the transitive dependencies in WEB-INF/lib? > > It's better to be hated for who you are > than loved for who you are not > > Ian D. Stewart > Appl Dev Analyst-Advisory, DCS Automation > JPMorganChase Global Technology Infrastructure > Phone: (614) 244-2564 > Pager: (888) 260-0078 > > > > "Sanjay > Choudhary" To: "Maven Users List" > <[email protected]> > <choudharysanjay@ cc: > gmail.com> Subject: War's - How to > exclude bundling of jars in WEB-INF/lib? They are caused > because of transitive > depedencies > 02/28/2006 03:56 > PM > Please respond to > "Maven Users > List" > > > > > > Let us assume that we have an EAR which is dependent on Struts-x version. > > Ear dependent on Struts > java 1 dependent on Struts > java 2 > web dependent on Struts > > > > Now when we build, our EAR contains struts-x.jar and all the other > transitive dependencies of struts. Since our classloader policy for EAR > is > "application", we don't want struts-x.jar and transitive dependencies in > web/web-inf/lib. To avoid this, in the web project pom.xml we defined > > <dependency> > <groupId>struts</groupId> > <artifactId>struts</artifactId> > <version>1.1</version> > <optional>true</optional> > </dependency> > > By doing this, I am able to avoid bundling of struts.jar in web-inf/lib > folder in WAR but all the transitive dependent jars are still bundled in > the > WAR. Is there a way to avoid this? > > -Sanjay > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
