You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ant.apache.org by bu...@apache.org on 2003/12/04 21:43:25 UTC

DO NOT REPLY [Bug 25226] New: - antlib availability

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=25226>.
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=25226

antlib availability

           Summary: antlib availability
           Product: Ant
           Version: 1.6Beta
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Core
        AssignedTo: dev@ant.apache.org
        ReportedBy: gudnabrsam@yahoo.com


It is possible to write antlibs that are composed, for example, entirely of 
<*def> element sets and thus use no custom code.  Currently the way to make 
these available via antlib namespaces, as I understand it, is to package the 
antlib in a jar file with an appropriate directory structure, and deploy it as 
you would any other Ant add-on.  Would it make sense to create an ANT_HOME 
subdirectory specifically for "jarless" antlibs?  This could be implemented as 
a "classes" type directory that would work for classes and/or resources.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org