ty simple. It's Java. (sarcasm).
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> On Fri, Jun 10, 2011 at 3:47 PM, Shamik Bandopadhyay <
>> sham...@gmail.com>wrote:
>> >>>>>
>> >>>>>
n 10, 2011 at 12:25 PM, sam lee
> wrote:
> >>>>>>> Try it and see. Does it work?
> >>>>>>>
> >>>>>>> I wouldn't try to reason Java complexity, OSGi.
> >>>>>>>
> >>>>>>>
t;>>>>>>>
>>>>>>>> Shamik,
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> I completely understand how you feel about making bundles out of
>>>>>>>
>>>>>>
>>>>>>> Thanks for your reply. Being a newbie, I'm finding a li'l hard to
>>>>>>> grasp the concept maybe. I agree, that embedding transitive dependency
>>>>>>> might not be the greatest idea since it contradicts OSGI fundamental
t;> out of a non-osgi .jar file.
>>>>>>
>>>>>>
>>>>>>
>>>>>> First, you may want to consider using Karaf. This product can ride of
>>>> top
>>>>>> of felix (or equinox), and it has a number
nto Felix, try using
>>> the
>>>>> following syntax:
>>>>>
>>>>> osgi:install wrap:mvn://version
>>>>>
>>>>>
>>>>>
>>>>> I haven't tried this in Felix, but in Karaf over the top of
On 10.06.2011 23:39, mvangeert...@comcast.net wrote:
> Do you feel that embedding all of a file's dependencies into a bundle
> is the right approach? I think it contravenes some of the core
> principles of OSGi to embed dependencies except in some rare
> corner-cases.
I'm not Justin, but..
Yes a
lson"
> To: users@felix.apache.org
> Sent: Friday, June 10, 2011 5:22:43 PM
> Subject: Re: Felix maven-bundle-plugin transitive dependency issue
>
> I would highly recommend not using resolution=optional with *
>
> It would be very atypical for *all* imports to trul
ot;
To: users@felix.apache.org
Sent: Friday, June 10, 2011 5:22:43 PM
Subject: Re: Felix maven-bundle-plugin transitive dependency issue
I would highly recommend not using resolution=optional with *
It would be very atypical for *all* imports to truly be optional. When you use
optional impor
araf over the top of Felix, this
>>>> will automagically wrap your non-osgi bundle. "Wrapping" in the process
>> of
>>>> using a tool to add osgi-stuff into a non-osgi .jar file's MANIFEST.MF
>>>> file. While this may not be the best approac
;> file. While this may not be the best approach for an operational
> >> environment, this will definately help you get your test stuff working.
> >>
> >>
> >>
> >> To make a more operational-ready bundle, you can use the bnd tool to
> wrap
> >> your existin
efinately help you get your test stuff working.
>>
>>
>>
>> To make a more operational-ready bundle, you can use the bnd tool to wrap
>> your existing bundle. Bnd is a very powerful tool and is pretty well
>> documented. Google it for more information.
>>
ol to wrap
> your existing bundle. Bnd is a very powerful tool and is pretty well
> documented. Google it for more information.
>
>
>
> Please let me know if this helps!
>
>
> ----- Original Message -
> From: "Shamik Bandopadhyay"
> To: users
ase, your build will break.
>>>
>>>
>>>
>>> A better approach is to identify those bundles that you are actually
>>> going to use (which you've already done), and deploy those into OSGi before
>>> you deploy your taxonomy dao bundle. A rul
users@felix.apache.org
Sent: Friday, June 10, 2011 2:52:09 PM
Subject: Re: Felix maven-bundle-plugin transitive dependency issue
Hi,
Thanks for your reply. Being a newbie, I'm finding a li'l hard to
grasp the concept maybe. I agree, that embedding transitive dependency
might not b
l-ready bundle, you can use the bnd tool to wrap
> your existing bundle. Bnd is a very powerful tool and is pretty well
> documented. Google it for more information.
>
>
>
> Please let me know if this helps!
>
>
> - Original Message -
> From: "Shamik Band
To: users@felix.apache.org
Sent: Friday, June 10, 2011 2:52:09 PM
Subject: Re: Felix maven-bundle-plugin transitive dependency issue
Hi,
Thanks for your reply. Being a newbie, I'm finding a li'l hard to
grasp the concept maybe. I agree, that embedding transitive dependency
might
e into OSGi before
>> you deploy your taxonomy dao bundle. A rule of thumb that I use is, if a
>> bundle is listed in the dependencies section of the pom, that bundle should
>> be available within OSGi.
>> >
>> >
>> >
>> > So, in short, try no
gt; >
> >
> >
> > So, in short, try not embedding any dependencies in your bundle; instead,
> deploying all of the necessary bundles into OSGi first. If that doesn't
> work, only then should you try to embed.
> >
> >
> >
> > Please let me know if
t;
> So, in short, try not embedding any dependencies in your bundle; instead,
> deploying all of the necessary bundles into OSGi first. If that doesn't work,
> only then should you try to embed.
>
>
>
> Please let me know if that helps!
>
>
> - Original Messag
Richard,
Thanks for the pointer, I'll do the reading and get back to you if
I need any clarification.
Appreciate your help.
Regards,
Shamik
On Fri, Jun 10, 2011 at 11:02 AM, Richard S. Hall wrote:
> Maybe this will have some advice:
>
> http://www.manning.com/hall/OSGIiAsamplech6.pdf
>
if that helps!
- Original Message -
From: "Shamik Bandopadhyay"
To: users@felix.apache.org
Sent: Friday, June 10, 2011 1:56:54 PM
Subject: Felix maven-bundle-plugin transitive dependency issue
Hi,
I'm new to OSGI and trying to deploy my first application. I've a
Maybe this will have some advice:
http://www.manning.com/hall/OSGIiAsamplech6.pdf
-> richard
On 6/10/11 13:56, Shamik Bandopadhyay wrote:
Hi,
I'm new to OSGI and trying to deploy my first application. I've a
spring dependency in my pom. While deploying I realized that Felix
runtime requir
Hi,
I'm new to OSGI and trying to deploy my first application. I've a
spring dependency in my pom. While deploying I realized that Felix
runtime requires all transitive dependencies to install the bundle
properly. Since then, I'm sort of struggling to resolve this issue.
I've tried embedded-depend
24 matches
Mail list logo
