Skip to content
Craig P. Motlin edited this page Jan 13, 2016 · 3 revisions

Eclipse Collections 7.0

Target: January 2016

The initial release of Eclipse Collections. We're starting the version number at 7.0 since it's functionally equivalent to GS Collections 7.0 after migrating the project to the Eclipse Foundation.

  • Replace Apache 2.0 license with EDL and EPL dual license.
  • Convert package names, directory structures from "com.gs" to "org.eclipse".
  • Remove the memory-tests module that rely on a third party library with a different license.
  • Update author information, README.md, and any other strings which refer to GS Collections.
  • Update README.md contents to be in line with Eclipse Collections.
  • Configure git settings.

Eclipse Collections 7.1

Target: February 2016

Make minor updates for OSS community engagement.

  • Migrate the GS Collections Kata to the Eclipse Collections Kata.
  • Provide instruction on migration from GS Collections to Eclipse Collections.
  • Update Eclipse project files.

Eclipse Collections 8.0

Leverage features of Java 8. Eclipse Collections already uses Java 8 in test modules, but the main library targets Java 5 bytecode. By dropping support for older versions of Java, Eclipse Collections can benefit from new features and better integrate with the standard libraries.

  • Make Eclipse Collections functional interfaces extend Java 8 functional interfaces
  • Create our own Streams and override the stream() method for better performance
  • Add new API methods that return Optional
  • Change our SortedSet and SortedMap implementations to additionally implement NavigableSet and NavigableMap respectively
  • Use default methods to reduce lines of code and jar size