Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[jdt-dev] JDT Java 9 release issues

Hey everybody,

 

First of all, congratulations for your great Java 9 release! I’ve been working with the beta for a couple of weeks now, and it’s been working really well.

 

However, I’ve noticed a couple of problems with the update site and the Marketplace entry for yesterday’s JDT Java 9 release:

 

Update Site

 

There seems to be an issue with the transparent mirror selection on eclipse.org . No matter if I try via Marketplace, or directly via update site (i.e. “Install new software…” dialog), the installation always aborts with errors like this:

 

An error occurred while collecting items to be installed

session context was:(profile="" phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action="">

Artifact not found: http://download.eclipse.org/eclipse/updates/4.7-U-builds/U20170921-1315/plugins/org.eclipse.jdt.core_3.13.50.v20170921-1218.jar.

http://download.eclipse.org/eclipse/updates/4.7-U-builds/U20170921-1315/plugins/org.eclipse.jdt.core_3.13.50.v20170921-1218.jar

Multiple problems occurred while downloading.

Artifact not found: http://download.eclipse.org/eclipse/updates/4.7-U-builds/U20170921-1315/plugins/org.eclipse.jdt.debug_3.11.50.v20170920-1717.jar.pack.gz.

http://download.eclipse.org/eclipse/updates/4.7-U-builds/U20170921-1315/plugins/org.eclipse.jdt.debug_3.11.50.v20170920-1717.jar.pack.gz

Artifact not found: http://download.eclipse.org/eclipse/updates/4.7-U-builds/U20170921-1315/plugins/org.eclipse.jdt.debug_3.11.50.v20170920-1717.jar.

http://download.eclipse.org/eclipse/updates/4.7-U-builds/U20170921-1315/plugins/org.eclipse.jdt.debug_3.11.50.v20170920-1717.jar

Artifact not found: http://download.eclipse.org/eclipse/updates/4.7-U-builds/U20170921-1315/plugins/org.eclipse.jdt.debug.ui_3.8.50.v20170920-1717.jar.

http://download.eclipse.org/eclipse/updates/4.7-U-builds/U20170921-1315/plugins/org.eclipse.jdt.debug.ui_3.8.50.v20170920-1717.jar

Multiple problems occurred while downloading.

Artifact not found: http://download.eclipse.org/eclipse/updates/4.7-U-builds/U20170921-1315/plugins/org.eclipse.jdt.ui_3.13.1.v20170921-0243.jar.pack.gz.

http://download.eclipse.org/eclipse/updates/4.7-U-builds/U20170921-1315/plugins/org.eclipse.jdt.ui_3.13.1.v20170921-0243.jar.pack.gz

Artifact not found: http://download.eclipse.org/eclipse/updates/4.7-U-builds/U20170921-1315/plugins/org.eclipse.jdt.ui_3.13.1.v20170921-0243.jar.

http://download.eclipse.org/eclipse/updates/4.7-U-builds/U20170921-1315/plugins/org.eclipse.jdt.ui_3.13.1.v20170921-0243.jar

 

I got it with all installations I tried, and I also asked around in my office, and everyone was getting the same.

 

Pasting any of the URLs in a browser, it redirects me to a mirror (in my case http://ftp-stud.fht-esslingen.de/pub/Mirrors/eclipse), which doesn’t have the artifacts in question. @Webmaster: I thought that the transparent mirror selection was not supposed to happen for P2 update site contents?

 

Marketplace Entry

 

Your Marketplace entry at https://marketplace.eclipse.org/content/java-9-support-oxygen is structured in a way that is probably not very helpful to a lot of users, and also unfortunately triggers a bug in the Marketplace Client. You currently list the following IUs on your entry:

 

[required/selected]   -  IU

  1. [t/t]    org.eclipse.jdt
  2. [t/t]    org.eclipse.pde
  3. [t/t]    org.eclipse.jdt.source
  4. [t/t]    org.eclipse.pde.source
  5. [f/f]    org.eclipse.sdk
  6. [f/f]    org.eclipse.sdk.ide
  7. [f/f]    org.eclipse.cvs

 

This causes a couple of issues:

  1. Having to install PDE as well as the two source features (2, 3, 4) is probably not what all users want or need
  2. The way MPC determines if an entry is already installed (all required features have to be present), your entry will not show up as an update in any of the EPP packages, but as a new install (because the source features and/or PDE won’t be present). Conversely, it will show up as an update in the SDK, since all required items are present.
  3. Unfortunately, b) surfaces an issue in MPC, because for the INSTALL operation, it will filter out org.eclipse.jdt as already installed without checking that it has updates available. This will be fixed in the next MPC release.
  4. As a side note, MPC only supports feature IUs, but org.eclipse.sdk.ide refers to a product IU, so it will never be resolved or used. This doesn’t cause any real issues though.

 

I would suggest to change your entry as follows:

 

[required/selected]   -  IU

  1. [t/t]    org.eclipse.jdt
  2. [f/?]    org.eclipse.pde
  3. [f/?]    org.eclipse.jdt.source
  4. [f/?]    org.eclipse.pde.source
  5. [f/f]    org.eclipse.sdk
  6. [f/f]    org.eclipse.cvs

 

I.e. make everything optional except for the JDT entry, and remove org.eclipse.sdk.ide. Whether you want the three previously required items selected by default is a matter of taste I guess, but I would lean towards deselected to minimize the surprise for your users.

 

Having just the JDT required will make the entry show up as an update in all EPP packages and in the Eclipse SDK, and the update operation will automatically select all IU entries for update that are already installed.

 

The only remaining issue is with the Eclipse SDK product (org.eclipse.sdk.ide). It makes no real difference if you list it or not – it will be ignored, since it isn’t found as a feature. Installation will still work even for Eclipse SDK users, because remediation will kick in and include the product IU in the update.

 

HTH,

 

Carsten Reckord

Lead Software Architect & co-founder

 

--

+49 (0)69 2475666-33 | reckord@xxxxxxxx | www.yatta.de


Yatta Solutions GmbH · Mainzer Landstraße 50 · 60325 Frankfurt a.M. (Germany)
Registered Seat: AG Kassel, HRB 14720 · VAT-ID DE263191529 · Managing Director Johannes Jacop

 

Back to the top