Re: [Jikesrvm-researchers] Congratulations on Jikes-RVM 2.0 - questions about licensing.
Thanks for your interest and encouragement regarding Jikes RVM. The
team is happy to provide a system that others will find useful.
You are correct that the license for the libraries is more restrictive than
the license governing the core RVM. I agree this is not ideal. The reason
for this is addressed in the Q&A Overview (first link on left navigational
menu), question 12, including here for convenience.
12. Why are different licenses used for the Jikes RVM and the libraries?
The Jikes RVM is released under the CPL (Common Public License), which
has been approved
by the OSI (Open Source Initiative) as a fully certified open source
license. The Jikes RVM was
written as a test-bed for evaluating new virtual machine technologies.
Research in library issues was
not a major goal. However, a VM is not useful without a minimal set of
libraries. The libraries
available with the Jikes RVM were developed independently by developers
at Object Technology
International, an IBM company. Although the library license is not an
open source license, it does
facilitate open source development of the RVM. We encourage any users
who would like to
develop open source libraries that work with Jikes RVM.
> I would suggest that a sub-project be started to integrate
> the code from GNU Classpath which should be able to replace the JLibrary
As the last sentence says, we would also encourage such an activity.
- - - - - - - - - - - - - - - -
Manager, Dynamic Optimization Group, Jalapeño Project
IBM Watson Research Center
914 784-7589, tieline: 863-7589
email@example.com (Kevin A. Burton)@www-126.southbury.usf.ibm.com on
10/24/2001 10:15:45 PM
Please respond to firstname.lastname@example.org
Sent by: email@example.com
cc: Sam Ruby/Raleigh/IBM@IBMUS, debian-java
Subject: [Jikesrvm-researchers] Congratulations on Jikes-RVM 2.0 -
questions about licensing.
-----BEGIN PGP SIGNED MESSAGE-----
Sorry for the x-post but I think this is relevant to everyone included.
For starters I would like to congratulate IBM and the RVM team on your
RVM 2.0 release (and published white-papers). This is definitely a great
contribution to the Java and Open Source communities!
Unfortunately, I have issues with the current RVM licensing terms.
Specifically the licensing of the JLibrary package.
This is a very restrictive license and I don't understand why it was chosen
it seems to go against the Open Source nature of the RVM.
This prohibits innovative use of the RVM code. Specifically integration
GNU Classpath, distribution with Debian GNU/Linux, etc.
Is there anyone at IBM we can talk with about changing the terms of the
package to an Open Source license? If the problem is a reliance on
code (AKA SUNs code), I would suggest that a sub-project be started to
the code from GNU Classpath which should be able to replace the JLibrary
Again. Congrats. I am very excited about the RVM release as I think that
lack of a quality (stable) Open Source JVM is hurting both the Java and
Need a good Engineer? Hire me! ( Java | P2P | XML | Linux | Open
Kevin A. Burton ( firstname.lastname@example.org, email@example.com,
Location - San Francisco, CA, Cell - 415.595.9965
Jabber - firstname.lastname@example.org, Web - http://relativity.yi.org
The invariable mark of wisdom is to see the miraculous in the common.
- Ralph Waldo Emerson (1803-1882)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Get my public key at: http://relativity.yi.org/pgpkey.txt
-----END PGP SIGNATURE-----
Jikesrvm-researchers mailing list