Community
Participate
Working Groups
Disable calls to the MethodVerifier class because it no longer reports any errors messages that we show. This should improve performance slightly and remove some potential NPEs.
Created attachment 193596 [details] patch
Explain why you believe this is a stop-ship defect. Or, if it is a "hotbug" (requested by an adopter) please document it as such. Not necessary to run this code anymore due to changes in semantic validation, so it hurts performance. Is there a work-around? If so, why do you believe the work-around is insufficient? No How has the fix been tested? Is there a test case attached to the bugzilla record? Has a JUnit Test been added? Nothing really to test, just turned off the call to the MethodVerirfier code. Give a brief technical overview. Who has reviewed this fix? Nitin reviewed the fix. Just commented out the call to MethodVerifier.verify(). What is the risk associated with this fix? None.
I'm ok with this, but will ask ... are you sure the method has no side effects, such that if not called, will change some other behavior? (I assume so ... just something I'd check myself, if I had the time). Also, in future, as RC weeks pass, please better justify "performance improvements" with some sort of relatively objective numbers ... 1%, 10% 50% of time to open a file (for example) ... just so its easier to see how important it is. Thanks for your care,
Did this fix go in already, into this week's declared build? If not, then it needs another PMC review/vote. If so, it should be changed to "fixed". Thanks
Isn't in 4/21(20) declared build. Requires a one more +1 from a PMC member. More wouldn't hurt.
looks good - do we want to remove more calls to this class in the future?
Checked into 3.2.4 and HEAD.