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 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | ------- Additional Comments From [EMAIL PROTECTED] 2005-08-10 07:00 ------- I found yet another reason to bite the bullet and depend on Ant-1.6.2+ instead of 1.5.x. I made some changes to my build so that as optional VFS dependencies are downloaded, I redefine the VFS tasks so that the next optional dependency to download can take advantage of the most recent downloaded optional dependency. For instance, if I download commons-collections, I can then re-define the task with commons-collections now in the classpath so that the next dependency can take advantage of the LRU cache, and so on.... So, I tried this and I got (partial stack track after doing ant -debug)... java.lang.ClassCastException: org.apache.commons.vfs.tasks.VfsTask$VfsRef at org.apache.commons.vfs.tasks.VfsTask.resolveFile(VfsTask.java:64) at org.apache.commons.vfs.tasks.AbstractSyncTask.handleSingleFile(AbstractSyncTask.java:339) at org.apache.commons.vfs.tasks.AbstractSyncTask.execute(AbstractSyncTask.java:182) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) at org.apache.tools.ant.Task.perform(Task.java:364) at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:64) However, when I revert back to the previous version of VfsTask.java and apply my patch, everything works like clockwork. No errors or anything. Can we, pretty please, just require Ant-1.6.2. The patch is deadpan simple, it actually works in all cases (try it if you have doubts), and if people are still using Ant-1.5, they are living in the dark ages anyway. The current solution is brittle. BTW, is commons-httpclient now *not* an optional dependency? I used to be able to only need commons-logging and commons-vfs in the classpath in order to have basic rudimentary downloading capability using simple http to grab a file. Now, if I don't have commons-httpclient in the classpath before using <vfs:copy>, I get this... java.lang.NoClassDefFoundError: org/apache/commons/httpclient/util/URIUtil at org.apache.commons.vfs.provider.URLFileName.getPathQueryEncoded(URLFileName.java:65) at org.apache.commons.vfs.provider.URLFileName.getURIEncoded(URLFileName.java:119) at org.apache.commons.vfs.provider.url.UrlFileObject.createURL(UrlFileObject.java:74) at org.apache.commons.vfs.provider.url.UrlFileObject.doAttach(UrlFileObject.java:63) at org.apache.commons.vfs.provider.AbstractFileObject.attach(AbstractFileObject.java:1215) at org.apache.commons.vfs.provider.AbstractFileObject.getType(AbstractFileObject.java:400) at org.apache.commons.vfs.tasks.AbstractSyncTask.handleSingleFile(AbstractSyncTask.java:341) at org.apache.commons.vfs.tasks.AbstractSyncTask.execute(AbstractSyncTask.java:183) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) at org.apache.tools.ant.Task.perform(Task.java:364) at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:64) Can we move back to making it optional? At a minimum, the optional dependencies page needs updating, but I'd much rather simply keep httpclient optional. Thanks, 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
