Here is extra information: * I obtained the latest files from the repository around 8:00GMT-5 and posted the patch around 12:30GMT-5. I hope there was not too much change made to those files during this time, because the patch covers a great portion of the affected files.
* I performed the following tests: * Affected code does compile, along with everything else. * Affected vm's do work correctly. * Generated code does compile. * Recreated the jar successfully. * Successfully ran my own application with the new jar and the generated classes. However, my application doesn't have a great code coverage ratio, so I cannot tell if it broke something that my application is not using. I noticed that there isn't a lot of test cases, and they do not cover the aspects that I modified. Maybe someone who has an application with a very good code coverage ratio should try out the patched version, in order to improve our confidence. Please let me know what is your usual strategy for testing such changes. -- Mathieu -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
