[Rxtx] wrapping rxtx in eclipse

[andrea antonello]

Hi Karl,
I think your suggestions are good.

The problem is that I am also no Osgi specialist.

I can ensure a continuity in maintainment and bugfixes only by
proposing something I would do anyways, which is keeping up the
plugins and fragments for my project.
For something something different I am afraid that after few time it
would get of low priority in my list of job tasks and I prefer to not
take that path.

Andrea




On Wed, Jun 30, 2010 at 11:17 AM, Karl Weber <karl.weber99 at gmx.net> wrote:
> Am Dienstag, 29. Juni 2010 22:39 schrieb andrea antonello:
>> Hi developers,
>> I am currently using rxtx in an eclipse based GIS project to connect
>> to GPS via bluetooth.
>> I found the
>> http://rxtx.qbang.org/wiki/index.php/Wrapping_RXTX_in_an_Eclipse_Plugin
>> page a great start to maintain platform "independency".
>>
>> We are currently working on eclipse 3.6 and created the rxtx plugins
>> as they suggest to do them now using plugins and fragments.
>> Currently the namespace of the plugin is ours with authors rxtx.org. I
>> was thinking it probably would make more sense to create them with the
>> rxtx namespace and make them downloadable here?
>> So finally the question:
>> - is it ok if I update the above wiki page with eclipse 3.6 instructions?
>> - would there be interst for me maintaining the eclipse plugins for rxtx?
>> - is it ok to add my project to the projects using rxtx?
>>
>
> I am no OSGi expert, but if you think about maintaining an eclipse-plugin for
> rxtx, I would suggest a better solution, which should work, as far as I
> understand OSGi:
>
> (1) Create an OSGi-bundle. What I mean here is, that one should not use any
> eclipse / equinox specific stuff, so that this bundle can be used with other
> OSGi-frameworks as well.
>
> (2) Do not create a wrapper. If only java-classes where involved, the
> difference between an OSGi-Bundle and an ordinary jar-file was only some
> entries in the MANIFEST-header. So, instead of heaving a jar within a jar, I
> would prefer to have only one jar that is an OSGi-Bundle. Such OSGi-Bundle
> can also be used outside of any OSGi-framework, as ordinary jar-file.
>
> That rxtx involves c-libraries should not make much difference. In addition to
> the java-classes the (single) jar should also contain the libs.
>
> It would also be nice, to enhance the rxtx build-service, such that it can
> create such OSGi-bundles from the sources.
>
> /Karl
>
>
> P.S. I am currently also using a wrapper plug-in, but I am not happy with this
> solution...
> _______________________________________________
> Rxtx mailing list
> Rxtx at qbang.org
> http://mailman.qbang.org/mailman/listinfo/rxtx
>