Problem in OSGi with net.imglib2 package

In plain OSGi, bundles define their dependencies as so called imports. A bundle states that it requires another by package name (e.g. import net.imglib2). However, this implies that the package names have to be unique, i.e. a package is not split across several bundles. At the moment the package net.imglib2 is split into imglib2-core and imagej-commons. In our OSGi world this doesn't work. So what are the plans to refactor the packages in imagej-commons?

Thanks!!

Christian

The issue concerns the net.imglib2 package split between imglib2-core and imagej-commons, but names no files or tests. Start by reviewing how those two bundles define and export the package in the OSGi setup. Done means an agreed refactoring plan that gives the package a compatible ownership arrangement.

Written by the indexing model from the issue text.