> No; it's a reason for doing a full clean build and unit test run > before checking in any changes.
> This way whoever added org.apache.Thing, or updated the library that > added it, is responsible for not breaking everyone else's build. > In this case causing a compiler error is good; the error will mention > the name of the class that was just added; and the adder will say "oh, > duh" and know what to do to fix it. More troublesome are interface > changes that are silently absorbed but cause semantic changes. I totally agree. Gavin McPhee Senior Software Engineer Object Connections Australia www.objectconnections.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
