How does exporting a package help? I don't have the package in my bundle, so that doesn't make sense to me.
Alasdair On 12 July 2011 15:28, Peter Kriens <[email protected]> wrote: > As you're VERY closely tied to the spec package I would just export the > package ... > > Kind regards, > > Peter Kriens > > > > On 12 jul 2011, at 11:21, Alasdair Nottingham wrote: > > > No it doesn't. I'm taking advantage of the "deferred resolution" > behaviour > > of DynamicImport-Package rather than the up front resolution. My scenario > is > > that I have a bundle that registers the OSGi MBeans as services. I want > to > > register the framework mbeans, but defer registration of the ConfigAdmin > etc > > MBeans until the services are available. An optional import would be > > resolved up front and if I don't have a ConfigAdmin provider at startup > the > > bundle would never be able to deal with the ConfigAdmin MBeans. This is > not > > what I want. > > > > Alasdair > > > > On 12 July 2011 10:01, Peter Kriens <[email protected]> wrote: > > > >> Doesn't optional then work better (if you know the packages)? > >> > >> Kind regards, > >> > >> Peter Kriens > >> > >> On 7 jul 2011, at 20:00, Alasdair Nottingham wrote: > >> > >>> Hi, > >>> > >>> I have just created a bundle that does a DynamicImport-Package. Is it > >>> possible to get the Maven bundle plugin to generate the package version > >>> range in the same way it does for normal Import-Package statements? > >>> > >>> Thanks > >>> Alasdair > >>> > >>> -- > >>> Alasdair Nottingham > >>> [email protected] > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > >> > > > > > > -- > > Alasdair Nottingham > > [email protected] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Alasdair Nottingham [email protected]
