Mark Wielaard ([EMAIL PROTECTED]) wrote:
> I already asked on the jakarta general mailing list about this since
> Paul Siegmann and I maintain the javax.servlet.* classes.
> (Those classes are not yet part of Classpath since it took us so long to
> send the paperwork to the FSF. And I am a bit afraid that they never
> arrived since I haven't heard anything about it.)
You should ping Paul Fisher. All paperwork and account creation should
be up to date. However, see below.
> Brain Behlendorf (One of the core Apache developers) and James Duncan
> Davidson (Sun Servlet API developer) said that they hope that this will
> benefit as much projects as possible and they believed that the Apache
> license was (mostly) compatible with the (L)GPL. I am not really sure
> about this, so I have asked Paul Fisher if he could look at this.
> Since this could affect/benefit a lot of Servlet related projects which
> use GPLed code such as GNU Paperclips, GNUJSP, GSP, WebMacro, etc.
> Hopefully it is also compatible with the MPL since a lot of XML stuff
> is released under the MPL and JSP 1.0 uses XML.
Apache is under the BSD license. It is compatible with the LGPL.
Unfortunately, the Apache folks have included the obnoxious BSD
advertising clause. IMO, this is an annoyance, but is not a major
obstacle to using their code. Hopefully Sun will not included the
advertising clause, but I suspect they probably will.
> I did volunteer to merge our code since it would be nice to have one
> single free servlet library, but Sun will not release their implementation
> of the javax.servlet.* classes under the Apache License only the reference
> release of the Servlet and JSP engines. So we will currently keep
> maintaining the Classpath version to make sure that there is a free
> implementation of those classes. (Which should work equally well with
> the Jakarta project.)
It might make more sense for your javax.servlet implementation to live
with the Jakarta project rather than Classpath. It appears that it
would fit nicely there. What do they think of using your code as the
javax.servlet implementation?
--
Aaron M. Renn ([EMAIL PROTECTED]) http://www.urbanophile.com/arenn/
