Enabled the memory test in the new build

The test is run using 'memory-test' profile on org.scala-ide.sdt.core.tests
The full command line to run the test from org.scala-ide.sdt.build:
mvn --projects ../org.scala-ide.sdt.aspects,../org.scala-ide.sdt.core,../org.scala-ide.sdt.core.tests -P scala-2.10.x,memory-test clean integration-test
Correct handling of source Scala libraries on the class path.

If a dependent project provides a Scala library as source, use the output directory
as the bootclasspath for the current project.

Don't filter out the Scala library from the class path. This allows compiling the Scala library itself.
Show verbose messages from the presentation compiler.
Clean file handle on refreshing changed files

The custom code I wrote to read an IFile was not releasing the file
handle correctly.
It was eventually closed when the object was GCed.
Replaced the code with some internal jdt util method.
Removed the incorrect method

Fix #1000909
Merge pull request #116 from skyluc/issue/memory-test-1001067

Enabled the memory test in the new build
Create fatal errors when a refactoring's initial check yields an error.

Until now, we created normal errors, which were shown in a wizard page,
and because they were non-fatal, the refactoring still tried to execute,
resulting in exceptions in the log file. Now we use fatal errors, which
immediately abort a refactoring and show the error message in a window.

Fixes scala-refactoring #76
Handle invalid target packages in the Move participant.

When the target package of a move refactoring cannot be found (e.g. because
the target is not a source folder), we abort with a warning. The user can
then still move the file, but he will be warned that the source won't be
changed. The JDT doesn't warn the user but simply moves the file without
refactorings its content.
Integrated reviewers comments.
Merge pull request #118 from skyluc/issue/unreleased_file_handle_1000909

Clean file handle on refreshing changed files
Merge pull request #119 from misto/issue/move-class-invalid-target-1001044

Handle invalid target packages in the Move participant.
Better matching between file-system paths and workspace resources.

A file-system path may correspond to several resources in the workspace. We used to choose
the first one, which lead to build errors being attached to the top-level project in nested
project setups, even when the error belonged to a nested project.

Fixes #1000734, #1000621, #1000881. Should be back ported to 2.0.x
Formatting changes.
Merge pull request #120 from dragos/issue/errors-attached-to-parent-project-1000621

Better matching between file-system paths and workspace resources.
Add configuration for editor 'surround selection' feature. 

Each character can be individually enabled. By default they are off.

Fixes #1001034
Remove workaround for #2296 scala compiler bug since it was recently fixed (neeeds to be ported to 2.9 as well), review by @dragos
Merge pull request #80 from scala-ide/issue/cleanup-for-2296-scala-bug

Remove workaround for #2296 scala compiler bug
Revert "Merge pull request #80 from scala-ide/issue/cleanup-for-2296-scala-bug"

This reverts commit 3441effa2ef9c58bc6baa8cea76496f3f771b1ae, reversing
changes made to 2f2d6a0ff943620822d1f36aa4a26d079cf9e4d2.
Merge pull request #122 from dragos/issue/optional-surround-braces-1001034

Add configuration for editor 'surround selection' feature. 
Merge pull request #117 from dragos/issue/separate-runtime-compiletime-lib-1000729

Correct handling of source Scala libraries on the class path.
Forgot one file.