Thanks again Wayne, mvn -X helped me find the problem. I appreciate the help and also that of others on this list who have helped me get familiar with maven. Thanks you.
Tom. -----Original Message----- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 03, 2006 11:08 AM To: Maven Users List Subject: Re: Removing jsp-api-2.0.jar from delpoyed webapp Try mvn -X and use the text dependency tree to identify which artifacts are pulling in that dependency. It might not be coming from where you think it is. I'll take a wild guess here and say you've got a J2EE multi-module project and while the WAR module is properly excluding the jsp-api, the EAR module is not, and so you're getting that jar bundled in. You will need to specify the exclude in both poms. Wayne On 10/3/06, Tom Hurley <[EMAIL PROTECTED]> wrote: > Thanks Wayne, > > I've tried both of those options but the jar is still being included. Its > making me say bad words... > > Any other suggestions? > > Thanks. > > Tom. > > > > Tom Hurley, Senior Lead Developer > Insightful Corp, 206-283-8802 x369 > > -----Original Message----- > From: Wayne Fay [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 03, 2006 10:48 AM > To: Maven Users List > Subject: Re: Removing jsp-api-2.0.jar from delpoyed webapp > > You have 2 options: > 1. Add an excludes node to the dependency node which is bringing in > this unwanted artifact. > 2. Specify the jsp-api-2.0 as a dependency with scope "provided" in your pom. > > Wayne > > On 10/3/06, Tom Hurley <[EMAIL PROTECTED]> wrote: > > Hi, > > > > I am having a problem with the Maven's transitive dependency mechanism. > It's > > a fantastic feature but I would like to be able to prevent it including a > > particular jar. > > > > I am creating a web app and deploying it to Tomcat. In my case one of the > 3rd > > party libraries results in the inclusion of jsp-api-2.0.jar in my > WEB-INF\lib > > folder. This is a shared library in Tomcat's common\lib folder and its > > inclusion with my application causes known problems when running my > > application. If I delete the jar everything works okay. > > > > Is there any way to either stop the dependency mechanism including this jar > > or can I flag it to Maven to exclude it? Someone else must have come up > > against this problem. > > > > Thanks in advance for any help or suggestions. > > > > Tom. > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
