On Sun, 27 Jan 2008 20:24:07 +0900 "Trustin Lee" <[EMAIL PROTECTED]> wrote:
> On Jan 26, 2008 5:09 PM, Emmanuel Lecharny <[EMAIL PROTECTED]> > wrote: > > Trustin Lee wrote: > > > I forgot to mention that we need to move transport-serial to > > > sandbox temporarilly due to the LGPL issue. I guess we need to > > > wait for the result of the board meeting which is going to be > > > held on Feb 20. > > > > > Yes, very true ! I thought about it yesturday too, but I also > > forgot to mention it... Hopefully, the [EMAIL PROTECTED] will define a > > clear position soon :) (This license stuff is by no mean easy...) > > > > But we may deliver a milestone without the serial subproject, can > > we ? > > Sure. That's what I meant. :) > > Trustin Hi, sorry for the lack of support on this issues I was on winter holidays. Those LGPL issues start to give me serious headache. I'll propose something I wanted to avoid, but it looks likes the bureaucratic issues have win. The serial connector can be modified to depend on a old Sun's comm.jar (2.X) in place of RXTX directly (you will anyway plug rxtx behind) which work on windows not like the 3.X release (who said Sun sucks ?:D). And the license terms are probably less irritating. You will still be able (anyway I seriously encourage you :D) to use rxtx2.0 (not 2.1) as the comm API implementation. By placing a "javax.comm.properties" files in your JDK lib directory containing the line : "Driver=gnu.io.RXTXCommDriver". What will lose : - RXTX 2.0 in place of RXTX 2.1 - depending on comm.jar, add another dependency - serial comm user will need to download an old version of Sun Communication API, and modify their JRE Lib directory for change the implementation (Sun comm API V2 doesn't work on Linux). What we win : - no more LGPL dependency - directly integrated serial communication in the MINA default build Julien
