I kinda like GPL/LGPL I have to say. The issue with use of internal Tomcat
classes is one that can be resolved by judicious use of re-factoring and
perhaps the creation of a separate "jBoss-Tomcat Integration Adaptor"
project that can [optionally] use a more "liberal" license. I am aware that
this may have to be done for every integration project where there is a
difference of licenses. So be it. We could just lump all integration
adaptors into the same overall project to save admin overhead.
I see no reason to change the license just for the issue of integration. It
will seem to me that the GPL/LGPL .vs. Other licenses discussion depends on
which side of the fence you are sitting on.
I am sitted firmly on the
improvements-MUST-be-contributed-back-to-the-community" fence post.
Cheers!,
Micheal
| -----Original Message-----
| From: [EMAIL PROTECTED]
| [mailto:[EMAIL PROTECTED]]On Behalf Of Aaron Mulder
| Sent: 02 November 2000 19:54
| To: jBoss Developer
| Subject: [jBoss-Dev] Tomcat & Licensing
|
|
| So I see we're adding still more jBoss code that directly
| references Tomcat classes. We wrote some interceptors, we call Tomcat to
| configure them, etc.
| The whole licensing thread seem to have died under it's own weight
| - which is OK, the heat was rising a little too fast for comfort. But I
| think it's more important than ever that something is done about the
| current jBoss license. We're quickly passing the point where we could
| "factor out" all the Tomcat specifics and claim to be using some generic
| interface. I think it's very clear that we're tightly integrated with
| Tomcat (I see around 20 instances of "org.apache.tomcat"), and IMHO we
| cannot claim to be "merely aggregating".
|
| Aaron
|
|
|
