Peter, yup basically jar libraries.
2017-03-02 11:18 GMT+01:00 Peter Kriens <peter.kri...@aqute.biz>:
> When you talk about libraries are you talking about native libraries (i.e.
> DLL, .so) or just about Java JAR libraries?
>
> I suggest enRoute because reading your mail I think you have little
> experience with OSGi. Doing the enRoute tutorials will give you grasp of
> the terminology and concepts. Since everything works out of the box you do
> not spend a lot of time figuring out very basic things. Once you’re there
> you can throw away the parts you don’t like and add the parts you need. It
> is a lot easier to get started with a working system then trying to build
> that up from scratch.
>
> Kind regards,
>
> Peter Kriens
>
> On 2 Mar 2017, at 10:13, Mestiri Meher <meher.mest...@gmail.com> wrote:
>
> Thanks Peter for your answser,
>
> But does the enRoute way resolves the way of shared libraries between
> bundles ??
>
> If I'm going to need in my project lot of bundles and all of them need
> library ('A' + 'B') which is the best way to expose those libraries (as
> bundles) to all the other bundles living in the osgi context ?
>
> Thanks in advance
>
> 2017-03-02 10:07 GMT+01:00 Peter Kriens <peter.kri...@aqute.biz>:
>
>> Did you follow the tutorials on OSGi enRoute site?
>> http://enroute.osgi.org?
>>
>> Wrapping is nowadays not that necessary anymore as it used to be. For
>> many unwrapped libraries there are good alternatives that are OSGi.
>> Wrapping is a complicated thing to do because the consequences of using
>> OSGi sometimes go further than just the manifest headers.
>>
>> If you start with OSGi enRoute you can get up and working quickly after
>> which you can modify your working setup to suit your needs. For example,
>> logging with SLF 4J is setup out of the box.
>>
>> Kind regards,
>>
>> Peter Kriens
>>
>> > On 2 Mar 2017, at 09:42, Mestiri Meher <meher.mest...@gmail.com> wrote:
>> >
>> > Hello guys,
>> >
>> > I have another rookie question about osgi.
>> >
>> > I'm creating an osgi project with multiple bundles.
>> >
>> > I want to put all the same and shared dependencies of these bundles in
>> a service registry or anywhere in Felix context so all bundles can use
>> these shared libraries.
>> >
>> > What I understood is I have to having them as bundles too, so I found
>> the maven plugin that helps in wrapping those depepndencies into bundles.
>> >
>> > Correct me if I'm wrong but I think the steps are the following :
>> >
>> > 1/ wrap the dependencies into wrappes.
>> > 2/ install them as bundles into the felix.
>> > 3/ make those bundles start oncethe felix starts.
>> >
>> >
>> > Following this I'm having an issue with an sl4j logger dependency :
>> "slf4j.simple_1.6.1.jar"
>> > and the error is that I can not start the bundle..
>> >
>> > "org.osgi.framework.BundleException: Fragment bundles can not be
>> started."
>> >
>> > Could you please let me know if I'm following the right scenario and if
>> you have an idea on how I could resolve the slf4j dependency.
>> >
>> > Kind Regards,
>> > Meher
>> > _______________________________________________
>> > OSGi Developer Mail List
>> > osgi-dev@mail.osgi.org
>> > https://mail.osgi.org/mailman/listinfo/osgi-dev
>>
>> _______________________________________________
>> OSGi Developer Mail List
>> osgi-dev@mail.osgi.org
>> https://mail.osgi.org/mailman/listinfo/osgi-dev
>>
>
> _______________________________________________
> OSGi Developer Mail List
> osgi-dev@mail.osgi.org
> https://mail.osgi.org/mailman/listinfo/osgi-dev
>
>
>
> _______________________________________________
> OSGi Developer Mail List
> osgi-dev@mail.osgi.org
> https://mail.osgi.org/mailman/listinfo/osgi-dev
>
_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev
