felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carsten Ziegeler <cziege...@apache.org>
Subject Re: Problems with bundle plugin [Fwd: Re: Support for OSGi]
Date Fri, 11 Jan 2008 09:57:27 GMT
Niall Pemberton wrote:
> On Jan 11, 2008 9:09 AM, Carsten Ziegeler <cziegeler@apache.org> wrote:
>> Stuart McCulloch wrote:
>>> Yes - and the way the plugin does this is by passing the complete classpath.
>>> But then you're back to having to tell Bnd exactly what you want to export
>>> and what you want to keep private...
>> Yes, and I think this is the better (and in the end easier) way to go;
>> for a quick
>> "adaption" of OSGi in commons I suggested to use the exclude package *
>> (but obviously without thinking it through to the end).
>> For commons io we already listed all packages explicitly and I think we
>> should do this for the other commons projects as well. This allows to
>> keep some stuff private.
> Using which approach - configuring plain manifest entries in the jar
> plugin (as commons io has) or using the bundle plugin?
Both :) You explicitly specify your exports and private packages in the
bundleplugin configuration and let the bundleplugin do the rest (like
generating the imports etc).

Carsten Ziegeler

View raw message