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=17844>. 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=17844 Standardized "deployment" files for Ant optional task jars (drag + drop tasks) Summary: Standardized "deployment" files for Ant optional task jars (drag + drop tasks) Product: Ant Version: unspecified Platform: All OS/Version: Other Status: NEW Severity: Enhancement Priority: Other Component: Optional Tasks AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] My idea is to make adding additional task jars into Ant very easy. Ideally, you would create your task sources, and a tasklist.properties which would map the tagname to the classname (like specifying a file or resource properties in a taskdef). You would then create the jar file of your classes and put the tasklist.properties in the META-INF directory of the jar file. You could use Ant to do this :) Now place your add-on jar into the Ant lib directory. You should now be able to use your custom tasks, and filters in any build file. This would be made possible by having Ant look at the jar files in the lib directory, and looking for the META-INF/tasklist.properties in each one. If it is there it will define those tasks using the current classpath plus that jarfile (and possibly also the classpath specified in the jar manifest). This should make it so that all you have to do to extend Ant is drop a jar into the lib directory.
