Java 26
Development with Java 26 is now supported out of the box – take advantage of the Vector API (JEP 529), Lazy Constants (JEP 526), Structured Concurrency (JEP 525) and other new language capabilities while coding in the Java editor.
To access these capabilities, in addition to configuring a Java 26 JDK, please ensure you enable Java 26 preview features.
Java 25
We have made the move to Java 25 and MyEclipse now runs on Java 25.0.3, the current LTS version of Java. Please review these release notes for a list of bugs and security issues addressed. We’ll continue to keep the Java version shipped with MyEclipse updated.
MyEclipse now brings to Eclipse a powerful inline diff capability that’s available both in text editors and in the compare view. Within an editor, use the Inline Diffs option on the status bar to quickly bring up a diff against the current Git HEAD or the last saved version of your file. You can then easily navigate between changes to examine them, undo changes you’d like to delete, or make additional changes and see the diff update live. You can control how this feature works from Preferences > General > Editors > Text Editors > Inline Diffs
An inline view is also available in the compare editor, for any comparison use cases you may have – comparing changes from the staging view, two random points in a file’s history, comparison against local history, clipboard, etc. You can even use it to examine changes an AI agent like GitHub Copilot has made to your files. Just hit the Inline Diff button in the compare editor to bring it up. You can make this the default compare mode by changing the preference at Preferences > General > Compare/Patch > Inline Diffs.
Tired of crafting complex SQL queries by hand, finding that elusive artifact on Maven central, messing with Git repositories or simply want to provide better IDE tooling to support your agents? Our MyEclipse MCP Server fixes these issues by enabling AI assistants to interact directly with MyEclipse features and your development workspace through the Model Context Protocol (MCP). Besides agentic workflows, the server also enables you to perform tasks in the IDE through chat instructions, performing both analysis and executing a series of IDE actions as required.
The server exposes a set of development, database, application server, Git, Maven, and workspace tools that can be consumed by GitHub Copilot Plugin (GHCP) inside MyEclipse and other MCP-compatible clients like Claude Desktop / Code that run external to MyEclipse.Continue to interact with your AI agent as before and it should pick the right tool automatically, sometimes chaining multiple tool calls together.
_________________________________________________________________________________________________________________________________________________________
Here are just a few examples of queries you can run in a chat that will be facilitated by tools provided by the MyEclipse MCP server.
Database: “Find products that were purchased more than 25 times and list their most recent purchase dates”
Application servers: “Deploy my webdemo application to Wildfly”
Project structure: “Please analyze the structure of the spring-petclinic application”
Git: “Can you find all the Git repositories in my home directory? Can you import the qmk_firmware repository into Eclipse?
Maven: “Which JAR has the org.apache.catalina.authenticator.FormAuthenticator class? Can you add the appropriate version to my pom?”
Console: “Can you place a breakpoint in my code based on the stack trace in the console”?
The MCP Server can be configured at Preferences > MyEclipse > AI > Model Context Protocol and is automatically enabled if you have GHCP installed and a Spring + AI or higher license. Please see our documentation for further details.
Have you ever wished you could cut out the noise and just focus on your code in the IDE? With our new Zen mode, we now make this possible – activating Zen mode will take your IDE full screen, turn off the toolbar, menu bar, status bar and close all views – it will only show the currently open editors.
You can activate/deactivate Zen mode using Window > Toggle Zen mode or the keybindings – Ctrl + Alt + F11 on Windows, Ctrl + ⌘ + Z on macOS, Shift + F11 on Linux.
We now have development support for the Astro web framework, with the inclusion of the Astro language server. The TypeScript editor will now support TypeScript 5.9 language features like the import defer syntax and stricter conditional return checking.
Better Markdown support with the new Markdown language server.
Several language servers have been updated to bring in support for the latest versions of frameworks like Angular, Vue, TypeScript, JavaScript, etc.
Formatting and Code Lens preferences have been added for Javascript and TypeScript.
MyEclipse Tomcat
Our embedded MyEclipse Tomcat server has been updated to the latest release 11.0.22 to pick up the latest fixes and security updates.
We’ve added support for the latest versions of the following application servers.
Spring support in MyEclipse 2026 now supports Spring Boot 4 and Spring Framework 5.
With support for ahead of time (AOT) repositories, code lens will show you exactly what SQL query will be generated by Spring Data, and provide navigation capabilities as well. Data generated during the build process is used to provide these features, and a build can be automatically initiated from the lens to facilitate this if required.
If beans are defined via bean registrars, the tooling will detect these definitions just like other definitions and provide content assist, validation and navigation capabilities for these beans too.
API versioning is a new Spring Framework 7 capability. When versioning is used, codelens on controllers will show you a quick overview of the web configuration. New validation on version attributes will check whether versioning is configured, whether the format is correct, etc. There is also validation for the versioning strategy in the configuration.
A new logical structure view provides a stereo-type focussed view of the project, with elements grouped by their stereotype. You can use a filter to hide items from the view as well. If Spring Modulith is used then that is taken into account as well.
The JDT will now recognize Nullable, NonNull and NonNullByDefault annotations from JSpecify and the Spring framework, in addition to those defined by the JDT itself. For example, you will see null analysis validation from the Java tooling even if you use org.jspecify.annotaitons.Nullable (as opposed to org.eclipse.jdt.annotation.Nullable).
Maven tooling can now support the multiReleaseOutput setting in the maven-compiler-plugin to support the creation of mult-release JARs.
The JRE for tests (TestNG and JUnit) is derived from the Maven execution JRE – the maven-enforcer-plugins requireJavaVersion and not the maven-compiler-plugin’s target/release configuration.
The embedded Maven version has now been updated to 3.9.11.
If you have “pom-less” Maven projects, you may have seen a build error frequently displayed when builds run – this has been fixed.
Fixed a regression due to which the RAML editor was not available.
We’ve made some changes to send fewer info-style messages to the Error Log, making it easier to see actual issues.
