[
https://issues.apache.org/jira/browse/MTOMCAT-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14019548#comment-14019548
]
Andreas Christoforides commented on MTOMCAT-257:
------------------------------------------------
I ran into another case of this issue so I looked at the code to see how the
"useSeparateTomcatClassLoader" parameter is used.
It seems the issue was introduced by this change:
http://svn.apache.org/viewvc/tomcat/maven-plugin/tags/tomcat-maven-plugin-2.0/tomcat6-maven-plugin/src/main/java/org/apache/tomcat/maven/plugin/tomcat6/AbstractRunMojo.java?r1=1297072&r2=1297073&;
All dependencies of the plugin are added to the separate Tomcat classoader.
It certain cases that is desirable as described in:
https://issues.apache.org/jira/browse/MTOMCAT-122
In other cases, it makes the plugin unusable since it brings in unwanted
libraries like slf4j and google guava.
> Classpathes separation between plugin and application is broken (can't use
> slf4j-jcl in app)
> --------------------------------------------------------------------------------------------
>
> Key: MTOMCAT-257
> URL: https://issues.apache.org/jira/browse/MTOMCAT-257
> Project: Apache Tomcat Maven Plugin
> Issue Type: Bug
> Components: tomcat7
> Affects Versions: 2.1
> Reporter: Brendan Le Ny
> Assignee: Olivier Lamy (*$^¨%`£)
> Attachments: MTOMCAT-227-2.zip, MTOMCAT-227.tgz
>
>
> I use in my war the slf4j-jcl, which is not compatible with the
> jcl-over-slf4j used in the plugin dependencies.
> I give you a little project that show the problem.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
