| [cross-project-issues-dev] Orbit to make last minute removal of com.google.collect |
Is anyone still using this com.google.collect bundle, for Juno?
Normally, we in Orbit would never consider removing a bundle this late in the cycle, but this bug has fallen through the cracks.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=371396
The original creators of com.google.collect recommend all users of that package use its super-set replacement com.google.guava
And if both end up on the same "classpath", chaos is likely.
http://code.google.com/p/google-collections/
So, I hope anyone interested and using this API has already moved to the new packages, and I think it best we remove it from Orbit's "active builds" and Juno Release to avoid confusion and lesson the chance of clashes and interference of one project with another.
Naturally, com.google.collect will stay in any old, previously provided R-builds (such as for Indigo) if people need it there for some maintenance builds or something (and thus, we can never guarantee there would never be some conflict between the old and the new packages, just lessening the odds).
I do not see com.google.collect in current "staging" repo, so fairly confident no one uses it, but ... thought such a large late change deserved special mention.
This Orbit S-build,
http://download.eclipse.org/tools/orbit/downloads/drops/S20120519125550/
is nearly our Juno R-build, except for removing this problematic bundle.
I'll wait until Friday 5/25 before promoting our Orbit final R-build, to at least give some chance for potential consumers to comment on bug 371396.
Thanks,