Re: managing OSGi Dependencies

2014-10-27 Thread PedroD
Pedro >>> >>> On 24/10/2014 23:46, Neil Bartlett wrote: >>>> Sure, here you go: https://github.com/njbartlett/jscience.example >>>> >>>> The only change to your code was to move it out of the default package. >>>> >>>>

Re: managing OSGi Dependencies

2014-10-27 Thread PedroD
gt;> The only change to your code was to move it out of the default package. >>> >>> Regards, >>> Neil >>> >>> >>> From: Pedro Domingues >>> <mailto:pedro.doming...@ist.utl.pt> >>> Reply: Pedro Domingues > &g

Re: managing OSGi Dependencies

2014-10-26 Thread Neil Bartlett
lt;mailto:pedro.doming...@ist.utl.pt> > > Date: 24 October 2014 at 23:14:48 > > To: users@felix.apache.org > > > <mailto:users@felix.apache.org>, Neil Bartlett > > > <mailto:njbartl...@gmail.com> > > Subject: Re: managing OSGi Dependencies > &g

Re: managing OSGi Dependencies

2014-10-26 Thread Pedro Domingues
014 at 23:14:48 To: users@felix.apache.org > <mailto:users@felix.apache.org>, Neil Bartlett > <mailto:njbartl...@gmail.com> Subject: Re: managing OSGi Dependencies Could you share your example project so that I could get a closer look? Thanks! On October 24, 2014 5:25:36 PM WE

Re: managing OSGi Dependencies

2014-10-25 Thread Christian Schneider
You are fully right. In fact you can even distinguish runtime and compile time libraries in maven. In reality though often all libraries are simply marked as compile (which is compile + runtime). Additionally people regularly forget to clean up the dependencies and remove unused ones. So as yo

RE: managing OSGi Dependencies

2014-10-24 Thread Neil Bartlett
Inline responses… From: Paulo Renato de Athaydes Reply: users@felix.apache.org > Date: 25 October 2014 at 00:37:50 To: users@felix.apache.org > Subject:  RE: managing OSGi Dependencies > Or perhaps they were necessary to satisfy the javac compiler but they  were not necessar

RE: managing OSGi Dependencies

2014-10-24 Thread Paulo Renato de Athaydes
hat this kind of error could be caught at compiling time. It's a huge mistake to wait for runtime to see what happens. Regards, Renato > Date: Fri, 24 Oct 2014 23:53:44 +0100 > From: njbartl...@gmail.com > To: users@felix.apache.org; renatoathay...@hotmail.com > Subje

RE: managing OSGi Dependencies

2014-10-24 Thread Neil Bartlett
ers@felix.apache.org > Subject:  RE: managing OSGi Dependencies You're playing with fire. Not providing all the dependencies at runtime that a library requires at compiling time is recipe for ClassDefNotFoundException which has plagued OSGi devs since the beginning of time. &g

Re: managing OSGi Dependencies

2014-10-24 Thread Neil Bartlett
ject:  Re: managing OSGi Dependencies Could you share your example project so that I could get a closer look? Thanks! On October 24, 2014 5:25:36 PM WEST, Neil Bartlett wrote: Further to this… I just created a Bndtools project to build a bundle containing your sample “SuchInterface” interface,

RE: managing OSGi Dependencies

2014-10-24 Thread Paulo Renato de Athaydes
You're playing with fire. Not providing all the dependencies at runtime that a library requires at compiling time is recipe for ClassDefNotFoundException which has plagued OSGi devs since the beginning of time. > Subject: Re: managing OSGi Dependencies > From: pedro.doming...@ist.ut

Re: managing OSGi Dependencies

2014-10-24 Thread Pedro Domingues
ett >Reply: Neil Bartlett > >Date: 24 October 2014 at 17:04:41 >To: users@felix.apache.org >, PedroD >> >Subject:  Re: managing OSGi Dependencies > >The Conditional-Package instruction is documented >here: http://bnd.bndtools.org/chapters/800-headers.

Re: managing OSGi Dependencies

2014-10-24 Thread Neil Bartlett
are they are MUCH more extensive than the runtime dependencies. Regards, Neil From: Neil Bartlett Reply: Neil Bartlett > Date: 24 October 2014 at 17:04:41 To: users@felix.apache.org >, PedroD > Subject:  Re: managing OSGi Dependencies The Conditional-Package instruction is docume

Re: managing OSGi Dependencies

2014-10-24 Thread Neil Bartlett
an OSGi bundle already:  http://jpm4j.org/#!/p/sha/57C2432E54DC40F871F55295C676B22672713602//0.0.0 Regards Neil From: PedroD Reply: users@felix.apache.org > Date: 24 October 2014 at 16:36:43 To: users@felix.apache.org > Subject:  Re: managing OSGi Dependencies Thanks On 24 Oct 2014,

Re: managing OSGi Dependencies

2014-10-24 Thread Neil Bartlett
. I hope that helps. Regards, Neil  From: PedroD Reply: users@felix.apache.org > Date: 24 October 2014 at 15:03:41 To: users@felix.apache.org > Subject:  managing OSGi Dependencies Greetings, I’m using Felix Framework for my OSGi project, but I’ve came across a severe problem conc

Re: managing OSGi Dependencies

2014-10-24 Thread Christian Schneider
I think this is an effect of the problem that people writing libraries depend too much on other libraries. One thing you should consider is if you really want to build upon a library that needs so many further dependencies. In some case you can not avoid it but you should limit these cases to

managing OSGi Dependencies

2014-10-24 Thread PedroD
Greetings, I’m using Felix Framework for my OSGi project, but I’ve came across a severe problem concerning third party dependencies. I’m using eclipse and maven-bundle-plugin to generate my bundles from the sources and the MANIFEST.MF from the POM.XML file. So far so good. however when I have