Community
Participate
Working Groups
The Galileo plan needs updating to reflect progress on plan items, and changes in reference platforms and execution environments.
Created attachment 123125 [details] Patch to plan
The draft plan in XML form is available at: http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_5_new.xml
(In reply to comment #0) > The Galileo plan needs updating to reflect progress on plan items, and changes > in reference platforms and execution environments. I question the motion of supporting Sun's 6u4 Java release because it is prone to crashing due to bug 214092. Please reconsider.
Boris gave me the answer to my other question on the mailing list. You can view a rendered plan by uncommenting line three of the plan xml file.
Yes, please reconsider. JDK6 releases between update 3 and 10 (both exclusive) were too unreliable when used with Eclipse as the number of duplicates on the referenced bug shows (as well as the number of votes on the bug in the Sun database).
Created attachment 123131 [details] Draft plan rendered as HTML Attached HTML rendering of the plan was done by following the instructions on http://wiki.eclipse.org/Development_Resources/Project_Plan Search that page for the text "If you prefer checking it locally before commiting" I think that at one point, Dave Carver also explained me how to use the Launch Configurations from his XSL Tools incubator project to perform the XML -> HTML rendering, but I forgot how that's actually done. What we'll eventually need is someone (Bjorn?) to fix bug 238434.
Re comment #3: I used Java 6 update 4 because that is the version we use on our test machines, and because we also use Java 6 update 4 on Windows. It is therefore our only tested configuration of Java 6. I'll await PMC input on whether we should change this to a newer update of Java 6 (and possibly also upgrade test machines).
John, is it just a typo or is there a reason that M6 is on a Thursday (03/12/2009) and not on a Friday?
Re comment #8: I believe that is a typo. I'll move it to the 13th.
In the interest of finally getting a first update out, I have released this plan update. We can update the Java 6 Linux version in the next plan update.
(In reply to comment #5) > Yes, please reconsider. JDK6 releases between update 3 and 10 (both exclusive) > were too unreliable when used with Eclipse as the number of duplicates on the > referenced bug shows We were considering moving the Reference Platform to Sun 6u11, but stumbled over a change in the THIRDPARTYLICENSESREADME.txt file that gets installed with the JRE: Namely, the following 3 sections have been added to the end of the file with 6u10: * May include 7-zip (licensed under LGPL + AES) * May include UPX (licensed under GPL) * May include LZMA SDK (multi-licensed under LGPL, CPL, Proprietary) I found this concerning because the document does not specify what portions of the JRE fall under those new licenses. In the extreme case, a vendor might pick up JRE 6u11 because it's an Eclipse Reference Platform, just to detect that he just became subject to the viral nature of the GPL. One assumption about the reason for these new licenses is that only the Java Kernel Installer might be affected by using UPX for packing the executable: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6612006 But this wouldn't explain why the Linux JRE's are also affected since they don't ship a Java Kernel Installer. What's more concerning is that the web-accessible variant of the THIRDPARTYLICENSESREADME does *not* contain the problematic new sections. I therefore filed a bug against Sun: http://java.sun.com/javase/6/javase-6-thirdpartyreadme.txt I googled but could not find any more information about the usage of these items in the JRE. Any insight from the Community would be helpful. At the same time, I filed another bug against Sun asking for clarification what items are affected. We'd like to defer updating the reference platform version in the project plan until these questions are clarified. See also bug 262907 which discusses enhancements to the process around reference platforms.
Update: The two bugs I have filed against Sun on 2-Feb are finally publicly visible on the Web (this took a whole month!): http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6800015 README must document what components of the JDK/JRE use (L)GPL http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6800013 Web-accessible THIRDPARTYLICENSEREADME.txt is out of date In the meantime, JDK 1.6.0_12 was released, and the problems are still in there -- in fact even an additional item was added to the THIRDPARTYLICENSEREADME.txt referring to parts of the JDK being under a Microsoft runtime license. Please vote for and watch the bugs to understand whether JRE 1.6.0_10+ can be used in your projects based on Eclipse.
Update: > http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6800015 > README must document what components of the JDK/JRE use (L)GPL This bug is now listed as "dispatched" but the problematic terms are still in the THIRDPARTYLICENSE.txt as of JRE 1.6.0_13 > http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6800013 > Web-accessible THIRDPARTYLICENSEREADME.txt is out of date This bug is now fixed, the current license (as of 1.6.0_13) is here: http://java.sun.com/javase/6/javase-6-thirdpartyreadme.txt I'd still be cautious using Java 6u10 or later in a product...
Update: As per JDK 1.6.0_17, bug http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6800015 is still in "dispatched" state an http://java.sun.com/javase/6/javase-6-thirdpartyreadme.txt still refers to "some parts" of the JDK being under (L)GPL -- UPX, 7z, LZMA SDK.
