Bumps version numbers
Increase test timeouts (possible source of flaky classpth tests).
Create features for each Scala versions

This will allow to install multiple versions of Scala on
the same Eclipse installation.
The main sdt build phase now only depends on p2 repos, external or local
created in the previous phases.
Some version definition
Tweaks the arguments in the build script
Creates a Scala 210 jars bundle

To be used instead of the normal bundles until when are able to support multiple bundles of Scala
Fixes scala211 source feature label
Adds computeSourcePath documentation
Cleans up new features labels
Merge pull request #690 from skyluc/issue/multi-scala-support

multi Scala support
Adds support to detect available Scalas

Detects both bundled jars and multi-bundles installations
Merge pull request #693 from skyluc/issue/detect-multi-scala

detect multiple scala
Added the ability to compile the sbt compiler-interface on the fly and use it.
Reviewer’s comments.
Fixes memory test configuration

Because the m2 repos are no more used in this part of the build, the
version for the needed Scala jars are no more pre-set.
Merge pull request #698 from skyluc/issue/fix-memory-test

Fixes memory test configuration
Merge pull request #694 from dragos/issue/on-the-fly-compiler-interface-2

Added the ability to compile the sbt compiler-interface on the fly
The ScalaBuilder chooses the Scala compiler version based on the project class path.

This commit adds the ability to build with either the current (at the time of this
work, 2.11) Scala compiler, or a previous version. The previous version is chosen
when a project is in “compatibility” mode, and the `-Xsource:` flag is used to put
the type-checker in the right mood.

The Scala builder now chooses a ScalaInstallation based on the Scala version on the
class path. The builder infers what Scala installation best matches the Scala Library.
It works by using the resolved class path, meaning that the Scala class path
container (if present) is honored as-is. If the `-Xsource` flag is set, but the Scala library is
still the platform version (2.11 at this time), the Scala library *on the classpath*
what determines the builder version of Scala.
Merge pull request #697 from dragos/issue/on-the-fly-classloaders-2

Build support for several versions of Scala
better scala container addition tagging