Hello.
I'm giving a try to tomcat6-maven-plugin. Good work guys, it's great!
I'm getting some extrange behavior with classloaders, I think that
tomcat common classloader is interfering in webapp classloader. I have
Spring 2.5.5 artifacts at tomcat level (tomcat lib) and Spring 3.1.1
at webapp level (WEB-INF/lib), and I'm getting errors because 2.5.5 is
loaded before in the webapp.
I tried to use "delegate = false" in the plugin config in order to get
first the webapp artifacts, but the behavior is the same.
My plugin config:
<plugin>
<groupId>org.apache.tomcat.maven</groupId>
<artifactId>tomcat6-maven-plugin</artifactId>
<version>2.0</version>
<configuration>
<port>8080</port>
<path>/app</path>
<serverXml>src/main/config/server.xml</serverXml>
<additionalConfigFilesDir>src/main/config/tomcat-conf</additionalConfigFilesDir>
<systemProperties>
<JAVA_OPTS>-Djava.security.auth.login.config=$CATALINA_HOME/conf/jaas.conf</JAVA_OPTS>
</systemProperties>
<delegate>false</delegate>
</configuration>
<dependencies>
<dependency>
<groupId>es.klicap.clinker</groupId>
<artifactId>josso-tomcat60-agent</artifactId>
<version>1.3.0</version>
</dependency>
</dependencies>
</plugin>
Note that josso-tomcat60-agent is the dependency that I want at tomcat
level and it gets Spring 2.5.5 transitively.
Am I using "delegate" correctly?
Thanks!
--
Antonio Manuel Muñiz Martín
Software Developer at klicap - ingeniería del puzle
work phone + 34 954 894 322
www.klicap.es | blog.klicap.es
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
