Comment Re:Speaking of sources.. (Score 1) 131
What other people have tried to tell you is true.
To sell java-based applications you pay no royalties to Sun. To download the JDK you pay no royalties to Sun. To look at the source code of the JDK you pay no royalties to sun.
If you modify the source code of the JDK and sell it, you pay royalties to Sun.
The "full source release to Sun's JavaTM Development Kit software" is not required to ship a Java application. It is only of interest if you are interested in the internals of the Java language -- perhaps if you were writing your own VM, or JDK or debugging tools. If your reasons
are for "educational, evaluation or research" purposes, you are (apparently) free to look at the code. If however you are "borrowing" the code or the code concepts for commercial purposes, you'll need to negotiate with Sun.
Strictly speaking, you don't even need Sun's source code to write your own VM, JDK or debugging tools. They have specifications for the VM and the core libraries which are publicly available.
To sell java-based applications you pay no royalties to Sun. To download the JDK you pay no royalties to Sun. To look at the source code of the JDK you pay no royalties to sun.
If you modify the source code of the JDK and sell it, you pay royalties to Sun.
The "full source release to Sun's JavaTM Development Kit software" is not required to ship a Java application. It is only of interest if you are interested in the internals of the Java language -- perhaps if you were writing your own VM, or JDK or debugging tools. If your reasons
are for "educational, evaluation or research" purposes, you are (apparently) free to look at the code. If however you are "borrowing" the code or the code concepts for commercial purposes, you'll need to negotiate with Sun.
Strictly speaking, you don't even need Sun's source code to write your own VM, JDK or debugging tools. They have specifications for the VM and the core libraries which are publicly available.
