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=6204>. 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=6204 support of ant targets in <apply/> task in addition to executable ------- Additional Comments From [EMAIL PROTECTED] 2002-02-04 18:14 ------- I want to add one more point to the original poster The reason we dont have a <javaon> is because we want you to write an ant task to do the same thing. This will give you -reusability -meaningful parameter names -the opportunity to implement dependency checking -the opportunity to implement mappers that work 100% of the time; your example mapper doesnt handle JSP pages with spaces in the names or pages named after reserved words. This may seem extra effort, but the result will not only benefit you, it will benefit everyone else who uses the task. As you observed, make makes what you want to do easy, but that is all it offers in terms of program invocation, and leaves you with makefiles that are a dog to maintain. Ant, on the other hand, encourages the creation and use of re-usable tasks to simplify build files and code reuse. For the jsp example, why not work with us to integrate weblogic JSP into the <jspc> task as another factory. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
