[maven-release-plugin] prepare release parent-3.2.0
[maven-release-plugin] prepare for next development iteration
Remove obsolete files
Replace all OSGi Bundle-Requirement with Import-Package

Bundle-Requirement has a lot of cons since it implies that the
consumer has knowledge of what bundle it is that provides what
packages in the OSGi runtime. In many cases its use leads to
conflicts.

The recommended way is to always use Import-Package instead and
combine that with 'uses' annotations on the exported packages. The
'uses' clause gives the OSGi runtime a hint on how to configure
classloaders in situations where there are several providers of one
package.

Good article on the subject:
http://olegz.wordpress.com/documents-and-articles/osgi-uses/
Limit version of com.google.inject to "[1.3.0,1.4.0)"

The 1.3.0 is Guice official release. The maven runtime bundle delivered
as part of m2e contains 'sisu' whith version 1.4.0 of com.google.inject
but with no com.google.inject.multibindings. This leads to a conflict
if this requirement is missing since the OSGi loader will attempt to
load the latest com.google.inject package.
Merge branch 'dev' into kepler