Removed the extra source folder in sdt.core that allowed master to compile with
both Scala 2.9 and Scala 2.10

Fix #1001674

(cherry picked from commit 5871ac2602e838417d62c2cab2c29f77751d2b25)
JVMUtil went away, workaround that.

(cherry picked from commit 2dfb6f4d66cfb5e49839807d37b10bb084935ca3)

Conflicts:
	org.scala-ide.sdt.core/src/scala/tools/eclipse/javaelements/ScalaJavaMapper.scala
Removed the Refined build manager.

Fixes #1001422

(cherry picked from commit f8c5241c2e494814cdc6c87dc62852fa772d1640)

Conflicts:
	org.scala-ide.sdt.core/src/scala/tools/eclipse/buildmanager/sbtintegration/EclipseSbtBuildManager.scala
Removes non-plugin reference to junit

It is provided as a bundle in the test plugins, it doesn't need to be added anywhere else.

(cherry picked from commit 0da9d32a69b69a91e88db940fb1972cb4268166f)

Conflicts:
	org.scala-ide.sdt.core.tests/META-INF/MANIFEST.MF
	org.scala-ide.sdt.debug.tests/META-INF/MANIFEST.MF
Applies changes needed to compile against Juno

Updates the jdt dependencies.
Implements the added and modified abstract methods.
Ligth cleanup of the poms.

(cherry picked from commit 26261aeac6f683e6a64f599e790790532a6a2fc8)

Conflicts:
	pom.xml
Adds a kepler profile to the build

For when we need a kepler only build

(cherry picked from commit 6b159c9471c82221bbb15300e39c3bc0aa0374b2)
Depend on mockito-core instead of mockito-all in the integration test projects.
Additionally, exclude dependency on org.hamcrest:hamcrest-core.

This fixes test failures on Kepler caused by conflicting versions of
hamcrest-core present on classpath: version 1.1 embedded in mockito-all and
version 1.3 pulled in as P2 dependency.
(cherry picked from commit 4e2ff88760b2326fa09ea946877af73110645f90)

(cherry picked from commit 32e6cbb12706b729588c34c1a89aceaab4499bb5)
Add scala-xml and scala-parser-combinator dependencies for the 2.11.x profile.

(cherry picked from commit a7fab2ad0b81d59b9e246b35840f030761a11fc8)
Add test ouput to file when test fails

(cherry picked from commit c70bf11326b9524404e81821dfcddd5798b4433f)
Delete old plugin signatures

(cherry picked from commit 214c6822b0f610937f81c2c791ba385c62c3d18c)

Conflicts:
	org.scala-ide.sdt.core/plugin.xml
	org.scala-ide.sdt.core/src/scala/tools/eclipse/Nature.scala
Updated sbt.version to 0.13.0-RC4

(cherry picked from commit f55ae2338f7058683aaa96a0cf16a873c616ef8b)

Conflicts:
	pom.xml
Updated sbt.version to 0.13.0-RC5

(cherry picked from commit e1815ed519ab93abaf35b514331af0a6fcc54a87)
Updated our build to use Zinc artifacts

Updated our build to use the Zinc artifacts built and published by dbuild.  The
main advantage is that we no longer need to build and publish the Sbt artifacts
(which are exactly the same used by Zinc) that are used in the Scala IDE for
incremental compilation.

(cherry picked from commit 6d40a3cd657cb4c5c895fd00946175198f6fcb9b)

Conflicts:
	org.scala-ide.sbt.full.library/.classpath
	org.scala-ide.sbt.full.library/pom.xml
	pom.xml
Removed unused properties and small cleanup in POMs

* Removed any reference to 2.9 profile
* Removed special-casing of dependencies due to Scala 2.9 (this is
  no longer needed as we dropped support for 2.9 a while ago)
* Removed a few properties that were not referenced.

(cherry picked from commit 68914958ca78b51a44ff8aaca41e712a44cc498e)
Do not export sbinary and jline packages in ``org.scala-ide.sbt.full.library``

We don't seem to need to export the sbinary and jline packages. Moreover, we
used to export these packages with the **wrong** version number, i.e., we were
using the ${sbt.version}, instead of the actual version the sbt build file
declared for these dependencies. Hence, I think we are better off not exporting
these packages anymore in the MANIFEST produced for
``org.scala-ide.sbt.full.library`` bundle.

(cherry picked from commit acad4154ad04dc923210d6744e86e9965d00cb02)
Switch to cross-compiled versions of Scala modules.

For the moment, only `scala-xml` is cross compiled.

(cherry picked from commit 29bb0a4a27f08fd083f4b7419703b8b4b202babc)
Switched to the new groupID for scala-xml.
(cherry picked from commit e7f84b0ad2f0fb8fe4ae8feb32d1a8abafc62647)
Switched to cross-compiled scala-parser-combinators.
(cherry picked from commit 99d87bb0f9126a8d813bc5ef893d159aa53f3edf)
Added a ``FlakyTest.retry`` combinator to be re-run tests known to be flacky

In our test suite we have a number of tests that are known to be flacky. The
``FlakyTest.retry`` combinator re-executes the same time up to N times (where
N is defaulted to 5 at the moment).

While we should of course strive to fix all sources of flackiness in tests, this
is a pragmatic solution to prevent spurious build failures.

(cherry picked from commit cfc7ee790a584350e8fc55b31dd917d9bd338e96)
Added Maven profile ``retryFlakyTests`` to reduce spurious test failures

Use the Maven profile ``retryFlakyTests`` for being robust against tests that
are known to be flaky. Inside Eclipse, you can achieve the same by passing the
system property ``-DretryFlakyTests=true``.

This profile should only be used by the Scala/IDE integration script to avoid
failing because of flakiness in our regression suite.

(cherry picked from commit c17e58a76500c5b10d8c9dab610b4e10db951763)