aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Bosschaert <david.bosscha...@gmail.com>
Subject Re: Aries JNDI dependencies
Date Mon, 16 Jan 2012 15:54:38 GMT
On 16 January 2012 14:41, David Bosschaert <david.bosschaert@gmail.com> wrote:
> Hi Tim,
>
> I'm not sure I completely follow this. Would this not limit the
> reusability of the JNDI uber-bundle? I mean I can equally see use
> cases for an 'uber' bundle where the user *does* want to use the
> blueprint functionality and creating a separate 'uber' bundle for
> every type of use of the functionality certainly isn't right.
>
> I looked at the jndi-url module. This module already declares the
> blueprint dependency as optional and the code in there is written
> defensively to work in cases where blueprint is available and where is
> isn't. Shouldn't we do this for the current 'uber' bundle too?

I've done this now in commit 1232044.

Hope that's ok with everyone. If not I'm happy to revert...

I'll look at changing the SLF4J dependency to an OSGi Log Service
dependency next...

David

Mime
View raw message