In the immortal words of @paulp:
 "Can we please, please not do this:

  import PatternMatchingStats._
  import global.{phase, currentRun, Symbol,
    Apply, Bind, CaseDef, ClassInfoType, Ident, Literal, Match,
    Alternative, Constant, EmptyTree, Select, Star, This, Throw, Typed, UnApply, (...)"

Let's simplify merges, by making our imports mono-line !

Thanksfully, in the IDE, we don't do (many) *mutli-line* braced Imports, so it
was enough to filter them with the following one-liner:

for i in `find ./ -type f -name "*.scala"`; do perl -nle 'if (m/^(\s*)import\s([^\n]+?){([^}]*?)}$/smg){my ($s,$x,@y)=($1,$2,split /,\s*(?!_|\s)/,$3); foreach $dep (@y){$dep =~ s/^\s+|\s+$//g; $dep=($dep =~ m/=>/)?"{ $dep }":$dep;print "${s}import $x$dep";}} else {print $_;}' $i > $i.nu; mv $i.nu $i; done

Note the negative lookahead to avoind busting final wildcards in
braced imports (see the Spec version 2.9, section 4.7), .

If you want to do this on a repo that contains multi-line braced
imports, look into unsetting the special variable '$/' of perl, and
relax the condition on the presence of new lines in the second capture
group of the regex above. I strongly advise against doing this
automatically on such a repo, though.

Fixes of multiline braced imports (manual).

Let this be the end of this lazy, messy, mergepain-inducing practice.

Fixing test relying on braced import.
Update Scalastyle Maven plugin to version 0.3.2
Merge pull request #448 from sschaef/t-scalastyle-update

Update Scalastyle Maven plugin to version 0.3.2
Merge remote-tracking branch 'origin/pr/444'
Merge pull request #439 from huitseeker/split-monoline-multiple-imports

Removes needless braced imports to ease merges.
Semantic Highlighting now works on classfile source attachments

Created a `ScalaCompilationUnitEditor` that contains the logic common to
both the `ScalaSourceFileEditor` and the `ScalaClassFileEditor`. In particular,
the logic needed to install/dispose semantic highlighting is encapsulated in
`ScalaCompilationUnitEditor`.

It is worth pointing out that the initialization of the Semantic Highlighting
engine is different for the two editors. On the one hand, on an editable scala
source, semantic highlighting is triggered by the reconciler. On the other
hand, for a classfile source attachement, no reconciler is needed (because the
source file can't be edited), hence semantic highlighting needs to be forced at
initialization. This is why in `ScalaCompilationUnitEditor` we have the
following two additional abstract methods

* `forceSemanticHighlightingOnInstallment`
* `createSemantichHighlighter`

This commit comes with no tests because it is not possible to avoid the loading
of UI classes.

Fix #1000939