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]
