Do you think that OSGi will evolve its package version numbers in a way
similar to the Eclipse version numbering schemes? That is, does it make
any sense today to spec Import-Package elements along the lines of
org.osgi.service.component;version="[1.0.0,2.0.0)",
org.osgi.service.http;version="[1.2.0,2.0.0)"
with an expectation that versions of these services fitting these ranges
will be binary backward compatible?
What is the best practice recommendation for people writing bundles now
but anticipating changes in OSGi 2.0/5.0/whatever the next real big spec
change is...
Jeff
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
