As a plugin user I would like reloadable contexts so that my development times
are reduced.
-------------------------------------------------------------------------------------------
Key: MTOMCAT-76
URL: http://jira.codehaus.org/browse/MTOMCAT-76
Project: Maven 2.x Tomcat Plugin
Issue Type: Improvement
Affects Versions: 1.1
Reporter: Ryan Connolly
It is a known limitation that context reloading does not take place with a
simple compilation in the current project or to a redeployment of a compile
time dependency.
As tomcat will scan WEB-INF/classes and WEB-INF/lib for class changes and the
plugin uses neither of these paths in the classpath, context reloading simply
does not occur even when context.setReloadable(true) is added and the current
WebappLoader instance is also set to reloadable.
It seems more likely that this feature could be achieved by adding a scanner (a
la jetty-utils' Scanner class or what has been proposed in MTOMCAT-15) that
will monitor ${build.outputDirectory} and any compile/runtime dependency
artifacts by default.
- Quick and dirty: (add jetty-utils dependency and use their Scanner class)
- Perhaps more correct for project: (figure out how the current scanning works
and determine whether the Embedded API exposes this functionality or not. If
not, create a scanner.)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
