ant-contribution.jar error

I am sure this has been answered, but googling isn't turning up any great results. I am trying to run the seam in action code examples which is a pretty simple build.xml file. Every time I try to run them ant spews this nice stack trace: java.util.zip.ZipException: error in opening zip file [tas

Re: DirectoryScanner cache to boost performance

On 2009-09-15, Raja Nagendra Kumar wrote: > is there a way to use the include and exclude patterns as part of > restrict.. just the name match is what we are looking far. yes, use name selectors (and wrap them in "not"s for excludes) together with correct "and"ing and "or"ing - this is what you

Re: DirectoryScanner cache to boost performance

yep.. missed to discover this.. Also, Stefan, is there a way to use the include and exclude patterns as part of restrict.. just the name match is what we are looking far. e.g patterns we wish to use are similar to the one we use in FileSet include and excludes. Regards, Nagendra -- View th

Re: Build Failed on Vista: File Not Found Error

Ismail, please keep in mind that I have no idea what the tolven project is nor what its build file contains. On 2009-09-15, Ismail wrote: > --- On Tue, 9/15/09, Stefan Bodewig wrote: >> For some reason Ant wants to use a basedir containing a property with a >> value it doesn't know and thus c

Re: DirectoryScanner cache to boost performance

On 2009-09-15, Raja Nagendra Kumar wrote: > Thank you very much for this info. I am trying to use this in our custom > task some thing like this > Union lUnion = (Union) TaskUtils.getCurrentProject().getReference( > lRoot); > Restrict lRestrict = new Restrict(); ...

Re: DirectoryScanner cache to boost performance

Hi Stefan, Thank you very much for this info. I am trying to use this in our custom task some thing like this Union lUnion = (Union) TaskUtils.getCurrentProject().getReference( lRoot); Restrict lRestrict = new Restrict(); lRestrict.setProject(TaskUtils

Re: NPE in RuntimeConfigurable.maybeConfigure() via UnknownElement after upgrade to Ant 1.7

Marc: UnknownElement seems to add the nesting capability to ProjectComponent without taking care of the project references of the nested children. And really, that would be a long and tedious road. So I think it was alway

Re: NPE in RuntimeConfigurable.maybeConfigure() via UnknownElement after upgrade to Ant 1.7

The ant api is very much a broken abstraction - i.e. it has not been designed to used as an api. One thing for sure is that if there is project field in any object, it needs to be set. It will at some stage be used. On Tue, Sep 15, 2009 at 11:30 AM, Wirth, Marc wrote: > Hello, > > After upgrad

NPE in RuntimeConfigurable.maybeConfigure() via UnknownElement after upgrade to Ant 1.7

Hello, After upgrading our environment from Ant 1.6.4 to Ant 1.7.1 we ran into NullPointerExceptions with some of our custom tasks, something like: java.lang.NullPointerException at org.apache.tools.ant.RuntimeConfigurable.maybeConfigure(RuntimeConfigurable.java:390) at org.a