jars (good).
--
View this message in context:
http://www.nabble.com/non-jar-as-bundle-unit-tp15805581p16002323.html
Sent from the Apache Felix - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
unless the general consensus of the group is that the
jar-to-bundle mapping is too central to use OSGi/Felix otherwise.
Thanks,
Jared
--
View this message in context:
http://www.nabble.com/non-jar-as-bundle-unit-tp15805581p15827584.html
Sent from the Apache Felix - Users mailing list archive at Nabb
th -output c.jar c.bnd
>
> where a.bnd, b.bnd and c.bnd contain instructions for pulling classes
> and resources from the project classpath into the relevant bundles.
>
> more details can be found here: http://aqute.biz/Code/Bnd
>
> HTH
&g
bnd contain instructions for pulling classes
and resources from the project classpath into the relevant bundles.
more details can be found here: http://aqute.biz/Code/Bnd
HTH
Thanks,
> Jared
>
> --
> View this message in context:
> http://www.nabble.com/non-jar-as-bundle-unit-tp1580
Well, you can install "exploded" bundles, i.e., a directory with a
META-INF/MANIFEST.MF file, using a URL like
"reference:file:/path/to/directory/" but that is about it. This probably
won't help you.
You could achieve what you want if you are willing to create a hacked
version of Felix.
->
gt;
> I ask because our current build system does not lend itself toward
> arbitrary
> jarring of the chunks of code that we'd want to make into bundles.
>
> Thanks,
> Jared
> --
> View this message in context:
> http://www.nabble.com/non-jar-as-bundle-unit-tp1580558
here.
I ask because our current build system does not lend itself toward arbitrary
jarring of the chunks of code that we'd want to make into bundles.
Thanks,
Jared
--
View this message in context:
http://www.nabble.com/non-jar-as-bundle-unit-tp15805581p15805581.html
Sent from the Apache Fel
7 matches
Mail list logo