I think that's a good point. Why did it build? Do you know what the extra file was? Groovy will often times successfully compile things that I wish would cause errors, but that's just the dynamic nature of it. OTOH, maybe a well placed test would have failed so you would know there was a problem...
On Thu, Aug 20, 2009 at 12:41 PM, Russel Winder < [email protected]> wrote: > 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. > > -- John Murph Automated Logic Research Team
