DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=28851>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=28851 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE ------- Additional Comments From [EMAIL PROTECTED] 2005-01-11 23:45 ------- (In reply to comment #0) > I fail to really understand the subtle difference between the 'undeploy' > and 'remove' and their associated use case. The distinction is a subtle one. 'undeploy' is opposite of 'deploy' and 'remove' is opposite of 'install'. The difference is really between 'deploy' which uploads a file to the server and 'install' which works with a file/directory that is already present on the server. > But for instance, the 'undeploy' command does not work as it validates that > the context docbase should be inside the manager working directory, which is > quite unlikely to half happen if deployed incorrectly due to PR 28830 'deploy' should put put wars in the appbase > I will send a complete patch within the next days. Fixing 28830 should fix this since the war will be in the expected place. Therefore, I am marking this as a duplicate of 28830. FYI - Remy has made this a lot better in 5.5.x but I don't propose to back port all his changes. *** This bug has been marked as a duplicate of 28830 *** -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
