Hi David, you are right that it's 1101448 that caused this regression, I met the same problem and attached a patch to OPENEJB-1552.
see more details: http://openejb.979440.n4.nabble.com/org-apache-openejb-core-interceptor-ReflectionInvocation-can-not-access-a-member-of-class-org-apache-td3534998.html On Fri, May 20, 2011 at 9:37 AM, David Blevins <[email protected]>wrote: > Seems we broke the example/schedule-methods part of the build. I setup a > spare machine to cycle back through the trunk revisions and try that test > out (https://gist.github.com/982141). > > r1101442.log:Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time > elapsed: 9.888 sec > r1101445.log:Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time > elapsed: 9.755 sec > r1101448.log:Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time > elapsed: 10.485 sec <<< FAILURE! > r1101452.log:Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time > elapsed: 10.086 sec <<< FAILURE! > > It starts breaking at 1101448 but strangely that revision doesn't seem at > all timer related. Revision 1101445 is timer related. > > I know Shawn and Ivan are super swamped with TCK work. Good contribution > opportunity for anyone looking for something to do. :) > > Anyone want to check it out? > > > -David > > > > > -- Shawn
