Good morning Stefan, nice work.
I do not know about all the optional tasks. I think that supporting resources for the Perforce tasks for instance would be a kludge, because p4.exe works against the filesystem anyway. Resources make sense for tasks which are coded against a Java API and which can take streams as input or output instead of files. Maybe for the FTP Task ? Would we also make a FTPResource ? Can we change the AntClassLoader (so definer, typedef, taskdef) to support resources in classpath ? For instance put in the class path all the jars which are in the WEB-INF/lib directory of a war file, without explicitly unpacking the war file. Cheers, Antoine Stefan Bodewig wrote: >Hi all, > >I've been travelling yesterday which gave me plenty of time sitting in >a train with a power supply available to me, the result you've already >seen in a bunch of commit messages. > >AFAICS all core tasks now support resource collections, at least where >it made sense. I'm not sure how/if I'm going to tackle the optional >tasks since I lack means of compiling quite a few of them. JUnit's >batchtest already supports resource collections instead of filesets. > >Stefan > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
