Daniel Fagerstrom wrote:
Reinhard Poetz wrote:
For those who're asking for a usecase: Imagine that bundle_C is the
forms block
and you want to deploy custom application A using version 1.0.0 of the
forms
block and custom application B using version 2.0.0 of it which is
_incompatible_
to 1.0.0.
OSGi R4 is extended with version ranges, so you can write:
Bundle-Name:bundle_A
Require-Bundle:bundle_C; bundle-version="[1.0.0,2.0.0)"
Import-Package:com.myCompany.bundleC.blah
Bundle-Name:bundle_B
Require-Bundle:bundle_D; bundle-version=2.0.0
Import-Package:com.myCompany.bundleC.blah
See:
http://dev.eclipse.org/mhonarc/lists/equinox-dev/msg00301.html
for Eclipse and
http://oscar.objectweb.org/oscar-alpha.html#changes
for more detailed documentation.
Here is a Eclipse bugzilla entry about the unsatifying state of the
documentation, with some documentation links:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=90358
And here is an interesting comparison between, among other things, the
package based export system in OSGi and the plugin based system in Eclipse:
http://dev.eclipse.org/newslists/news.eclipse.technology.equinox/msg00039.html
thanks, that's more than I expected and should cover all our usecases. We also
have to think about what this means for component management and the sitemap
(blocks:/) part of blocks.
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
