Hi, Not sure this can work. But you can test with modifying the code and put setReloadable on the created webappLoader. If it works for you, we can integrate this in the code.
2010/6/3 Matt Cristantello <[email protected]>: > Hello everyone, > > I'm having a minor issue with the maven-tomcat-plugin version 1.0 when > using tomcat:run -- it is adding the class folders from the maven reactor, > but Tomcat does not reload the classes when they are modified. My current > plugin config is: > > <plugin> > <groupId>org.codehaus.mojo</groupId> > <artifactId>tomcat-maven-plugin</artifactId> > <version>1.0</version> > <configuration> > <warSourceDirectory>${basedir}/public_html</warSourceDirectory> > <additionalConfigFilesDir>${basedir}/tomcatconf > </additionalConfigFilesDir> > <path>/mycontextroot</path> > <useSeparateTomcatClassLoader>true</useSeparateTomcatClassLoader> > <systemProperties> > <java.util.logging.manager>org.apache.juli.ClassLoaderLogManager > </java.util.logging.manager> > <log4j.configuration>file://${basedir}/src/log4j.xml > </log4j.configuration> > <org.apache.catalina.level>FINEST</org.apache.catalina.level> > </systemProperties> > <contextFile>${basedir}/public_html/META-INF/context.xml</contextFile> > </configuration> > <dependencies> > <dependency> > <groupId>org.apache.tomcat</groupId> > <artifactId>juli</artifactId> > <classifier>log4j</classifier> > <version>6.0.26</version> > </dependency> > <dependency> > <groupId>org.apache.tomcat</groupId> > <artifactId>juli-adapters</artifactId> > <version>6.0.26</version> > </dependency> > <dependency> > <groupId>log4j</groupId> > <artifactId>log4j</artifactId> > <version>1.2.13</version> > </dependency> > </dependencies> > </plugin> > > I have tried not using the useSeparateTomcatClassLoader flag, and leaving > the contextFile out too, with no change. The problem was also occurring > before I added the log4j configuration, I set that up to see if I could > figure out why this was not working. I saw in the maven-tomcat-plugin code > that the reloadable property is set on the context, so I'm not sure what's > going on. It could be related to the non-standard project structure, I > suppose, but given that I can load and run the application without any > trouble I'm not sure. Have any of you seen this issue before? If not, do > you have any ideas? > > Thanks in advance, > ~Matt > > -- > **************************************************************************** > Matthew D. Cristantello > [email protected] > *************************************************************************** > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > -- Olivier http://twitter.com/olamy http://fr.linkedin.com/in/olamy http://www.viadeo.com/fr/profile/olivier.lamy7 --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
