commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 34942] - [VFS] no vfs_cache cleanup after ant task completed
Date Mon, 15 Aug 2005 14:34:28 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=34942>.
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=34942





------- Additional Comments From hoju@visi.com  2005-08-15 16:34 -------
Ok, I see what you mean now.  It's hard to say.  If you look at ant-contrib,
they haven't prefixed their task names.  However, they also don't have any task
names that conflict with ant-core or ant-optional tasks in the default
namespace.  This might be a good question for the ant-user list (which I'm not
currently subscribed to).

One immediate thought that comes to mind is that if the tasks.properties file is
left in place and people use it directly instead of antlib and don't povide a
namespace when they <tasksdef> the tasks, then the copy/move/delete/mkdir tasks
either won't work or will conflict with strange ways with the core/optional
tasks.  The buld will almost certainly blow up.  It might be wise to remove
tasks.properties altogether and define everything explicitly in antlib.xml. 
This would force users to provide their own namespace when they declare VFS
tasks since they'll have to enter one as a <project> xmlns entry.  At that
point, naming the taks something like "copy" rather than "v-copy" will be safe
because "copy" will always be referenced within its own namespace.  Again, I
would consult with the Ant guru's before making a final decision.

Jake



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


Mime
View raw message