Redeploy goal does do what is says on the tin.
----------------------------------------------
Key: MOJO-566
URL: http://jira.codehaus.org/browse/MOJO-566
Project: Mojo
Issue Type: Improvement
Components: tomcat
Environment: Windows XP Professional, Intel Centrino, Java 5, Tomcat
5.5.16, latest snapshot of tomcat plugin.
Reporter: Trent Rosenbaum
Priority: Minor
Attachments: patchfile.txt
The class and properties message that make use of the term redeploy should be
renamed to reload. Within the class that implements the redeploy goal the
method "reload" is used on the manager. The task should be renamed because it
does not complete another deployment of content over the existing deployment of
the web app. The documentation on the tomcat site says that the a reloading of
classes is completed, (making you think there is a deployment of new code) but
this is only if the classes and resources are placed under the webapps
directory within tomcat.
A new RedeployMojo should be implemented to extends the existing deployMojo but
should override the isupdate method to allow the existing deployed context to
have a new deployment placed over them. If the project does not feel this is
worth doing then it should be made clear what tomcat:redeploy is doing. If the
class is not implemented then a user could set the configuration for this value
to be true.
I have included a patch file for the rename.
--
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
