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

2009-09-15 Thread David Byrden
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

2009-09-15 Thread Peter Reilly
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

2009-09-15 Thread Wirth, Marc
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