Meanwhile, back at the ranch

Now that there is a plan proposed for JDK 7 (and JDK 8) it's worth a reminder that there are binary snapshots of JDK 7 available for those that want to try out the new features, or just see that existing code and applications still build and run well. The more developers using these builds then the better chance of catching issues. This goes for both the new features, the dozens of other improvements, and the 5000+ bug fixes that this release has snacked on so far. Even in areas with good tests there is always the risk of breaking something. So, if you find something that stops working with JDK 7 then try to narrow it down and submit a bug. Alternatively, if you have a fix, then get a contributor hat and bring the patch to OpenJDK.
Comments:

Hi Alan,

Since you point to the OpenJDK 7 feature list I assume these JDK 7 snapshots are derived from the OpenJDK sources. Could you post them under a more friendly license, preferably just GPL like the rest of us are using?

I tried to use them to compare to my own builds, but apparently the license doesn't allow me to :{ Error: License was not accepted.

This was the same issue pointed out some time ago:
https://gnu.wildebeest.org/blog/mjw/2009/11/14/trusting-companies-with-your-code/

Then Mark Reinhold actually published his builds under the GPL:
https://gnu.wildebeest.org/blog/mjw/2009/11/19/gpled-jdk-7-m5-jigsaw-binary-packages/

Could you please do the same?

Thanks,

Mark

Posted by Mark Wielaard on November 04, 2010 at 03:06 AM PDT #

I guess you know this already, but Oracle's binaries get built with some proprietary components such as the plug-in, web start, installers. Creating binaries from the OpenJDK repos would be nice but I personally don't have cycles to do that. In any case, this entry wasn't meant to highlight that hoary issue. Rather it's to coax developers into trying JDK 7 and sending feedback so that bugs/issues are caught as early as possible. JDK 7 might not be a large release (relatively speaking), but there are still several truck load of changes.

Posted by Alan Bateman on November 04, 2010 at 09:21 PM PDT #

Sure, you still have some proprietary blobs. But you can just use the GPL+exception for all the OpenJDK code. Only your proprietary add ons need to be covered by a closed license (thanks to the assembly exception). That way people would actually get the freedom to inspect the OpenJDK parts themselves and see what is different from the community builds. The current draconian proprietary license you are using basically forbids community members to inspect the free shared code. Using a license that forbids sending feedback to the OpenJDK communtiy really is not nice and unfair to all who contributed to the code.

Posted by Mark Wielaard on November 04, 2010 at 09:54 PM PDT #

Here is the relevant bug report, opened more than 6 (SIX!) years ago:

http://bugs.sun.com/view_bug.do?bug_id=6186134

:(

Posted by Dusty on November 09, 2010 at 10:16 PM PST #

My previous post has been lost, I was saying that a very basic bug on the JVM has been reported 6 years ago, the cause was found, but it's still unfixed..

Alan, can you, working at Oracle, raise the attention on it?

Thanks!

Posted by Dusty on November 10, 2010 at 09:32 PM PST #

Post a Comment:
Comments are closed for this entry.
About

user12820862

Search

Top Tags
Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today
News
Blogroll

No bookmarks in folder