Add a scala-version suffix to the library version number.
The Scala compiler translates lazy values earlier (in typer) from 2.10.1 onwards. This makes some heuristics
fail.

We needed to fixes in `namePosition`:

* don't call `lazyAccessor` on a lazy accessor (you'd get `NoSymbol`). Make sure you only call it on a lazy field that backs up a lazy val
* identify `lazy val Pattern(lv) = ..` inside `DefDef`s now (prior to 2.10.1 the `DefDef` would be added several phases later).

This fixes the IDE build for 2.10.1 and (probably) 2.11.0
Merge pull request #4 from dragos/fix-lazyvals-in-2.10.x

Fix `namePosition` for 2.10.1 and 2.11.0
Merge pull request #3 from misto/master

Scala-Version Suffix
Don't sign the artifacts per default

Instead, use the release-sign-artifacts profile to sign.
Updated Tycho versions to something more recent, see also:
http://wiki.eclipse.org/Tycho_Release_Notes/0.12
Revert "Add the Scala version number to the artifact id."

This reverts commit 07b00e413d185c53332118711ff12be75f4df994.

Conflicts:
	org.scala-refactoring.library/pom.xml

decreasing Tycho to 0.12
Progess with the strong tycho/junit dependencies
re-ordering plugin repositories (helps with mirror configurations)
Sanity bump of maven-javadoc-plugin
Merge pull request #6 from huitseeker/bug/bump-tycho-version

Updated Tycho versions to something more recent
Release version to 0.6.1
Set version to 0.6.2-SNAPSHOT
Add organize imports refactoring that collapses multiple selectors into a wildcard

Has a configurable number of selectors above which it will perform the refactoring, as well as an 'exclude' parameter to exclude certain packages.

I think it should not cause compilation errors in a working file. It refuses to do the collapse when

- The selectors already contain a wildcard
- The selectors contain a rename
- It would cause an implicit conversion to get into scope
- It would cause a currently explicitly imported name to collide with a wildcard imported name, if the precedence gets lowered by changing it into a wildcard
- It would cause a currently wildcard-imported name to collide with a new wildcard-imported name.

The last two are determined by just looking at the imports. This makes it more conservative than necessary. For example, suppose that we import `scala.collection.immutable._` and we don't use `HashMap`, and a bunch of names from scala.collection.mutable which could be eligible for collapsing, it won't do it, because it doesn't know whether the `HashMap` from the two packages will collide. If you look at the `Tree` instead of just the `List[Import]`, you could determine that `scala.collection.immutable.HashMap` is not used, and decide that it's safe to import both `scala.collection.mutable` and `scala.collection.immutable` can be imported with a wildcard.

However, that would require more code changes.

Also, it currently just does nothing for imports that satisfy any of the rules above. We could optionally refine this by doing a wildcard after all, and hiding the colliding members.
Merge pull request #9 from eamelink/collapse-imports

Add organize imports refactoring that collapses multiple selectors
Adapt expected CU dependencies for Scala 2.10.1

SI-7163 improved something related to annotation positions, so we need
to adapt our expectations.
Put the JavaDoc generation behind the release profile.
Fix change w.r.t overriding API's change of semantics in Scala's 0eff6cd

overridenSymbol became assymetric and does not reports abstract that look like they would override a concrete.
it was used here in a symmetric manner (i.e. reporting overridees as well as overrides)
Fixing test w.r.t. 2.11.x branch
Split monoline multiple (braced) imports to ease merging

See https://github.com/scala-ide/scala-ide/pull/342