[Rxtx] RXTX rebundled (fwd)

[Andre-John Mas]

I avoid Maven, simply because it is too much infrastructure for my needs. I have started using Ivy though, mainly because I was trying to deal with dependency hell that Hibernate created.

BTW I do notice that Rxtx is on Ivy Roundup:

http://ivyroundup.googlecode.com/svn/trunk/repo/modules.xml

As an aside, I think it would be nice to see some of the improvements in some of the forks brought back into the main project. Maybe using git (via github or Google Code) could be an option, since it is designed to facilitate non-authorised forks, that can then be brought back in the main project.

I have been using NRJavaSerial for the recent builds of my projects.

On 2012-04-19, at 10:22 , Dyer, Tristan wrote:

> Personally I appreciate not being forced to use Maven. 
> 
> Adding support for it is probably a good thing as long as removing the ability to download a zip/tar is preserved.
> 
> Just my thoughts.
> 
> 
> Thanks,
> --
> Tristan Dyer
> 
> -----Original Message-----
> From: rxtx-bounces at qbang.org [mailto:rxtx-bounces at qbang.org] On Behalf Of Gregg Wonderly
> Sent: Thursday, April 19, 2012 11:13 AM
> To: rxtx at qbang.org
> Subject: Re: [Rxtx] RXTX rebundled (fwd)
> 
> Automatic loading of the native libraries is a big win for portability of applications between OSes.  That certainly should be in place.  Support for Maven is a separate issue, but one which I think makes sense in this day and age.
> 
> Gregg Wonderly
> 
> On Apr 19, 2012, at 6:13 AM, Trent Jarvi wrote:
> 
>> 
>> Would there be interest in seeing these change in RXTX?
>> 
>> ---------- Forwarded message ----------
>> Date: Thu, 19 Apr 2012 11:21:00 +0200
>> From: Alexander Christian <alex at root1.de>
>> To: tjarvi at qbang.org
>> Subject: RXTX rebundled
>> 
>> Hi Trent,
>> 
>> Thanks for the greate rxtx Java Library. I already used it several times in different projects.
>> 
>> But now I wanted to use it in a Maven3 project. I searched the Maven Central Repo and found it. Great. BUT: The artifact does not contain the native libraries and there was no suggestion on how to handle this issue "the maven way". I also found the setup-explanation in the wiki a bit away from "state of the art" (changing the JRE installation isn't practivle for stand-alone desktop applications etc...). So I rebundled your rxtx library and extened it a little bit:
>> 
>> 1) The artifact consists of one single JAR containing all required files, including the native libs
>> 2) I added a kind of "automatic library loader", which replaces the "System.loadLibraray()" calls in rxtx source code. This loader detects the OS + ARCH and extracts the correct native lib from JAR to the temp folder of the OS. Finally the extracted native lib is loaded from temp folder. If JVM terminates, the temp native lib files are removed.
>> 3) The rest of rxtx source is unchanged.
>> 
>> So, one can now use maven to get RXTX library + no worry about "how to load the lative lib" and "where to get the native libs when using maven" ...
>> Of course there's one "downside" of this improvement: The rxtx JAR is a bit bigger due to the fact that it contains all native libs for all OS + ARCH. But today size (currently 554k) often doesn't matter.
>> 
>> Maybe you're interested in these changes?!
>> 
>> You can find the source here:
>> 
>> http://svn.root1.de/svn/rxtx-rebundled/tags/2.1-7r2/
>> 
>> 
>> 
>> best regards,
>> Alex
>> 
>> _______________________________________________
>> Rxtx mailing list
>> Rxtx at qbang.org
>> http://mailman.qbang.org/mailman/listinfo/rxtx
> 
> _______________________________________________
> Rxtx mailing list
> Rxtx at qbang.org
> http://mailman.qbang.org/mailman/listinfo/rxtx
> _______________________________________________
> Rxtx mailing list
> Rxtx at qbang.org
> http://mailman.qbang.org/mailman/listinfo/rxtx
>