Russel, I have seen behavior that could lead to this. I don't understand the circumstances, but I've had "miscompiled" Groovy classes that inherit from Java classes that pass all nulls to the Java constructor instead of the objects that were given to them. I simply recompiled the Groovy and the problem disappeared. I saw this behavior by stepping threw the execution and saw non-null values get passed to the Groovy constructor, and then the Java super class constructor gets called with all nulls.
I'm wondering if this might be related to your other problems compiling the CopySpec stuff. My only hesitation in this suggestion is that I don't know why this happened to me, so I don't know the circumstances that lead to this bug. Would you please put a couple println in the code and see if my guess is correct? SettingsFactory creates the DefaultSettings object, so make sure settingsDir is not null there. If it's not, my guess is correct. On Thu, Aug 20, 2009 at 8:42 AM, Steve Appling <[email protected]>wrote: > > Russel Winder wrote: > >> Just checking first but this seems like a bit of an emergency: >> >> > It looks like the built in empty settings file is not being used. You > might be able to work around this temporarily by providing an empty settings > file. > > -- > Steve Appling > Automated Logic Research Team > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > -- John Murph Automated Logic Research Team
