Split out a parent POM for all SciJava projects to be wrapped into bundles

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Fix parent POM

The parent POM is not supposed to build bundles itself, instead just
providing the configuration of the Maven plugins so that its children
can generate bundles.

So let's just put the executions into a profile that is activated by
default only if src/main/java exists.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Make the parent POM an aggregator

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
We need to set the required execution environment property

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Make a clean slate before rebuilding the scijava bundle

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Rebuild the scijava bundle

The trick was performed by: mvn

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Do not hardcode the exported package in the parent POM

It needs to be different in pretty much every child project...

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Add a project to build an ImgLib2 bundle

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Avoid embedding scijava-common into the ImgLib2 bundle

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>