I should have made clear: the problem for this project build was in the Gradle that got built, it was unreliable. Now I found the Gradle build problem, I have a Gradle I trust, and it seems to compile the project fine. So the whole incident has been very spurious, consequent on managing to get a build when a build should never have completed.
On Thu, 2009-08-20 at 17:37 +0100, Russel Winder wrote:
> John,
>
> It turns out that there was a rogue groovy file in the working tree, and
> it has been causing all my problem of compiling Gradle for the last week
> or so.
>
> My hypothesis is that there was a problem during a Bazaar update of my
> mirror and that a file that used to be in the codebase that should have
> been removed got left, but then was forgotten about by Bazaar. I
> normally use a branch of the mirror for working in so didn't see this,
> if I had I would have quickly seen it. However my script for compiling
> Gradle uses the mirror and not my working area so it was seeing it. I
> just failed to twig to the fact. Silly me.
>
> Apologies to all for the verbiage and the noise.
>
> On Thu, 2009-08-20 at 10:34 -0400, John Murph wrote:
> > 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.
>
--
Russel.
=============================================================================
Dr Russel Winder Partner
xmpp: [email protected]
Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road, f: +44 8700 516 084 voip: sip:[email protected]
London SW11 1EN, UK m: +44 7770 465 077 skype: russel_winder
signature.asc
Description: This is a digitally signed message part
