Amy Roh wrote:
Local deploys do not copy the WAR over.
So local deploy is *not* persistant until we implement to save config. This
is what I was referring to.
Fixing the bug is rather annoying, and the amount of stuff which should be automated is quite big, and seems not worth it.
Instead, I'd like to remove local deploy from the manager servlet (IMO, it's useless). If using the Ant tasks to do a local deploy, then it's up to you to persist the config later, upon the user's choice.
+0
I think we should also add some Ant tasks:
- a "save config" Ant task - with a context parameter allowing to save just one context (this task is also useful when using the JMX tasks to reconfigure Tomcat, and persisting the config is needed)
- maybe extend a bit the JMX tasks
+1
Amy
Comments ?
Remy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
