Not a bug a Felix bug, just an OSGi, Maven2 plugin technique.
For example, I might use a number of Apache libraries, which are not OSGi
ready, and I'd like to avoid the overhead of adding 3 or 4 separate bundles
in Felix.
Using a pom like the one below, one can download 3,4,5,6,... Apache jars,
extract the classes you need, and then merge them into one apache-utils.jar
and finally export the packages I need for my project. Then I only need to
install one bundle in lieu of 6 bundles.
For Grizzly I was using some internal packages that were probably not meant
for export. So the pom I used as an example downloads the 4 (5?) jars that
make up Grizzly, combines them into 1 jar, and exports the actual packages I
use. I only need to install 1 Grizzly jar into Felix nstead of 4 or 5 as
well.
I do similarly for SleepyCatJE, etc...
Its just a technique to create a bundle from a set of jars. It is not a
work-around for any Felix bug.
This may very well be common knowledge, but I thought I'd mention it and
show an example.
R.
On Sat, Nov 22, 2008 at 12:57 PM, Richard Jackson <richard.jackson_at_gmail.com
> wrote:
> Have you asked about this on the felix list? I know there where some
> bugs in older Felix builds around split packages and fragments but I'm
> not up on the details of the issue.
>
> Richard
>
>