It's not a mistake. I think we had enough discussion: http://markmail.org/message/zpjhpxlj3hul3phx#query:+page:1+mid:zpjhpxlj3hul3phx+state:results
Please let me know if we need to add some notice statements in our distribution. Long story short, Sun made some backward incompatible changes in their communications API, and the new version of the API didn't support Linux (or Windows?) at all at that time and the situation lasted for a long time. RXTX also has forked from Java communications API due to this reason. I didn't keep track of the recent support of Sun's communication API, let me know if you find something useful. AFAIK, adding sun's communication API into our direct dependency list, it bothers our users to download it from the official web site manually. In contrast, RXTX is available in the official Maven repository and very stable and mature in what it's supposed to do. What we need to do is to tell users that it is a LGPL'd library, and that's why LICENSE.rxtx.txt is there. Trustin On Jan 20, 2008 1:07 AM, Alex Karasulu <[EMAIL PROTECTED]> wrote: > I thought we used SUN Java comm interfaces for serial communication and that > the native libraries or Java API for RXTX are not redistributed or used by > the MINA we distribute. Why then would we have it's LGPL license included > at our top level? > > https://svn.apache.org/repos/asf/mina/trunk/LICENSE.rxtx.txt > > Is this a mistake? > > Alex > > -- what we call human nature is actually human habit -- http://gleamynode.net/ -- PGP Key ID: 0x0255ECA6
