As already pointed out GPLing java will mean you are forced to use the same license for your project using java and hence avoiding to make any commercial use of java.
This is obliviously not feasible, as the only license, so SUN will use dual license (mysql way) one free and one commercial targeted at two different needs finally making money out of java...
And what if I contribute back to the GPLed codebase ? Will my gpl source be released under a license I may not want to agree?
Also in this scenario the viral effect of GPL will make all the opensource software released under other license (i.e. BSD/Apache) to move to GPL that's not feasible either.
So SUN will need a third license or another custom license?
For small software I think LGPL is the best way to force contribute back but if the poll were still open I would have voted for Apache/BSD the most "liberal", since the people fixing and enhancing the codebase have all the interest to contribute back and make the changes available to all.
I'm not an license expert, these are just thought from a java developer, I probably got it wrong and I wish more developer comment on my statements and this important poll in general. Unfortunatly the poll is closed...
my 0 cents |
java.net RSS Feeds
