This week's book giveaway is in the Reactive Progamming forum. We're giving away four copies of Reactive Streams in Java: Concurrency with RxJava, Reactor, and Akka Streams and have Adam Davis on-line! See this thread for details.
I have major problems with the fluidity of the Jakarta Commons public API.The last (or was it a bit earlier) release changed so much in the public API that a lot of code using them needs major changes to work again. This is not good of course and a major reason why I'm wary of using them...
I agree, this makes it terribly unusefull. Why do they do that. ? In such a case the whole book would be outdated very quickly
swimming certificate (A & B), shoelaces diploma, and some useless java ones.
I don't quite agree that commons components are that fluid. And even if there are changes, the old methods stay deprecated for quite a long while before being deleted. APIs are bound to change and evolve as new requirements and people come in. So I think API changes will always be there. If one does not need the features of a new version, why migrate? Jakarta keeps all versions of a component available for download so you could very well keep using a version that suits your needs.