Hi,
just my 2 pence on the licensing issue (which my company has also been
thinking
a lot about). Maybe it�s just our perception and you should correct me if
I�m wrong:
>> >Then how can jBoss (which is GPL) use the Tomcat server which is
> APL?
APL is non-infective and open, so you can put a GPL wrapper/interface around
without any problem, right? The other way round, it�s impossible. So
shipping tomcat with jboss is just the same as shipping tomcat with your
commercial product .... Developing GPL source around APL is as legal as
developing commercial source around it. Point.
>jBoss is doing a lot of things illegally. At least one of the developers
>recognizes this and has pushed to have licensing modified. Laundry list
>include all JMX, JMS, apache stuff (ie cocoon/tomcat etc) + any other
>non-GPL compatable library.
Ok, my impression is that it�s indeed not fully legal to ship
ejb.jar, jmxri.jar, tools.jar etc. with the jBoss source dist or binary dist
(that�s what gives the project this thrilling "underdog" look and makes so
much fun ;-).
But nothing hinders you to obtain them from SUN directly for development
purposes. Nothing hinders you to get a redestribution license for that stuff
(similar the commercial mapping products that interfaces are built for, ect)
if you want to ship your final product.
Again, what is the problem of developing/compiling/shipping GPL source code
against any commercial/APL/other-licensed stuff .... unless the stuff has an
infective licensing character that EXPLICITELY excludes GPL and other sorts
of open source?
Best,
CGJ
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
