Kevin O’Neill points to Jakarta’s Java Caching System (which looks like a useful project/tool) and says that he has found a potentially nasty bug in the ReadWriteLock class. Hopefully a JCD submitter will stumble upon the buzz generated by Kevin’s post and fix it. Or perhaps someone knows a perfect solution, fixes the problem and emails it off. I like Kevin’s concluding thought:
This hilights both the problem and the power of open source code. The problem is that you can never be quiet sure of it’s quality (though I have mostly found it to be high, and yes I know that the same could be said for closed sourced code); the power is that you can look at the code and make your own assessments/adjustments.