I updated trunk to include the latest compendium code, so this should be
ok in trunk now.
-> richard
On 7/17/09 10:06 AM, Guillaume Nodet wrote:
Karak includes a snapshot of the jmx ri from the OSGi alliance, but i
will try to upload a new one with a downgraded version.
I think felix should also upgrade to the latest package.
Unfortunately, I won't be able to do that before I come back from
vacations in 10 days...
On Friday, July 17, 2009, Richard S. Hall<[email protected]> wrote:
Perhaps that is why it is set that way. :-)
We need to update our compendium classes to R4.2, I was waiting for the
official release, but I can probably grab a snapshot and use that since the
release is close. I am traveling and won't likely get this done until next
week, though.
I wonder, does Karaf really depend on some feature of the unreleased Service
Tracker? If not, why don't we just downgrade the version?
-> richard
On 07/16/2009 04:36 PM, Moloney, Tim M wrote:
I noticed that the trunk currently has Karaf configured to use the
Equinox framework. (Shouldn't we be eating our own dog food?)
karaf/assembly/src/main/filtered-resources/etc/config.properties:
karaf.framework=equinox
When I changed this to felix, I get the following error in Karaf.
ERROR: Error starting
mvn:org.osgi/org.osgi.impl.bundle.jmx/4.2.0.200907080519
(org.osgi.framework.BundleException: Unresolved constraint in bundle
org.osgi.impl.bundle.jmx [19]: package;
(&(package=org.osgi.util.tracker)(version>=1.4.0)(!(version>=2.0.0))))
org.osgi.framework.BundleException: Unresolved constraint in bundle
org.osgi.impl.bundle.jmx [19]: package;
(&(package=org.osgi.util.tracker)(version>=1.4.0)(!(version>=2.0.0)))
at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3393)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1597)
at
org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1077)
at
org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:263)
at java.lang.Thread.run(Thread.java:619)
The system bundle is exporting org.osgi.util.tracker,version=1.3.3 which
(I think) is in the default setting of
org.osgi.framework.system.packages.
Should the version number of org.osgi.util.tracker be changed to 1.4.0?
I think that it was explicitly set to that in earlier versions of
config.properties. As a work-around, adding "org.osgi.util.tracker;
version=1.4.0" to org.osgi.framework.system.packages.extra fixes the
problem.
Tim Moloney The reasonable man adapts himself to
MRSL the world; the unreasonable one persists
2015 Cattlemen Road in trying to adapt the world to himself.
Sarasota, FL 34232 Therefore all progress depends on the
(941) 377-6775 x208 unreasonable man. George Bernard Shaw
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
