ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 31999] - Easier way to declare externally-written tasks in build script
Date Mon, 22 Nov 2004 17:34:36 GMT
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=31999>.
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=31999


gudnabrsam@yahoo.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WORKSFORME




------- Additional Comments From gudnabrsam@yahoo.com  2004-11-22 18:34 -------
I don't think you've gotten all the antlib usages.  You mentioned "where does
the typedef know where to find tasks/types".  <taskdef> and thus <typedef>
is/are documented as accepting one of five (I think) classpath specifications,
or default locations (ANT_HOME/lib for one) are used.

Next, if all antlib.xml files existed at the same resource location it would
make retrieving them much more difficult than a simple getResource call because
you'd have to look in every jar.  Having antlib URLs allows the construction of
different locations for antlib.xml and puts the task of finding the appropriate
resource onto the JVM.  It also means you can (if you wanted to) bundle multiple
antlibs into a single archive.

Next you propose that the task writer define the namespace uri.  I'm no expert
on XML namespace theory but at the very least you could say that if two tasks
were defined by their respective authors to live in the same uri with the same
taskname (not entirely improbable) the innocent user might have trouble using
the competing tasks together.

As for simplicity, I most often use the <project xmlns:foo="antlib:org.foo">
approach.  Having the user declare the namespace is not unreasonable and I
expect shields us from numerous bug reports by virtue of requiring that the user
know what he or she is doing.

Please feel free to post to the user list if you need further help with antlibs.

Thanks,
Matt

-- 
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: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message