Well, I was wondering about this too, but I think if there is an impact,
we can just make the impacted subprojects depend on the already released
version of compendium until they are made compatible with the newest
version. I think that should work.
-> richard
Christian van Spaandonk wrote:
Hi Stefano,
makes sense to me, I created a JIRA issue for this [1]. I would assign
it to myself but I am not yet confident I have a clear overview of the
impact this may have for other modules...
friendly,
Christian
[1] https://issues.apache.org/jira/browse/FELIX-514
Stefano Lenzi wrote:
Hi All,
The issue FELIX-510 is related to the deploymentadmin bundle which is
an implementation of the Deployment Admin Specification defined in
the OSGI R4.1 Compendium document. At the moment the deploymentadmin
bundle contains, in its source folder, all the new API defined by the
OSGi R4.1 which are not contained in any other Felix bundle.
I think that new API should be moved elsewhere and in particular the
natural cradle are the o.a.f.:org.osgi.compendium and
o.a.f:org.osgi.core bundles.
Moving the new classes to compendium or core it will require
releasing a new version of those bundle. Regarding that I think that
we should change the version schema used for the core and compendium
bundle. I think that the best version schema for the version schema
adopted by the Felix Common subproject.
What do you think?
Ciao,
Stefano "Kismet" Lenzi
