Hello,
Well, I am sorry for my naive question but in this old email,is Mehta
means that he can't use external libraries in his bundles because
everything that is imported into a bundle, needs to be a bundle itself?
I am new to OSGi, that's why I am asking.
I wrote a simple bundle, that imports a library (something with gsm
modem communication for the record). In manifest file (in eclipse) is
reported an error about not importing a package, that I use at my source
code (the lib for the sms's). So I conclude from all this that whatever
you import as 3rd party library must be another bundle(!?) But this is
somehow weird, on the contrary of what the specification reports! At the
r3 book, look at page 588 at the Bundle-Classpath Section. Isn't this
the section that describes this exact situation? Xmmm
I am really sorry if I am asking nonsense..... :-[ :-[ :-[ :-[
There is always a starting point :-P
Best Regards,
Aggelos Mpimpoudis
Nikunj Mehta wrote:
Hi folks,
I have had one nasty practical problem with OSGi. Every time I find
the need for a third party library, I have to figure out how to get it
bundle-ized. On top of that, I am using Maven, which means I need to
get a Maven-ized, bundle-ized version of the library. While doing this
once is not such a big deal, it has acted as a major deterrent in
using external libraries.
How do people overcome this problem? Can OSGi provide a standard
solution to this major barrier to adoption?
Thanks,
Nikunj
_______________________________________________
OSGi Developer Mail List
[email protected]
http://www2.osgi.org/mailman/listinfo/osgi-dev
--
Dept. of Informatics & Telecommunications, University of Athens
Athens, Greece
GSM +306942075153 / Msn: [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
_______________________________________________
OSGi Developer Mail List
[email protected]
http://www2.osgi.org/mailman/listinfo/osgi-dev
