Avoid calling Option.get
Don't connect and disconnect a model to the document.

This is entirely unnecessary, an annotation model is connected for the lifetime
of an editor. This gives rise to a race condition in `Save`.

Fixed #24.
Cleanup in error annotations.

Don't accumulate annotations in "previousAnnotations" and don't create error
markers during reconciliation.

Fixed #47.
Merge pull request #52 from dragos/issue/fix-save-failed-24

Save Failed assertion failed and small cleanups in error annotations.
Use Tycho 0.16 and updated scala versions in POM

* Updated the README build example to use the ``scala-ide-stable``
  profile. Why? Because this is going to make it easier for people to
  start hacking as it is the stable update-site. As a consequence,
  ``eclipse-indigo`` is now used (that the Eclipse version that is
  currently  supported by the 3.0.0 IDE release).

* Removed scala-2.9.x profile because Play 2.1 only supports Scala 2.10
Created a TestSuite class for running all tests in the regression suite

* Updated the POM to run the new ``TestSuite`` class.
Graceful handling of parsing errors from template compiler

* Because the Play template compiler throws an exception as soon as a parsing error is
encountered, calls to the Play template compiler are now wrapped in a ``Try``.
It's the responsability of the calling code to handle the failure case as it
makes sense.

* Use ``Annotation`` for reporting both parsing and compilation errors from
template files. The implication of this is that compilation  errors are no longer
displayed in the Problem View or the Package Explorer.

* Because we now solely use Annotation, we no longer need to use the Eclipse
extension point for defining new markers (look at the deleted lines in
plugin.xml).

* Finally, I'm aware that the code could use some more clean-up, but my intention
was to minimize changes as we plan to release 0.1 possibly next week already.

Fixes #29
Merge pull request #54 from dotta/issue/catch-errors-from-template-compiler-29

Issue/catch errors from template compiler 29
Don't restrict where templates can be located..

.. but log a warning in the Log (in case this proves a bad idea).

Fixed #45.
Defined the content type name for Play Template files

Fix #62
Add a few more syntax classes for coloring.

* 'symbol
* numeric literals
* multi-line strings

Fixed #44.
Merge pull request #63 from dotta/issue/no-content-type-for-play-template-file-62

Defined the content type name for Play Template files
Updated scm config in POM required to extract the GH hash
Adds a preference and an project preference page

The preference is initialized with framework defaults (play.api.templates._, play.api.templates.PlayMagic._).
It can be overriden at the project level, in the project properties.
Changes are not applied directly, as we are currently lacking a real builder.

Fix #35.
Automatically add Scala nature when opening Play2 Template editor

Java Play2 Template project don't have the Scala nature by default, and this
caused an exception to be thrown whenever the user tried to open a Play2
Template editor because the editor needs access to the ``ScalaProject``
facilities.

The implemented solution is to automatically add the Scala nature if a project
doesn't have it.

Note that ``TemplateCompilationUnit.scalaProject`` is no longer ``lazy``
because I want the code to fail fast if a ``ScalaProject`` cannot be created.

Fix #33
Minor clean-up in code and POM

* Removed unused import in ``RouteTestSuite``.
* Added explicit return type on public methods.
* Remove comment in POM about Play 2.0.x support.
Merge pull request #56 from dragos/issue/more-syntax-colors-44

Add a few more syntax classes for coloring.
Merge pull request #43 from skyluc/issue/additional-imports-35

Adds a preference and an project preference page
Merge pull request #64 from dotta/issue/detect-missing-scala-nature-33

 Automatically add Scala nature when opening Play2 Template editor
Now plug-in compiles against against Scala IDE 3.0.0

* The class ``LiteralAutoEditStrategy`` is only available in the Scala IDE
  master (i.e., 4.0.0), so I had to remove the usage Removed unused imports
* (which were also causing compilation issues)