DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9242>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9242 Please use more specific ant task names than <install> and <remove> Summary: Please use more specific ant task names than <install> and <remove> Product: Tomcat 4 Version: 4.1.0 Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] While I welcome the new Ant tasks for webapp management, could you please use names that are more tomcat centric than <remove> and <list>, things like <tomcatremove> and <tomcatlist>, for example. That way we arent constrained from ever introducing a toplevel datatype like <list> by the fear of breaking tomcat build files. Now I know that you are going to say "but the users can choose any name they like in the build file", but we will still get grief when things break in a future ant version. Also, <taskdef> can take the name of a properties file on the classpath, loading in all task declarations in there. That is much better approach for declaring >1 task, which is what your examples do. If you are going to move to that model of taskdef, it is imperative that you adopt tomcat specific names. Ta, -steve -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
