Note: This feature patch is disabled. It was originally intended to be installed on top of 4.7.1 builds.
Java™ 9 support for Eclipse JDT is available now with Oxygen.1a (4.7.1a) and newer releases.
The new and noteworthy entries can be accessed here: https://www.eclipse.org/eclipse/news/4.7.1a/#java-9.
Unsuccessful Installs in the last 7 Days: 0
Submitted by Paul Verest on Thu, 2018-01-25 03:09
Just update Eclipse JDT to the latest (or download Eclipse Oxygen.2),
there is no need to install this solution
(that was only for Oxygen.1 while it was the latest released)
Submitted by Vignesh M on Fri, 2018-01-05 10:05
The update URL seems to be invalid. The Java9 module support hence not accessible in Eclipse.
Submitted by Stephan Herrmann on Mon, 2018-01-15 12:31
Repeating my own comment from below:
If you carefully read the description and also recent comments, you'll find that this entry is no longer in use (and why so).
Submitted by Jean-Jacques Kujawa on Wed, 2018-01-03 08:31
I just reinstalled eclipse from scratch and Eclipse Platform. (Oxygen)
When I try to install this package from marketplace it says:
No repository found at http://download.eclipse.org/eclipse/updates/none.
I see that there is also a version of Java in the package name. Does this mean that i won't be able to code with prior versions of Java?
Now using the legacy "install new software..." method works.
Submitted by Stephan Herrmann on Wed, 2018-01-03 09:37
On the other question: Eclipse will continue supporting older versions of Java (this entry only served for adding support for Java 9 while this was not available in any released version).
Submitted by Hisayuki Ookubo on Wed, 2017-12-13 20:21
then,got a error
The method get(URI) in the type Paths is not applicable for the arguments (String)
Submitted by Stephan Herrmann on Thu, 2017-12-14 09:36
This works fine for me.
If you have sufficient information on how to reproduce, please file a bug at https://bugs.eclipse.org/bugs/enter_bug.cgi?product=JDT
Also note, that this market place entry is no longer in use, as support for Java 9 is available in the official Oxygen.1a release.
Submitted by Ireneusz Kordal on Sat, 2017-11-11 15:51
Cannot be installed on a fresh Eclipse installation.
I get this error:
No repository found at http://download.eclipse.org/eclipse/updates/none.
Submitted by Dani Megert on Tue, 2017-11-14 03:43
Java 9 is now part of Oxygen 1a and also Photon M3. The Marketplace install is no longer needed and has been retired.
Submitted by Lorenzo Mengoni on Sat, 2017-10-28 04:31
I get this error when I try to install from market place:
Sat Oct 28 10:27:29 CEST 2017
May be the url is wrong?
Submitted by Dani Megert on Mon, 2017-10-30 09:07
Submitted by Stephan Herrmann on Fri, 2017-10-13 17:42
Attention: if you previously installed the BETA version of Java 9 Support, you should either start with a fresh new installation, or at least uninstall the BETA Patch / ensure that the following feature is no longer installed:
Failure to do so may cause the older path feature to override newer installed plugins.
Submitted by Cahao Vien on Thu, 2017-09-28 21:51
After I installed Eclipse Oxygen.1 Release 4.7 and JDK 9+181 on Linux Mint Cinnamon (Ubuntu) Sonya,
see bug reports regarding --add-modules=ALL-SYSTEM for this and cf: StackExchange regard ibid.
I opened Help -> Eclipse Marketplace ... ->
<typed in> Java 9 <enter> -> <selected> Install [button] ->
Confirmed | Finish | Update Installation -> Accepted License Agreement ->
***(IMPORTANT STEP:)*** <then waited for the full installation to finish::
progress bar is hidden on bottom right of workspace [hard to see]> ->
<Eclipse prompts for restart> Accept -> <should work automatically now>
To review: make sure you Install Java 9 Support for Oxygen 4.7 as many people have said, but I add make sure you *wait* for the full installation to complete before closing the window!
Submitted by Giovanni Lovato on Wed, 2017-09-27 10:47
Seems like today mirrors are not up-to-date with yesterday snapshost as install fails. Many JDT files at http://download.eclipse.org/eclipse/updates/4.7-U-builds/U20170927-0115/... return 404 (e.g. org.eclipse.jdt.core_3.13.50.v20170926-1643.jar).
Submitted by Dani Megert on Fri, 2017-09-29 05:15
There were issues in the mirroring code, see https://bugs.eclipse.org/517294. This should work now.
Submitted by Reggie K on Mon, 2017-09-25 01:43
What is the repo url for mirroring with tycho plugin or using the p2 mirrorApplication?
Submitted by Zhubin Salehi on Fri, 2017-09-22 10:34
I have the same issue mentioned earlier. It breaks maven regardless of which version of Maven or JDK I use.
Submitted by Sarika Sinha on Thu, 2017-09-28 08:18
It is fixed now. You can run Maven with Java8 now.
Submitted by Alexander Rühl on Fri, 2017-09-22 09:04
I tried the plugin a week ago when it was still named "beta" with the latest early access Java 9 build, but today after the release of Java 9 it does not work.
First of all it does not smoothly installs as before, complaining about existing Eclipse components, even though it was a freshly downloaded Eclipse and with following the steps above.
And then, it still states "Target is not a JDK root. System library was not found." when trying to add a JDK.
Submitted by Manoj Palat on Tue, 2017-09-26 02:21
Which Eclipes was used?
Submitted by Dipannita Basu on Tue, 2017-09-19 05:37
I am using eclipse Oxygen 4.7 and in the step of create source module, I am not getting checkbox to crate a module -info descriptor file.
Submitted by Manoj Palat on Wed, 2017-09-27 02:27
Can you please try out with the latest version and try? You can try using the project context menu -> configure -> create module-info to get a default module-info.java file for a starter. Please report a bug if you hit any issues.
Submitted by Mike Dudley on Sat, 2017-09-16 05:35
As soon as I installed Java 9 support I get this error running maven:
Error: Could not find or load main class org.codehaus.plexus.classworlds.launcher.Launcher
note: this error is always the same no matter I use different JDK to run maven.
Submitted by Richard Evans on Thu, 2017-09-07 05:14
Reading the introduction above, I think this is not possible, but want to check. Is is possible to add extra modules to the build path of a poject? Or limit the modules visible? Quick tests show that modiles in java.se.ee but not java.se are visible to projects by default. How do I restrict to just java.se modiules?
Submitted by Stephan Herrmann on Mon, 2017-09-25 17:47
Support for add/limit modules has recently been added, see https://www.eclipse.org/eclipse/news/4.7.1a/
Towards the end it describes how double-clicking "Is Modular" opens a dialog for modularity details, where tab "Contents" lets you select which modules are included (explicitly, or implicitly as dependencies of the former).
Note, that the linked document is work in progress, and also the implementation is still being finalized for the Oxygen.1a release scheduled for Oct. 11.
Submitted by FirstName LastName on Thu, 2017-06-29 09:09
i tried to install on neon2,neon3,oxygen m1 to m7,every time failure!but use
download dot eclipse dot org/eclipse/downloads/drops4/P20170519-0945/
to download and install by offline way,every time success! java ee and java se version~
we can also choose version as follows:
ftp dot acc dot umu dot se/mirror/eclipse.org/eclipse/updates/4.7-P-builds
https colon double slash ftp double gnome dot org/mirror/eclipse.org/eclipse/updates/4.7-P-builds
cdimage dot debian dot org/mirror/eclipse.org/eclipse/updates/4.7-P-builds
Submitted by Richard Evans on Sat, 2017-06-03 06:23
Will not install with Oxygen 4.7RC3. Install new software from update site (http://download.eclipse.org/eclipse/updates/4.7-P-builds) gives "There are no items available" and install from Marketplace client gives:
The following solutions are not available: Java 9 Support (BETA) for Oxygen 4.7
If you tjen attempt the install it fails with no error in the .log
Submitted by Richard Evans on Mon, 2017-06-05 13:22
Submitted by Richard Evans on Thu, 2017-01-12 15:05
I've added Java 9 support to Eclipse 4.7M4 and I'm trying it with some existing code. One class has an illegal import from a sun. package. This is not shown as an error in the editor, just a marker.
Submitted by Dani Megert on Tue, 2017-01-17 10:12
Please don't report bugs here. Instead file a bug report against JDT Core with steps to reproduce.
Submitted by Dani Megert on Mon, 2017-01-16 09:54
I'm not sure what you mean. Markers are used to show errors and warnings. Please file a bug report against JDT Core with an example.
Submitted by Richard Evans on Mon, 2017-01-16 14:21
The import is:
and the imported is used later on in the code. Neither location is flagged as an error.
Submitted by Dani Megert on Tue, 2017-01-17 10:13
Submitted by Chris Hennick on Fri, 2017-01-13 15:18
If your sun.* classes are in the following list, they can still be used -- just write a modupe-info.java in your source root and make sure your module declares "requires jdk.unsupported;" sun.misc.Unsafe, sun.misc.Signal, sun.misc.SignalHandler, and sun.reflect.ReflectionFactory.
Submitted by Chris Hennick on Wed, 2017-01-11 01:43
My project contains multiple modules, and I'm getting this error:
Description Resource Path Location Type
The project was not built due to "Build path contains duplicate entry: 'module-info.java' for project 'Sunset'". Fix the problem, then try refreshing this project and building it since it may be inconsistent Sunset Unknown Java Problem
How do I fix this?
Submitted by Jay Arthanareeswaran on Wed, 2017-01-11 10:38
Or join the discussion on https://bugs.eclipse.org/bugs/show_bug.cgi?id=479483
Submitted by Dani Megert on Wed, 2017-01-11 10:26
Currently one project corresponds to one module. You have to refactor it into multiple projects. If you disagree with that, please open a bug report against JDT Core.
Submitted by Chris Hennick on Wed, 2017-01-11 16:02
Thanks! Creating a new project for each module seems to have fixed that error message. (It'd be nice if there was a way to automatically create a project for every subfolder of a given folder, and make them all into a new working set.) But now, I'm getting this error once per project:
Description Resource Path Location Type
The project was not built since its build path is incomplete. Cannot find the class file for java.lang.Object. Fix the build path then try building this project sunset.classloader Unknown Java Problem
The error persists even after manually applying the org.eclipse.jdt.MODULE_PATH workaround, restarting Eclipse and cleaning all the projects. What's wrong now?
Submitted by Dani Megert on Mon, 2017-01-16 09:52
I can't tell from here what's wrong. Please file a bug report against JDT Core with an example project.
Submitted by Eric Kolotyluk on Fri, 2016-12-23 17:16
When launching Eclipse, after choosing the workspace I get
An error has occurred
See the log file /Users/eric/documents/workspace/.metadata/.log
I appended the following to the config.ini file
but I still get the same error
!ENTRY org.eclipse.osgi 4 0 2016-12-23 14:14:47.551
!MESSAGE Application error
org.eclipse.e4.core.di.InjectionException: java.lang.NoClassDefFoundError: javax/annotation/PostConstruct
Submitted by Dani Megert on Tue, 2017-01-03 11:38
-addmods was used by older Java 9 versions. These days you have to use --add-modules=java.se.ee as explained above.
Submitted by Eric Kolotyluk on Tue, 2017-01-24 15:10
I have added modules=java.se.ee as explained above, and the effect is still the same: An error has occurred, see the log file.
The only way I can get Oxygen to launch is to add this to the Shortcut Properties in Windows.
Submitted by Dani Megert on Wed, 2017-01-25 10:34
> I have added modules=java.se.ee as explained above
Nothing above says that this is what you need to do. You need to add --add-modules=java.se.ee (assuming you are using a recent Java 9 version).
Submitted by Manoj Palat on Wed, 2016-12-21 08:21
With the latest as of now: http://download.eclipse.org/eclipse/updates/4.7-P-builds/P20161221-0730/
Ref https://bugs.eclipse.org/bugs/show_bug.cgi?id=509354 for details.
Submitted by Eugene Rabii on Fri, 2016-12-16 06:04
I'm on Mac OS, Fresh Install of Neon + http://download.eclipse.org/eclipse/updates/4.6-P-builds/.
First as already noted by some bug, Eclipse neon.1 (4.6.1) does not start under JDK-9. So the only way to start it is via :
Now it starts.
Things I am looking at :
Eclipse -> About Eclipse -> Installation Details -> Eclipse JDT Patch with Java 9 is installed.
Eclipse -> Preferences -> Java Compiler -> No option for JDK-9.
Fresh install of Eclipse Oxygen. It starts with JDK-9 with default configuration.
Things I am looking at :
Eclipse -> Preferences -> Java -> Compiler -> 9 (BETA) is there. I select it.
Eclipse -> Preferences -> Java -> Installed JRE's -> Installed JRE Location no longer Exists. JRE will be removed.
Again, it does not work.
Can anyone provide any details on how this is supposed to be configured?
Submitted by Dani Megert on Wed, 2016-12-21 11:37
Sorry for any inconvenience. Java 9 is still moving and the latest Java build 149 had breaking changes (new keywords and new class file format. We have uploaded a new feature patch that solves that issue. Please give it a try!
Submitted by Manoj Palat on Wed, 2016-12-21 05:35
please note that this is https://bugs.eclipse.org/bugs/show_bug.cgi?id=509354
Submitted by Markus Keller on Tue, 2016-06-07 13:03
The update site http://download.eclipse.org/eclipse/updates/4.6-P-builds/ now works with Neon (4.6) RC4 and later builds.
Submitted by Matthias Zimmermann on Fri, 2016-05-06 03:58
I did not manage to add Java9 support to the Eclipse Scout M7 EPP via Marketplace (as described above) or via P2 update site http://download.eclipse.org/eclipse/updates/4.6-P-builds/
* org.eclipse.equinox.p2.core.ProvisionException: Unable to read repository at http://download.eclipse.org/eclipse/updates/4.6-P-builds.
* No repository found at http://download.eclipse.org/eclipse/updates/4.6-P-builds/P20160308-1615.
Submitted by Ueli Hofstetter on Thu, 2015-08-13 13:09
i am getting errors when i try to compile a simple hello world program. described the problem on stackoverflow
search for eclipse-mars-support-for-java9-build-path-settings
Back to the top