Why should we leave apache common collection?
There are several reasons to change the collections framework.
Since the apache collections should be backward compatible it would not be possible to change to a actual Java version. It would be necessary to change to another collection framework (or write all the stuff by yourself).
There are several projects which created a collections framework by themselves or took the apache collection library and upgraded it with generics.
Guava is a project like the apache commons. Since a few weeks the Google collection project is now in the guava project integrated.
I just will take a view to the collection package in the guava library.
What is in the guava-collection?
Helper classes for:

google, Java Collections, Google, Guava, Java

We use a lot of open source libraries and components in our daily business. Open source libraries provide us a big advantage regarding time to market with our products. Every time when we are facing a problem in our software (problem is related to business domain to implementation domain difficulties) we first look into the open source world if someone has already solved that problem or even parts of it. Sourceforge, codeplex and google code (to name a few) are often the first pages we visit to look for code samples, libraries and frameworks. But how can we find the needle in the haystack?

Agile, Methodology, Software apache2, CodePlex, GitHub, Google, Open source, Select framework, select library, sourceforge

There are times, where people ask you questions, which can directly be found on Google. This kind of questions are mostly boring. But hey, there is a nice solution for responding to those people:

On the website Let me google that for you you can enter any search query and send the generated link to the person, who asked you something. Perhaps, this person will learn something and will google the next question before he will ask you…

Methodology Fun, Google