You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by Daniel Kulp <dk...@apache.org> on 2013/05/07 17:37:46 UTC
Why is bp-core exporting org.osgi.service.blueprint?
Can anyone tell me why blueprint-core is exporting an org.osgi.service.blueprint package? First off, I don't think it should be exporting any org.osgi packages at all as those should be in the api bundle. Second, that package isn't even part of the spec. There should be blueprint/container and blu[eprint/reflect (both from the api bundle).
Anyway, it's causing issues cause if I have blueprint-core on the classpath (to create namespace handlers), the bundle-plugin is adding an import to org.osgi.service.blueprint which doesn't exist if using Gemini.
I'd like to remove it from the exports, but I have a feeling that will trigger a "major version" bump. :-(
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
RE: Why is bp-core exporting org.osgi.service.blueprint?
Posted by Timothy Ward <ti...@apache.org>.
This is a known bug in Gemini blueprint. I'm sure that the Eclipse team would love a patch, I don't think they do a huge amount of maintenance on their blueprint implementation at the moment with the whole SpringSource/VMware/Pivotal thing happening.
Regards
Tim Ward
-------------------
Apache Aries PMC member & Enterprise OSGi advocate
Enterprise OSGi in Action (http://www.manning.com/cummins)
-------------------
> Subject: Re: Why is bp-core exporting org.osgi.service.blueprint?
> From: dkulp@apache.org
> Date: Tue, 7 May 2013 11:56:01 -0400
> To: dev@aries.apache.org
>
>
> On May 7, 2013, at 11:44 AM, David Jencks <da...@yahoo.com> wrote:
>
> > 121.13.5
> > Type Compatibility
> >
> > Two bundles are type compatible for a given class if they both load the same class object, or if either bundle cannot load the given class.
> >
> > To mitigate type incompatibility problems, a Blueprint extender must export the org.osgi.service.blueprint package. In the uses: directive, it should list any packages of classes that can be shared between the Blueprint extender and the Blueprint bundle. Blueprint bundles should import this package.
> >
> > confuses a lot of people :-)
>
> Well, Gemini doesn't seem to export it anywhere (at least in Virgo). Thus, bundles that import it cannot deploy into Virgo. :-(
>
> Dan
>
>
> >
> > david jencks
> >
> > On May 7, 2013, at 8:37 AM, Daniel Kulp <dk...@apache.org> wrote:
> >
> >>
> >> Can anyone tell me why blueprint-core is exporting an org.osgi.service.blueprint package? First off, I don't think it should be exporting any org.osgi packages at all as those should be in the api bundle. Second, that package isn't even part of the spec. There should be blueprint/container and blu[eprint/reflect (both from the api bundle).
> >>
> >> Anyway, it's causing issues cause if I have blueprint-core on the classpath (to create namespace handlers), the bundle-plugin is adding an import to org.osgi.service.blueprint which doesn't exist if using Gemini.
> >>
> >> I'd like to remove it from the exports, but I have a feeling that will trigger a "major version" bump. :-(
> >>
> >> --
> >> Daniel Kulp
> >> dkulp@apache.org - http://dankulp.com/blog
> >> Talend Community Coder - http://coders.talend.com
> >>
> >
>
> --
> Daniel Kulp
> dkulp@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
Re: Why is bp-core exporting org.osgi.service.blueprint?
Posted by Daniel Kulp <dk...@apache.org>.
On May 7, 2013, at 11:44 AM, David Jencks <da...@yahoo.com> wrote:
> 121.13.5
> Type Compatibility
>
> Two bundles are type compatible for a given class if they both load the same class object, or if either bundle cannot load the given class.
>
> To mitigate type incompatibility problems, a Blueprint extender must export the org.osgi.service.blueprint package. In the uses: directive, it should list any packages of classes that can be shared between the Blueprint extender and the Blueprint bundle. Blueprint bundles should import this package.
>
> confuses a lot of people :-)
Well, Gemini doesn't seem to export it anywhere (at least in Virgo). Thus, bundles that import it cannot deploy into Virgo. :-(
Dan
>
> david jencks
>
> On May 7, 2013, at 8:37 AM, Daniel Kulp <dk...@apache.org> wrote:
>
>>
>> Can anyone tell me why blueprint-core is exporting an org.osgi.service.blueprint package? First off, I don't think it should be exporting any org.osgi packages at all as those should be in the api bundle. Second, that package isn't even part of the spec. There should be blueprint/container and blu[eprint/reflect (both from the api bundle).
>>
>> Anyway, it's causing issues cause if I have blueprint-core on the classpath (to create namespace handlers), the bundle-plugin is adding an import to org.osgi.service.blueprint which doesn't exist if using Gemini.
>>
>> I'd like to remove it from the exports, but I have a feeling that will trigger a "major version" bump. :-(
>>
>> --
>> Daniel Kulp
>> dkulp@apache.org - http://dankulp.com/blog
>> Talend Community Coder - http://coders.talend.com
>>
>
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
Re: Why is bp-core exporting org.osgi.service.blueprint?
Posted by David Jencks <da...@yahoo.com>.
121.13.5
Type Compatibility
Two bundles are type compatible for a given class if they both load the same class object, or if either bundle cannot load the given class.
To mitigate type incompatibility problems, a Blueprint extender must export the org.osgi.service.blueprint package. In the uses: directive, it should list any packages of classes that can be shared between the Blueprint extender and the Blueprint bundle. Blueprint bundles should import this package.
confuses a lot of people :-)
david jencks
On May 7, 2013, at 8:37 AM, Daniel Kulp <dk...@apache.org> wrote:
>
> Can anyone tell me why blueprint-core is exporting an org.osgi.service.blueprint package? First off, I don't think it should be exporting any org.osgi packages at all as those should be in the api bundle. Second, that package isn't even part of the spec. There should be blueprint/container and blu[eprint/reflect (both from the api bundle).
>
> Anyway, it's causing issues cause if I have blueprint-core on the classpath (to create namespace handlers), the bundle-plugin is adding an import to org.osgi.service.blueprint which doesn't exist if using Gemini.
>
> I'd like to remove it from the exports, but I have a feeling that will trigger a "major version" bump. :-(
>
> --
> Daniel Kulp
> dkulp@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>