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 18011] - Overriding built-in types fails within tasks
Date Sat, 15 Mar 2003 02:11:46 GMT
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=18011>.
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=18011

Overriding built-in types fails within tasks





------- Additional Comments From greg.pickering@mirant.com  2003-03-15 02:11 -------
Thanks for the feedback.  I wouldn't say that replacing a task midway through 
the build is really my goal.  It is more an artifact of the fact that in order 
to provide a new implementation of, say fileset, I either have to reimplement 
or extend all of the tasks that support fileset where I want to use this new 
functionality or I have to make Ant think my task is really fileset.  

If Ant supported something like classifying a new task as another type (like my 
CCVersionSet, which extends FileSet, as a FileSet) and when it encountered a 
ccversionset type, it called addFileSet, I'd be perfectly happy.  This would 
seem to take full advantage of polymorphic behavior within scripts, which is 
what I'm really after.  Alas, it does not function so.  If I had a suggestion 
for improvement, that would be it.

Mime
View raw message