使用“Eclipse IDE for Java EE Developers”软件包修复ClosedFileSystemException错误

Question

I am using Windows 10. I am using the final release Eclipse 2018-09 (4.9) with the "Eclipse IDE for Java EE Developers" package.

Unfortunately this version has a bug that produces a ClosedFileSystemException in some situations. This problem was filed as Eclipse Bug #539536 and marked as resolved. Unfortunately the discussion on that ticket isn't clear to me regarding how I am supposed to update my "Eclipse IDE for Java EE Developers" to include the bug fix.

(Perhaps the ticket is clear but my mind is a little slow. If so, please indulge me while I ask some very specific questions; I get confused easily with ambiguous answers. I'll mark the questions in italics so they will stand out.)

1. I went to the Eclipse 2018-12 M1 download page , but there was no "Eclipse IDE for Java EE Developers" package there. Is the "Eclipse IDE for Java EE Developers" package for Eclipse 2018-12 M1 available for download somewhere, and if so, where?
2. A comment on Bug #539536 indicated that I can add http://download.eclipse.org/eclipse/updates/4.10milestones/ as an update site and then use "Check for Updates" to fix this bug. Should I expect that this update site will update my "Eclipse IDE for Java EE Developers" to the full 2018-12 M1 release, after which my Eclipse will show "2018-12 (4.10) M1", or will it only update one or more "features"?
3. If http://download.eclipse.org/eclipse/updates/4.10milestones/ will not update my version of Eclipse to 4.10 M1, then why does the URL include "4.10milestones"?
4. By using "Check for Updates" after adding the http://download.eclipse.org/eclipse/updates/4.10milestones/ update site, I was able to update to "Eclipse Java Development Tools 3.16.0.…", "Eclipse Plug-in Development Environment 3.13.300.…", and "Tip of the Day UI Feature 0.2.200.…". Does installing one or more of these updates fix Bug #539536 (the ClosedFileSystemException bug)—does my "Eclipse IDE for Java EE Developers" now have the fix for Bug #539536?

Thank you very much in advance for your time and clarifications.

Answer 1

See the answers to the separate questions below:

1. I don't know why the Java EE package is missing in 2018-12 M1 (the 2018-12 M1 announcement on the epp-dev mailing list just says why the modeling package is missing; you might ask on this mailing list or in the EPP forum why also the 2018-12 M1 Java EE package is missing), but if you don't want to wait for 2018-12 M2, you can download a current build directly from Jenkins which might not be as stable as the milestone builds and which are intended for testing .
2. No , because this is the milestone 4.10 update site of the Eclipse Project (Platform, JDK and PDE), not of the simultaneous release. The Eclipse simultaneous release 2018-12 staging update site is http://download.eclipse.org/staging/2018-12/ . The Eclipse Packing Project (EPP) builds the Eclipse IDE for Java EE Developers from features from different Eclipse projects ( Eclipse , JGit , EGit , WTP , etc.).
3. 4.10 is the upcoming version of the Platform, JDK and PDE. In contrast, 2018-12 is the version of the upcoming simultaneous release (which will contain also eg JGit/EGit 5.2 and therefore uses the different version scheme).
4. If you mean Eclipse Java Development Tools 3. 16 .0.v20181010-1800 and not Eclipse Java Development Tools 3. 1.6 .0.… , yes . The last part of the version number tells you when it was built (here: 10 October 2018, at 6 pm). The changes regarding Eclipse bug 539536 should be included .

I would recommend updating only the JDT feature instead of the whole product/package. The aggregation of the different parts from different projects into one package might be buggy, especially with early milestone builds when new features are added and larger changes are made.

In addition, if you use the Eclipse (Platform/JDT) project milestone update site instead of the simultaneous release staging update site, you get the changes at least four days earlier because the Eclipse project has an offset of "+0", while other projects have an offset up to "+3" days and the aggregation of the packages by EPP takes place on "+4" .