I've added version ranges to the JMX package imports. The version of
the org.osgi.jmx.framework package, which we implement, changed from
1.5 to 1.7 between r4.2 and r5 of the enterprise spec. This means
version 1.0.0 of our jmx-bundle won't resolve against r5 enterprise
APIs. Is this what you
Hi Holly,
Yes, JMX is a bit of interesting spec in that the packages are not
versioned on their own, but rather follow the version of the packages
that they mirror over JMX.
So for example org.osgi.jmx.framework mirrors org.osgi.framework and
org.osgi.jmx.service.cm mirrors org.osgi.service.cm
Thanks David, that helps me understand what's going on. Based on your
explanation, though, it seems to me like jmx actually needs to be
fairly closely coupled to the framework version. Backwards
compatibility isn't enough, since the jmx classes actually implement
the framework interfaces. For
Hi Holly,
On 20 July 2012 17:03, Holly Cummins holly.k.cumm...@googlemail.com wrote:
Thanks David, that helps me understand what's going on. Based on your
explanation, though, it seems to me like jmx actually needs to be
fairly closely coupled to the framework version. Backwards
compatibility
