On Thu, 2009-08-20 at 13:25 -0400, John Murph wrote: > 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... > CopySpecImpl.groovy was the culprit, it was there in addition to CopySpecImpl.java, so a hang over from the commit that changed the implementation language. This would then lead to choice of source being dependent on class loader behaviour which I guess could lead to different choices in different situations.
--
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
