On 4/4/11 23:14, Donald Whytock wrote:
I see...thanks. I really appreciate learning this...it was starting
to drive me nuts.
Is this one of those good-idea-type things I should do in every bundle
from now on?
If you don't ever intend to run your bundle on very old OSGi frameworks,
then yes
You have to import it with status=provisional, since the Gogo API is
based on unreleased OSGi API, so it will change in the future and we are
warning you about this by making the status attribute mandatory.
- richard
On 4/4/11 17:17, Donald Whytock wrote:
Hi all...
I'd like to execute felix
Okay, I've tried the following:
org.apache.felix.service.command;status=provisional;version=0.8.0
and on load it comes up with missing requirement package;
($(package=org.apache.felix.service.command)(version=0.8.0))
On Mon, Apr 4, 2011 at 5:22 PM, Richard S. Hall he...@ungoverned.org wrote:
Not sure. If I look at the Gogo Command bundle, it does this in its
manifest:
Import-Package: org.apache.felix.service.command;status=provisional;ve
rsion=0.8,org.osgi.framework;version=1.5,org.osgi.service.log;ver
sion=1.3,org.osgi.service.packageadmin;version=1.2,org.osgi.servi
p.s. If you really can't figure it out, you can send me an example
failing bundle and I will look at it.
On 4/4/11 17:42, Richard S. Hall wrote:
Not sure. If I look at the Gogo Command bundle, it does this in its
manifest:
Import-Package:
After looking at your bundles, you are not creating OSGi R4 bundles, you
are creating OSGi R3 bundles. You must include:
Bundle-ManifestVersion: 2
Bundle-SymbolicName: foo
Technically, this isn't necessary to if you are just creating a bundle
that imports other packages normally,
I see...thanks. I really appreciate learning this...it was starting
to drive me nuts.
Is this one of those good-idea-type things I should do in every bundle
from now on?
On Mon, Apr 4, 2011 at 11:05 PM, Richard S. Hall he...@ungoverned.org wrote:
After looking at your bundles, you are not
7 matches
Mail list logo
