MyEclipse CI Stream Delivery Log

Java 26 Support

Java 26 Support
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.

Inline Diff

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.

MyEclipse MCP Server

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.

Note: For updates from prior versions, the AI component is not installed by default. Please use Help > Choose Components and install the AI > Advanced IDE AI Support component.

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.

Zen Mode

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.

Modern Web Development

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.

Application Servers

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.

• Payara v7.2026
• WebLogic 15
• JBoss EAP 8.1

Java 25

Java 25 is now supported in MyEclipse with the final versions of many preview features we already supported in MyEclipse 2025.

With JEP 512 you can have really compact source files without boilerplate, JEP 513 allows for flexible constructor bodies including the ability to execute code before calling super for instance.JEP 511 allows you to import all packages exported by a module. Various editor features like organizing imports and code cleanups have also been updated to take these capabilities into account.

To access these capabilities, in addition to configuring a Java 25 JDK, please ensure you enable Java 25 preview features.

MyEclipse 2026 now ships with Java 21.0.10+7 which was released in Jan 2026. Please review release notes for a list of bugs and security issues addressed. In future releases of MyEclipse, we will explore a shift to Java 25, which is the current LTS version of Java.

Java Language Tools

Coding

You can create multi-release JARs (where a single JAR file contains multiple versions of the same class) directly from MyEclipse by configuring the target Java release for a specific source folder.

If you have deprecated fields, quick fixes and code clean ups can now automatically correct your code to use a suggested replacement if available. Note that this capability already existed for methods.

Markdown comments can now be configured for a number of different constructs like Fields, Constructors, Getters and Setters, etc, and used when using Java 23 or higher.

Custom Folding Regions can now use the same text for both the start and end region comment – in such a case the same comment can now end a folding region and start a new one.

MyEclipse now supports JUnit 6.

Debugging

Breakpoints with hit counts and trigger points can be easily set in the editor ruler area.

Use Compare with Clipboard to compare the value of a selected variable in the Variables view with the clipboard.

It’s common to have several lambda expressions chained on a single line – when setting breakpoints, you can now choose which specific expression to break on without having to break up the expressions onto multiple lines.

To make it easier to manage breakpoints, you can now group them by enablement state.

For more details on the Java coding improvements, please see these notes.

Maven

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.

AI

MyEclipse 2026 includes Copilot4Eclipse version 1.7 which supports code completions and chat. However, for Agentic AI support, we recommend updating to the GitHub Copilot plugin, which MyEclipse is fully compatible with. MyEclipse’s AI capabilities will run with both Copilot4Eclipse and the GitHub Copilot plugin. If you do not have them installed, MyEclipse will help you install the GitHub Copilot plugin.

If both Copilot4Eclipse and the GitHub Copilot plugin are installed, the GitHub Copilot plugin takes precedence over Copilot4Eclipse for code completion.

Watch out for further advances in the AI space from Genuitec in the coming months.

Spring

Framework Support

Spring support in MyEclipse 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.

UI and AI Enhancements

A new logical structure view provides a stereo-type focused 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).

Additional Enhancements and Notes

Compare with Clipboard

You can now compare an entire file or a selected piece of text with the contents of your clipboard by using the corresponding context menu action.

Trust Stores on Windows / macOS

With this release, the trust store of the JVM (lib/security/cacerts) and the trust store of the OS are merged resulting in more robust network access from within the IDE. One common issue that this change addresses is the PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target error. This is controlled by the -Declipse.platform.mergeTrust=true switch added to the myeclipse.ini file.

Matisse

Due to changes in SWT, Matisse for MyEclipse is no longer compatible with MyEclipse 2026 and has been removed from the IDE. To continue using Matisse, please feel free to use MyEclipse 2025 or earlier versions.

Validation

A bug due to which updates in property files were not correctly picked up for validation and building has been addressed.

Java 24 and Editing

MyEclipse now ships with Java 21.0.8+9-LTS, an update from 21.0.7 in prior releases, keeping us current with Java fixes and addressing security vulnerabilities discussed here.

Java 24 Support

This release brings in code and compiler support for Java 24, in addition to support for some new language constructs.

For quick prototyping or if you’re new to Java, get right to business without the boilerplate thanks to simpler source files (JEP 495) that look as simple as this – yes, this is the entire file.

String greeting = "Hello, World!";
void main() {
    println(greeting);
}

In a constructor, I’ll bet you’ve found yourself sometimes wishing for the ability to execute some code before invoking super – with support for JEP 492, now you can!

For access to these and other features like JEP 488 and JEP 494, in addition to configuring a Java 24 JDK, be sure to enable preview features in your project or workspace.

Java Editing

Support for folding control statements as well as custom regions makes it much easier to read large pieces of code.Some interesting cleanups and quick fixes have been added too – we’d like to highlight the String concatenation to text block cleanup which now handles StringBuilder and StringBuffer based concatenation as well. There’s also a quick fix which can add permitted types automatically to switch case labels.

For a more detailed list of enhancements to Java capabilities, please refer to these documents.

Jakarta EE 11 and Application Servers

This release of MyEclipse delivers initial support for Jakarta EE 11. We’ve updated our project wizards so you can create Jakarta EE 11 projects which are created with the correct schema references, updated libraries and Maven plugins where applicable.

We don’t leave you hanging with projects you can’t deploy anywhere – our new connectors for Payara 7.2025, Glassfish 8 and Wildfly 35+ support the deployment of Jakarta EE 11 projects. In addition, the embedded MyEclipse Tomcat 11 server also supports deployment of Jakarta EE 11 web projects.

Note: Jakarta EE 11 support is still WIP in MyEclipse and updated support for specifications JPA and JSF are not yet available. Please let us know what Jakarta EE 11 area you would like us to focus on, is your company adopting new specifications like Jakarta Data?

Embedded Tomcat Update

Our Embedded Tomcat server has been updated to 11.0.11. This addresses the following security vulnerabilities: CVE-2025-48989, CVE-2025-52520 and CVE-2025-53506.

Note: The embedded Tomcat server is not likely to create an exploitable vulnerability on your system as it would require the local port to be mapped such that it is accessible externally. Unless this is explicitly done by a user, the embedded server is not accessible outside the machine on which the IDE is running. Regardless of this fact, we’ll continue to keep infrastructure of this nature updated.

Eclipse Paltform

This release is based on Eclipse 2025-06 (4.36), and brings with it a host of fixes and enhancements across the IDE. Here are a couple of highlights:

Breakpoints can now be labeled to distinguish them from others – especially useful in a sea of breakpoints which can otherwise only be identified by file name and line number. Note that this works for all languages and not just Java.

On Windows, if you use multiple monitors at different DPIs, there’s a new capability that better handles scaling the IDE on these different screens. We found that this new capability still causes rendering issues in the IDE, like in the Terminal view, so MyEclipse has it disabled by default. However, if you want to try it, please edit the myeclipse.ini file and remove the -Dswt.autoScale.updateOnRuntime=false line. You can then control it from the Preferences > General > Appearance page.

Copilot4Eclipse

This release includes an updated version of Copilot4Eclipse, adding support for the latest code completion models and an updated Copilot API for better compatibility with the GitHub Copilot service. You can now also DnD files into the chat panel to add context, and a new /clear command has been added.

Debugging

There have been so many cool enhancements in the Java debugging that we decided to give it its own section.

Our favorite feature is the collapsible stack frames that will make it so much easier to look through the stack with a focus on frames coming from user-created projects. Enable this capability from the debug toolbar.

Another useful capability is the ability to have Trigger Points automatically resume when hit, with the option to resume only if some conditions are met. This allows you to immediately stop at your intended breakpoint when debugging.

In the Variables view when stopped at a breakpoint, you can easily compare objects of the same type.

Finally, exception objects are better formatted, so you no longer need to create a custom detail formatter to be able to easily read exceptions.

For more details on these enhancements and more, please see these documents.

Reporting

A large number of fixes and enhancements have been made to our reporting tooling, including better handling of SVGs and glyphs in PDFs, corrected row alignment in spreadsheets and a new dialog allowing you to search in the Outline view. For fix details, please see these documents.

WebSphere Connectivity

For users of WebSphere 8.5 and 9, recent fix packs would allow you to start the server from the IDE but disrupt connectivity so deployment and server management would not work. This release restores normal functionality for these versions of WebSphere.

Note: The issue would affect WebSphere installations that have Fix Pack 8.5.5.27 / 9.0.5.21 or more recent versions applied.

Embedded Tomcat

Our embedded Tomcat server has been updated to Tomcat 11.0.8 to address CVE-2025-46701, CVE-2025-48976, CVE-2025-48988, CVE-2025-49124 and CVE-2025-49125.

Note: The embedded Tomcat server is not likely to create an exploitable vulnerability on your system as it would require the local port to be mapped such that it is accessible externally. Unless this is explicitly done by a user, the embedded server is not accessible outside the machine on which the IDE is running. Regardless of this fact, we’ll continue to keep infrastructure of this nature updated.

Miscellaneous Updates

Copilot4Eclipse 1.6.0
This release includes API updates to better integrate with the GitHub Copilot service.

Matisse
By popular demand, Matisse is now a part of MyEclipse again – it was removed in MyEclipse 2025.1.0. While not installed by default, you can install it from the Help > Choose Components menu.

Security Updates

JDK Update
MyEclipse has been updated to ship with and run on Java 21.0.7+6-LTS, an update from version 21.0.6 in 2025.1.0 to address a few security vulnerabilities as discussed here.

Embedded Tomcat Update
Our embedded Tomcat server has been updated to Tomcat 11.0.6 to address CVE-2025-31651, CVE-2025-31650 and CVE-2025-24813.

Note: The embedded Tomcat server is not likely to create an exploitable vulnerability on your system as it would require the local port to be mapped such that it is accessible externally. Unless this is explicitly done by a user, the embedded server is not accessible outside the machine on which the IDE is running. Regardless of this fact, we’ll continue to keep infrastructure of this nature updated.

Copilot

Public Code References
If you have “Suggestions matching public code” blocked for your account or organization, Copilot4Eclipse will now block these suggestions within the editor, and will show clickable references to the blocked code in the Chat panel.

Language Support
For new conversations, you can now specify a language for the conversation at Preferences > Copilt4Eclipse > Chat

Spring

A number of validation preferences have been added for configuration files, expressions, queries, and even best practices. You can find these at Preferences > Frameworks > Spring > Validation.

Miscellaneous Fixes

TomEE
Our TomEE connector has been updated to work with the latest release of TomEE, version 10.0.1.

Error Dialog on Startup
An error which would cause an error dialog to display on startup (“Register for CLI”) in some circumstances has been fixed.

MyEclipse AI

MyEclipse AI is a new feature that will significantly boost your coding productivity and quality. From any editor you can call on MyEclipse AI to provide realtime code suggestions and to initiate a request for AI assistance. For Java coders, MyEclipse AI provides a special annotation known as a “sparkle” in the Java Editor. Clicking a sparkle icon reveals a menu of quick AI actions that you can choose from.

The AI smarts behind MyEclipse AI is the popular GitHub Copilot. MyEclipse AI uses the Copilot4Eclipse plugin (also from Genuitec) to integrate GitHub Copilot AI capabilities directly into your Eclipse editors and from a custom Chat Panel for conversational AI.

We are just getting started bringing you AI powered code development. Stay tuned for upcoming advances in this feature.

Requirements

• MyEclipse AI requires Copilot4Eclipse 1.4.1 – if you don’t have this plugin installed, you can easily initiate installation from the MyEclipse AI menu, or alternatively, install Copilot4Eclipse from the Eclipse Marketplace.
• MyEclipse AI is available at the MyEclipse Spring + AI license level or greater. A free 30 day upgrade to this level is available from within MyEclipse.
• GitHub Copilot Subscription – you will need a GitHub Copilot subscription. A free subscription level is available to enable you to get started at no additional cost.

Copilot4Eclipse

Copilot4Eclipse is a companion plugin developed by Genuitec that integrates GitHub Copilot features into Eclipse editors and provides a conversational AI Chat Panel. Copilot4Eclipse is installed by default in new MyEclipse installations.

If you’re updating from a prior MyEclipse version, manually install Copilot4Eclipse from the MyEclipse Component Wizard at Help > Choose Components. You can also use the MyEclipse Component Wizard to uninstall Copilot4Eclipse and many other components.

Copilot4Eclipse can be used in multiple ways:

• Use it with MyEclipse AI.
• Initiate conversations (from writing tests to fixing code) using its context menu in the editor.
• Chat directly from the Copilot4Eclipse view.

With this latest release of Copilot4Eclipse, you can choose between different AI models from the Copilot4Eclipse chat view.
To see Copilot4Eclipse in action, check out these videos.

Java

MyEclipse 2024 ships with and runs on Java 21.0.6.

Java 23 Support

MyEclipse 2025 enables development with the latest Java 23 language features. To create and compile Java 23 projects, configure MyEclipse with a Java 23 Runtime.

Java 1.7 Support Removed

Compiling against a compliance level of Java 1.7 or below is no longer supported. This is due to Eclipse removing support for these source levels in the JDT, similar to the JDK itself removing support for compiling against this version of Java since version 20. If your project is set to compile with Java 1.7, we would suggest upgrading it to source level 1.8 (ideally higher) or using the prior release, MyEclipse 2024.1.2.

Tooling Improvements

• Ctrl / Cmd + Click on a type will now give you the option to open a Call Hierarchy too, in addition to its declaration and implementation.Recall in the last release this functionality was added for fields and methods.
• Debug inspect popups can now be pinned, so you won’t lose it if you focus on other elements.
• Like using Text Blocks? If you use Java 15+, the quick fix to convert a concatenation of literals and variables into a MessageFormat call will now effectively use text blocks.
• Several cleanups have been added, including a few key enhancements to the if / else cleanup to include null handling and Enum constants

Application Server Connectors

In order to support newer web applications, MyEclipse has updated its embedded Tomcat connector to Tomcat 11.0.2 and its embedded Derby database server to 10.17.1.0. Additionally, a new connector for Tomcat 11 has been added.

MyEclipse’s server connectors are compatible with the latest versions of popular app servers, including

• Glassfish 7
• Wildfly 35
• Tomcat 11
• TomEE 10
• JBoss EAP 8
• Payara 6.2025
• OpenLiberty 25

Users can continue to deploy, serve, debug, and run against these app servers with ease.

Modern Web

Develop with the latest version of Angular, Vue and React with this release of MyEclipse.

Support for the latest modern web framework is powered by updates to several language servers under the covers from TypeScript to XML. Fixes have been made to improve language server stability during development. These updates improve the editing experience with a variety of languages like HTML, XML, JSON, CSS, YAML and more

Spring Framework

A number of Spring annotations now have better language support in the editor, with content assist, navigation and validation provided. These include @Profile, @Resource, @Qualifier, @Value, @DependsOn, @ConditionalOn? and many more.

Auto completion is now available for CRON expressions and an inlay hint will help ensure you got it right!

SpEL expressions support go-to-definition for beans and methods.

A new delta based index cache consumes less memory and makes the Spring tooling more performant.

Miscellaneous Improvement and Key Fixes

MyEclipse 2025.1 is now based on the Eclipse 2024-12. This brings improved compatibility with third party plugins and core platform improvements.

Sticky Scrolling can be enabled for text editors, and will “stick” the most important lines to the top of the editor as you scroll. Go to Preferences > General > Text Editors to turn this on.

The compare editor will now show syntax highlighting for more languages.

Parting Thoughts

AI is rapidly transforming the way we will develop software. Begin your transformation with MyEclipse 2025 and its most productive Java enterprise coding tools ever.  We look forward to seeing what you create with MyEclipse.

Apache TomEE

TomEE 10 is still not GA, but we did add in a new connector that will allow you to use it right away! Additionally, we’ve fixed a bug where deployments to TomEE would not respect the “Web Context Root” value in the project’s deployment assembly.

PHP & Vue

If you added Eclipse PHP Development Tools (PDT) to MyEclipse, you’d find that PHP files were rendered in greyscale, er …  without syntax coloring – this has been fixed.

When editing `.vue` files, duplicate content assist suggestions will no longer appear for both Vue 2 or Vue 3 projects.

Welcome to the Future with Copilot4Eclipse

MyEclipse 2024 is compatible with Copilot4Eclipse 1.2.0, the latest release of our very own GitHub Copilot plugin for Eclipse. Inline completions, and persistable chat conversations are now fully supported.

For starters, Copilot4Eclipse can give you more intelligent content assist within your editors, from suggesting simple method invocations to generating several screens full of implementation code. With the Chat panel however, you can do even more – get it to explain some new code to you, fix your bugs, add dependencies, generate tests and even make writing documentation easier. Chat conversations are persistable, so you can come back to any number of context-rich conversations anytime.

Future versions of MyEclipse will include richer integration with Copilot’s capabilities through Copilot4Eclipse. To see Copilot4Eclipse in action, watch these videos.

Note: Copilot4Eclipse is not currently being bundled with MyEclipse, please install it from the Eclipse marketplace.

Application Servers

This release includes new connectors for Payara 6.2024 and updated support for Open Liberty Server, now supporting version 24 of this server.

Our JBoss EAP connectors were updated to work with recent versions of Red Hat JBoss EAP 8.0, and updated connectors for WildFly will work with WildFly 31 and 32. Notably, WildFly 32 preview includes some level of Jakarta EE 11 support. While we don’t support Jakarta EE 11 development yet, you can bet we’re keeping our eye on this specification for support in upcoming releases of MyEclipse. As a reminder, we do support Jakarta EE 10 development with these servers already.

And, somehow missed from MyEclipse for many a year, (and almost forgotten in these notes too) we have a new connector for WebLogic 14.

Java

Java 22 Support

With this update we add support for Java 21 and Java 22. These versions of Java are supported in our Enterprise wizards as well. Please note that MyEclipse does not ship Java 22, and you will have to configure your own JRE in Preferences > JREs to compile against this version of Java.

Some Java dev updates you’re sure to find interesting:

• New, smart, Make Static refactoring for instance methods
• Annotation based resource leak analysis
• For switch expressions, validation and quick fixes around default/break
• Better formatting for switch expressions ensures arrows are correctly aligned
• A new clean-up can replace calls to deprecated methods with inlined calls
• Ignore whitespace in compare editors is now smarter and will no longer ignore semantically significant whitespace
• Using Ctrl + Click for fields / methods will give you the option to quickly open the Call Hierarchy

Note: MyEclipse 2024.1 runs on an updated version of Java 17 under the hood – Java 17.0.11. We will be moving to Java 21 for subsequent major / minor releases

Warning: The JRE preference page (Preferences > Java > Installed JREs)  includes a new preference, “Detect available JVM installations at startup” that in some circumstances, could change the default JRE in your workspace. If you notice issues around this, please confirm that your workspace has the right default.

Spring

Our Spring tooling is significantly faster and more resource efficient at validation, code completion and symbol reconciliation. This means less memory used and the ability to handle larger Spring projects seamlessly.

If you’re working with Spring boot and need to add more boot dependencies to your POM, use the Add Spring Boot Starters hint to easily do so.

The Boot dashboard will now specially indicate active profiles.

You will also notice improvements in the Spring Language server behavior too, no longer running when not required, getting stuck mid-job or taking up resources – do let us know if you still see this happening.

Modern Web Development

Angular 18 and the latest versions of Vue and React are supported by this release of MyEclipse.

Note: In .vue files, you might see duplicate content assist suggestions. To resolve this, go to Preferences > Language Servers and disable the first two Vue language servers, labeled “Vue Language Server” and “Vue Volar Language Server”.

During creation of the above projects using our Wizards, the Terminal+ view would sometimes not accept input if the CLI had questions to ask, ultimately preventing the project from being created – this issue has been addressed.

A number of additional language servers, grammars and extensions have been updated for better content assist, validation and updated language support. These include TypeScript, JavaScript, YAML, JSON, XML, etc. In that same vein, a new Language server view gives you some idea of what servers are active for your workspace.

Debugging

Under the covers, the Chrome debugger has been updated to use vscode-js-debug, no longer the deprecated vscode-chrome-debug framework. You should now have a better debug experience for modern web applications inside MyEclipse. String interpolation for JSON launch parameters is now supported; you can specify these on the Debug Adapter tab of your launch configuration. Like the following example, you can now use variables in the JSON, allowing you to check-in these configurations without system specific values.
{
“webRoot”:”${workspace_loc:/project_name}”,
}

Maven

Embedded Maven runtime has been updated to Maven version 3.9.6.

You can specify a toolchain.xml to be used in workspace builds at Preferences > Maven > User Settings. Note that the maven-toolchains-plugin is now disabled by default for workspace builds.

Source/resource folders outside your Maven project’s base directory are now added to the project as linked resources.

If you use a .mvn/maven.config file within your project for global or user settings, the tooling will now take these into account.

Miscellaneous Enhancements & Key Fixes

MyEclipse 2024.1 is now based on the Eclipse 2024-03 with core improvements to the platform and improved compatibility with recent releases of third party plugins.

Quick search terms will be displayed alongside the Quick Search title in the dialog, making it easy to distinguish between open Quick Search dialogs.

The compare editor will now display a count of the number of differences. When diffing Java files, this figure will change based on the selection in the Java Structure Compare tree.

Reporting tooling has been updated from BIRT 4.13 to BIRT 4.15, bringing with it a large number of improvements across the board from formatting and layout fixes to improved rendering. Please see these release notes for details.

Our WindowBuilder integration has been updated from version 1.12 to 1.15. Changes include support for Java 21, Jakarta annotations in E4 parts, lambda support and dozens of fixes. Release notes for more details.

Important Changes to Note

As mentioned earlier, your workspace’s default JRE could change as a result of a new, “Detect available JVM installations at startup” preference on the Preferences > Java > Installed JRE page, based on how Java is set up on your OS.  In case this happens, simply go to this page to correct the default JRE.

For security reasons, HTTP is no longer supported when installing from update sites, and you must use HTTPS instead. If, for some reason you still need to use HTTP, please edit the myeclipse.ini file and add this switch at the end -Dp2.httpRule=allow

CodeTogether has been removed from the MyEclipse distribution. If you were actively using CodeTogether and had not already updated it from its public update site, it will be removed by this update. Please manually install it from the Eclipse marketplace to ensure you are working with a more recent and supported release. If you are not using CodeTogether, simply close the CodeTogether view to remove it from your perspective, if present.

Cross-product Fixes and Improvements

For Maven projects, we fixed a regression  in 2023.1.1 which prevented the dependency IntelliSense in the pom.xml from working.

The integrated version of Spring Tools has been updated from 4.18.0 to 4.19.0. This addresses performance issues reported by some of our users with an excessive number of Spring related jobs running in the workspace. If you continue to experience issues, please let us know.

The filter in the MyEclipse Explorer can now search through resources that were nested under the Java Resources node.  If you’re not familiar with this filtering capability, do give it a try!

If you updated to the 2023.1.1 release from a prior release, installation of several third party plugins would fail with odd dependency errors. This issue would not affect fresh installations of 2023.1.1. Update to 2023.1.2 to resolve this issue, restoring your Eclipse ecosystem freedom!

A critical failure in the Report Web Project wizard would prevent it from opening. This has been resolved.

You’d see a number of error dialogs when dealing with Mylyn tasks – those that existed in your workspace as well as when creating new tasks. These issues are now resolved.

For our MyEclipse Secure customers with Pro / Blue licenses, a MyEclipse 2023.1.1 installation created using the pack would not launch – this issue has been resolved in the 2023.1.2 packs.

Vue

If you had an old version of create-vue already installed, our new Vue 3 wizard could create projects with older versions of Vue, missing resources or incomplete metadata. We’ll now ensure the latest version of Vue 3 is used. We’ll work towards providing additional control here in future releases.

Additional issues around incorrect or missing validation of TypeScript sources in Vue projects, duplicate content assist proposals and broken inline references have also been addressed.

Legacy Tooling Support

We realize it’s often difficult to move on from legacy tooling and frameworks for a variety of reasons. With MyEclipse, we strive to keep these technologies working for you, even after they are abandoned by the rest of the ecosystem.

One of our users complained that in 2023.1.0, they could no longer launch Ant builds with Java 8. While we provided a workaround, with this release, you will now, once again, be able to launch Ant builds with Java 8.

Another MyEclipse user brought to our attention the fact that some CVS operations were not working. We’ve fixed this as well and you can now continue to interact with your CVS repositories as before.

Miscellaneous Fixes

A regression in 2023.1.0, the dependencies-only Maven facet would not result in Maven dependencies being actually added to the project – this functionality has now been restored. Several additional Maven fixes were made, including a fix that prevents dependency resolution from taking place too often.

A few fixes to our Quarkus / Qute tooling to ensure corresponding language support is made available only when appropriate.

The default Open Type hotkey was incorrectly bound to the Open Symbol action, even when editing Java files. The default binding has now been restored.

On Linux, we fixed an issue where the MyEclipse installer would not work with Java 17 and/or the Wayland display protocol.

If you joined a CodeTogether session from MyEclipse, the client editor showing the host files would be unusable – you can now easily code together … again!

We’ve fixed an issue where a large number of JPA update jobs would unnecessarily run, spamming your progress view.

Jakarta EE 10

Jakarta EE 10 is the first major release of the specification which brings far more to the table than schema updates. From the new Core profile to improvements in CDI and EL, there are plenty of features to take advantage of – there are 12 minor and 11 major updates to specifications in this release!

With updated wizards for multiple enterprise project types – EJB, EAR, Web, Web Fragment, etc., you will be able to easily create projects with this version of the spec. Of course, we won’t leave you hanging – deploy and serve these projects using our updated server connectors. We’ve added the following connectors in this release:

• GlassFish 7.x
• Payara 6.2023.x
• JBoss EAP 8.x
• Tomcat 10.1.x
• Open Liberty 23.0.0.x
• WildFly 27+ (compatible with WildFly 28)

Java

Java 20 Support
As Java continues to evolve, in MyEclipse 2023, we extend our support to Java 20 with support for Virtual threads, structured concurrency, pattern matching for various constructs, the vector API, and more. Beyond IntelliSense and validation, these constructs are further supported by corresponding refactoring and clean-up actions too.

New Java Development Features

MyEclipse itself will run on Java 17 LTS – we ship a Java 17 JDK with the IDE.

Did you know you could label specific Object instances? We added this capability in our last release, but it was specific to the Variables view. These labels will now show up in the Expressions view as well, even for watched and inspected objects.

The Favorites list (Java > Editor > Content assist > Favorites) will propose static members from this list even if the import is missing. You can now easily add members to this Favorites list by using Ctrl / Cmd + 1 on a static import in the Java editor.

Several quick fixes have been added, like one for creating sub types for sealed types, extending interfaces, extracting lambda bodies, etc. –  don’t forget to use this shortcut while editing.

Don’t like how the new switch constructs are formatted? New formatting settings now allow you to customize this.

From the Java Stack Trace console, you can now use hyperlinks to jump to Java types for stack traces copied from the Debug view using the Copy Stack action.

Spring

Spring 6 and Spring Boot 3

Whether you’re working on the very latest versions of Spring, like Spring Framework 6 or Spring Boot 3, or on legacy applications that use Spring 2, our updated tooling will give you a superlative Spring development experience.

Tooling Improvements

We’ve got several exciting enhancements on the tooling front for you to enjoy.

Live information from your running application can be displayed right in your editor as code lens annotations and on hover.

Use the new Spring Symbols view to quickly find and navigate to beans, functions, request mappings and more at the workspace, project and file level in your IDE.

We have a new editor for Spring Boot properties files with content assist and validation to ensure you’re not specifying imaginary properties.

Validation will let you know if there are updates to the version of Spring Boot you’re using in your project and refactoring to help you execute the update if you choose to do so.

Modern Web Frameworks

Angular
This release supports Angular 16, which is the latest version of Angular at the time of this release. With changes in our core to support recent changes made to the Angular CLI, we expect our tooling to continue to support future versions of Angular as well.

Vue
Our new Vue project wizard makes Vue 3 project creation a cinch. We’ve also added superlative support for Vue 3 development with the new, recommended Volar extension to MyEclipse. This provides better support for the  development of Vue applications with TypeScript, and support for Vue 3 specific features like the composition API, fragments, teleport tag, etc.

Note: While there is no Vue 2 project wizard, Vue 2 continues to be supported in MyEclipse. Import existing Vue 2 projects into MyEclipse to take advantage of our Vue 2 framework support.

Frontend Language Support

JavaScript and TypeScript
Besides grammar updates for improved language support, you can choose to display inlay hints for parameter types, return types, member values, etc. Please see the Preferences > JS/TS > JavaScript / TypeScript > Inlay Hint preference pages.

`jsx` and `tsx` files are now better recognized as JavaScript and TypeScript files.

Better detection of tsconfig files in your projects results in an improved TypeScript debugging experience.

XML / HTML / CSS / YAML
Significantly improved coding experience by means of content assist, validation, formatting, typing enhancements and more. Please see the Preferences > CSS / HTML / XML / YAML trees for settings you can use to customize the language support.

Hibernate 6

Whether you’re using Hibernate as a JPA provider or standalone, our wizards will allow you to create and develop against the latest versions of this OG persistence framework – Hibernate 5.6, 6.1 and 6.2. In the light of API changes in Hibernate 6.x, we’ve ensured that our reverse engineering code generation adapts based on the version of Hibernate you’re using in your project.

Maven

The pom.xml editor now provides content assist suggestions for Maven dependencies and plugins, making it much easier to manage these without a wizard.

In the new project wizard, archetype parameters can be validated with regular expressions, if available. Archetypes can also use Groovy scripts for processing of input parameters.

For large Maven projects, build performance has been improved, along with a reduction in memory consumption.

Quarkus

We now have support for Qute templates in MyEclipse. If you’re working with Qute files, you will get advanced content assist and validation when editing. Integration between Java and Qute ensures you get support for method parameters, `@TemplateExtension` methods and value resolvers.

An updated Quarks project wizard allows you to easily sort through a categorized list of hundreds of extensions that you can choose for your new project.

Miscellaneous Enhancements & Key Fixes

This release is built on Eclipse 2023-03 and will be compatible with the latest versions of any additional plugins you may wish to install.

The IDE will start faster than ever, so you can get to coding sooner. These improvements also reduce the amount of time required for the IDE to restart after adding/removing plugins.

The console can now display colored output, and you will notice this when doing Maven builds, running applications, etc.

All text editors now support new shortcuts for efficient multi-selection editing.

There’s a new, “Compare with each other” action in the Git staging view that you can use to compare staged / unstaged files with each other.

Tired of a flickering set of jobs in the progress view where you could accidentally kill the wrong one? New jobs are now always added at the bottom for a predictable experience.

Inline debug values will now show up when debugging languages like Node.

If you rely on our UML1 tooling (yes, we still support UML1), an issue where the editor menus would not stay open for more than a split second has been addressed. You no longer need to be an e-sports champion to click the menu items!

Our React Serve  launch configuration will now correctly serve React applications for easy deployment.

Annoyances while editing HTML files around the use of comments and editing tags have been fixed.

A few invalid validation (ha!) errors with JSP-EL syntax have been addressed.

WebSphere 8.5.5 with recent fix packs applied can now be launched from MyEclipse without the need for any workarounds. We also fixed a bug where MyEclipse would not be able to stop a WebSphere server that was configured to run as a Windows service.

Jakarta EE 9 and 9.1

We’ve updated our support for Jakarta 9 and added preliminary support for Jakarta 9.1 – at this time, we’re the only Eclipse product to support this version of the Jakarta EE specification.

When you create any enterprise project, you can choose these versions of the specification and we’ll make sure your projects are created with the right versions of the schema  and the right libraries. Here’s a reminder on the project types we support:

• Enterprise Application
• EJB
• Web & Web Fragment
• Web Service
• Connector 
• Application Client

Specifications like JAXB, JPA, JAX-WS and JAX-RS have been updated as well.  For instance, if you want to use Hibernate 5.6 or EclipseLink 3 as a JPA 3.0 provider, you now can, easily. All our JPA functionality works with this version, including reverse engineering. I’m sure I’m forgetting to mention a specification or two here, but our developers haven’t –  explore them all in the IDE!

Now – where can you deploy these, “cutting edge” projects? No worries – we’ve got you covered with a bunch of new server connectors:

• GlassFish 6.0 – 6.2
• Payara v5 and v6
• Wildfly 23 onward
• IBM’s Open Liberty

Of these, Payara v6 and Wildfly 24+ support Jakarta EE 9.1, while most of the others support Jakarta EE 9. Do check the connector for additional details.

Modern Web Enhancements - Vue, Angular, React and More

You’ve asked and we’ve delivered – Vue support is here! Also, with updates to all embedded language servers, we now support newer versions of popular modern web frameworks too. MyEclipse supports Angular 13.2+, TypeScript 4.5, and the most recent versions of React as well. 

Developing with Vue? MyEclipse provides syntax highlighting, IntelliSense, validation, quick fixes and navigation. And yes, Vue 3 is also supported!

Support for more recent versions of Angular means you will no longer see erroneous errors in your Angular projects.

JavaScript

JavaScript language support can be enhanced by creating a jsconfig.json file in the project to define a project context. The config file specifies files to be included, ECMAScript version targeted, module systems, etc. Follow the prompt in the editor and MyEclipse will create this file for you – you can tweak it further as desired, more details here.

Snippets

How do you insert a copyright symbol into your markup? Stop googling and use the new  HTML section in the Snippets view to drag and drop this character entity into your code.

Servers View

Our Servers view has been enhanced to give you the ability to launch additional modern web applications, right from within the IDE. In addition to Angular, you can now launch Vue, React, Webpack and Next.js applications too.

Note: If you’d like to hide these launch types from the UI, deselect the, “Show NodeJS Launches” item from the view’s menu.

Java 17

We have inbuilt support for Java 17 – just ensure you configure a Java 17 JDK / JRE in the JRE preference page, and you’re good to go. If you’re interested in preview features like, “Pattern Matching for Switch”, please enable features for Java 17 from Preferences > Java > Compiler when you have a compliance level of 17 selected.

MyEclipse Core Updates

Apple Silicon Support

If you’re using an Apple Silicon chip like the M1, MyEclipse can now run natively on this chip, resulting in significant performance improvements. For one of our test workspaces, this reduced the amount of time MyEclipse took to be ready for work from 50 seconds (when running in the Rosetta emulator) to 12 seconds. Of course, these figures will be different for you, but we wanted to give you an idea of how much faster this build can be.

Note: If you have an existing install, updating this install will keep you on the Intel build. Uninstall MyEclipse and use our new offline installer to reinstall it. Be sure to select Apple Silicon on the architecture selection page.

Smaller Footprint

In a bid to decrease the size of our installers and the number of plugins active in a MyEclipse installation, new installations will not include a number of old, heavy libraries and library related plugins that are not often used. If MyEclipse detects that you have projects that use these libraries, we will help you install them.

The MyEclipse for Spring, and the ICEFaces Support components will also not be installed by default.

To install these components, simply go to Help > Choose Components and install the desired components.

• Legacy built-in libraries support for MyEclipse – set of old built-in libraries used by projects that do not use Maven or Gradle
• MyEclipse for Spring – additional tooling for Spring 2/3, not applicable for newer versions of Spring 
• ICEfaces Support for MyEclipse

Offline Installations
If you do not have Internet access, you can download an archived update site from here, and unzip it, either on your local system or on a locally accessible web server. Go to Preferences > MyEclipse > General and put the URL in the Offline Component Installation field and the component flow described above should work seamlessly.

Eclipse 2021-12

With this release, we’ve upgraded our base Eclipse from 2021-03 to 2021-12, so there are a lot of improvements across the board, and we’ve summarized our personal favorites below.

Java Debugging & Launches

The new Launch Configuration view makes it easy to manage your launches without having to go through the launch dialogs.

What do you do when you want to closely observe the value of a particular variable in a chain? Most often, you create an intermediate variable to hold the value. Well, you can now simply hover over the variable to see its value. In a related enhancement, you can also label objects so they are highlighted and stand out in the variables view.

Git

If you work with GitHub or GitLab, you’ll appreciate the ability to fetch pull and merge requests in the context menus. 

From a more efficient directory comparison display to the ability to compare with the working tree, branch, etc., there are now a plethora of enhancements that make it easier to analyze differences.

Misc Enhancements

Want to edit multiple areas in your file at once? Easy! Use the new multi selection capability. Use Alt + Click, or Select All in the Find / Replace dialog.

To take a look at all the enhancements yourself, consider browsing through the N&N pages for 2021-06, 2021-09 and 2022-12.

Live Share your Coding Sessions with CodeTogether

If you’ve ever wanted to code together with your colleagues, à la “Google Docs for code”, this is now super simple with our CodeTogether integration. Coding sessions you host can be joined from other IDEs, and they don’t even need to be MyEclipse – other distributions of Eclipse, IntelliJ, VS Code and even a browser will do just fine. You can host a session for upto 60 minutes with 3 guests for free! Find out more at codetogether.com.

Note: Use Help > Check for Updates to check for CodeTogether updates too – these updates are independent of MyEclipse updates.

Key Fixes and Enhancements

We’ve updated the templates in our DB Driver wizard, making it easier to create drivers for more recent databases like H2, MariaDB, MongoDB, etc., and newer versions of databases like PostgreSQL. We’ve also removed templates to databases that are dead/rarely used. Drivers you’ve already defined will remain untouched, of course, and we remain compatible with any JDBC compliant database, even if it isn’t listed – just use the Generic template.

Fixing a regression in MyEclipse 2021, the XML editor in MyEclipse can now display line numbers if desired.

Comparing a pom.xml file with a prior revision would display a blank pane, with no diff details visible. Now fixed!

Do you use JSP in JavaScript in JSP? Yes, you heard that right – scriptlets like this were marked with an error in our JSP editor, but they will now be validated correctly.

In extremely rare cases, bringing up the context menu for a project in the explorer would leave you hanging for a long time, with the menu taking quite some time to show up. No more waiting with this release!

On Windows 11, attempting to use our awesome Terminal+ would result in an external terminal being opened instead – certainly not cool! We’ve fixed this so you can continue to use our powerful, integrated Terminal+.

If you use our custom, “Dependencies Only” Maven support, the Maven Dependencies node will now correctly populate with your referenced dependencies.

In the light theme, arrow heads in UML2 diagrams were invisible – you can now see them without having to explicitly change their colors.

New Editors

The core of an IDE is its editors, and this release has updates, as well as brand new editors for a whole slew of web dev file types. We’re talking about core editors like HTML, JavaScript, JSON, TypeScript, and their React counterparts, JSX and TSX.  For stylesheets, CSS , SCSS, SASS, and LESS. Editors for the  XML family, and YAML and RAML too.  Yup, that’s a lot of editors.

Language Server Tech

The editors are based on Language Server technology, and will provide the most capable, up to date, efficient and standardized coding experience going forward. Capabilities like validation, content assist, hover info, outlines, refactoring, navigation and even code analysis are all serviced by the language server protocol, so we’re talking about rich support for each of the types mentioned above.

These editors have been added to MyEclipse through the continued development and refinement of the preliminary integration of Eclipse’s WWD project in the MyEclipse 2020.9 release last year. We’ve been paying attention to performance as well, and have ensured that our integration doesn’t come at the cost of IDE performance, with changes in how the language servers are initialized as you work on different files types across your workspace.

Accessing the New Editors
We’ve set up IDE defaults so that your files will automatically open in the correct editors, no additional steps required. Some editors like the MyEclipse visual HTML / JSP designers are now no longer the default for their corresponding file types, but they can be accessed through the Open With context menu. Conversely, while newer editors are available for file types like XML, XSD, XSL, etc., we’ve retained the older MyEclipse editors as default in these cases for now.

JavaScript

The new JavaScript editor is based on the language server tech we mentioned above, replacing our dated Tern based support. The editor now supports ECMAScript 2020 out of the box, and the support extends to JavaScript in JSP files too. This is a huge jump from ECMAScript 2015 that we natively supported in MyEclipse until now. So everything from async and yield, to the new nullish operators and optional chaining, are now fair game for the JavaScript editor. ESLint support is integrated as well.

TypeScript

The new TypeScript editor supports TypeScript 4.1, again, a huge jump from version 2.5 natively supported in MyEclipse.  As always, TSLint continues to be well supported.

Differences of Note

Do we still need CodeMix?
As some of you might be aware, CodeMix could be installed into MyEclipse to add up-to-date support for all the languages we discussed and frameworks like Angular and React. CodeMix has now been EOLed, but the great news for MyEclipse users is that the support now inbuilt in MyEclipse replaces what CodeMix would provide. Frameworks like Vue that we don’t yet support natively in MyEclipse will be picked up in subsequent releases. Going forward, we will continue to provide and improve on modern web support in MyEclipse itself.
CodeMix is no longer compatible with MyEclipse and cannot be installed into this version.

Project Level Validation
Project level validation for JavaScript, TypeScript and HTML has been removed. We found that this validation, especially in the case of JavaScript, was often not desired by our users and time consuming, despite our efforts to make it performant across the years. These files will be validated when you open and edit them, with the newer language server tech which provides a much higher quality of validation.

Editor Preferences
Several editor, typing and coloring preferences for these file types have been removed. We found that this level of customization was seldom used, with most users making their settings at the global level – these settings will apply to these types.

Updated Support for Modern Web Frameworks

Angular

Angular support in MyEclipse has been given a major refresh. We now support the most recent versions of this framework, including Angular 12.  The new project wizard has been enhanced, and several  new wizards have been added. Content assist, validation and navigation in Angular templates has been significantly improved. Of course, you can still start and stop Angular projects from the Servers view, and we’ve fixed a bug that prevented CodeLive  from working with Ivy built components. 

React

There’s a new React project wizard that makes it easy to create a blank react project, or one with the Next.js framework. And you can choose whether you’d like to use JavaScript or TypeScript too.

Server Connectors

We’ve added new server connectors for WildFly 21, 22, 33, JBoss EAP 7.4 and Tomcat 10.  Do note that Tomcat 10 supports the new Jakarta EE spec, so if you want to deploy older applications to it, you’ll have to migrate them first, or use Tomcat 10’s legacy converter. Read more here.

We’ve also added an embedded version of Tomcat 9, so out of the box you will be able to deploy to this server. The embedded Tomcat 8.5 server (updated to version 8.5.66 from 8.5.9) remains for now, but will be removed in a future release.

Jakarta EE 9

Enterprise Java support has always been at the core of MyEclipse, and we’re thrilled to be able to continue providing this support through the next level of Java in the Enterprise –  the Jakarta EE 9 platform. This release includes experimental support for Jakarta EE 9 – almost all of our new project wizards will allow you to choose this version when creating a project. Projects created with this version will include updated libraries and reference corresponding Jakarta EE 9 schemata. 

As this is a preview release, some support is still not available – our form based editors do not support this version, and our web services wizards (JAX-WS/RS) and JPA support have yet to be updated.  We will continue to focus on this area in future MyEclipse releases.

Eclipse 2021-03

We’ve jumped three Eclipse versions since the last MyEclipse release, which was based on Eclipse 2020-06, so there are literally hundreds of enhancements in the product as a result. Here are a few of our favorites:

For those of you on macOS Big Sur, you’ll be happy to know that all UI glitches, missing capabilities and bugs have been addressed, so this version of MyEclipse works out of the box on Big Sur. A list of issues fixed can be found here.

On Windows, you can scroll horizontally using Shift + Mouse Wheel and touchpad gestures – this was already possible on other OSes.

The last edit location is a feature many don’t use, but can make such a difference to your coding productivity. Instead of just remembering the last edit location, the last 15 locations are now persisted. Use [Ctrl + Alt / Ctrl + Opt] + Left/Right Arrow to go backwards and forwards through your edits, and if you haven’t tried this feature before, now’s a good time to start!

If you’ve ever wanted to do a repeated search in the console view, you now can with the Ctrl + K & Ctrl + Shift + K.

Java Enhancements

Development with Java 15 and 16 language features is now supported. Text blocks, Records (including a new Record wizard), pattern matching for instanceof, support for sealed classes and interfaces, etc., are supported in the editor.  Visit these pages for more examples of supported Java 15 and Java 16 code.Note: MyEclipse bundles Java 14, you would need to manually configure an updated JRE to code using Java 15/16.

For faster searching, a new parallel index search is now enabled by default, taking advantage of available hardware to improve performance.

Running a program that takes dozens of arguments, sometimes too many for the command line? If using Java 9 or higher, you can now specify arguments using an argfile in any Java based debug configuration.

We all love NullPointerExceptions, don’t we? Would it be great to know which variable was actually null? Well, thanks to JEP 358, the culprit will now be named and shamed in the exception message. You need to use Java 14 or higher to launch, and check the -XX:+ShowCodeDetailsInExceptionMessages box in the debug configuration.

Content assist for methods will now insert best guessed parameters too, and hopefully save you some time. You might also find general content assist behavior improved as by default it will intelligently overwrite code with selected proposals instead of inserting the proposals. Several new quick fixes have been added across the board.

If you’re one who likes Java code cleanups there were dozens added.

The integrated version of JUnit has been updated to version 5.7.1.

Spring

This release includes a couple of really cool Spring features we’d like to highlight.

First, there’s a new wizard that allows you to add Spring Boot starter modules to existing Spring Boot projects. Select Spring > Add Starters from the context menu of an existing Spring Boot project.

If you have Docker running locally, you can build docker images from your workspace Spring Boot projects by simply dragging and dropping them into the Boot Dashboard. You can then run your application on Docker, even debugging it directly within the container. You can add Spring Boot Devtools to your project to speed up change cycles.  More details here.

Quarkus

With an update to version 4.19.0 of JBoss Tools, our integrated Quarkus and OpenShift tooling has also received updates.

When creating a new Quarkus project, if the extension(s) selected support CodeStarts, your project will be initialized with example code.
Instead of using an application.properties file, you can use an application.yaml file in more recent versions of Quarkus. Simply create this file manually and you will get content assist within. You can also specify environment variables in run / debug Quarkus configurations.

OpenShift

The OpenShift Application Explorer is now based on odo 2.x, which allows development to be based on a devfile.  These components may expose start projects, i.e. sample code that will initialize your empty project. Specific content assist is also available for devfile.yaml files.
For clusters which use more enhanced authentication infrastructure, you can now still login with the wizard, which will pop out an embedded web browser as required.

VisualVM

Our VisualVM integration was MIA for a few releases, but by popular demand, we now have a fresh new integration of the very latest 2.0.7 version.

Java Improvements and Java 14

MyEclipse now ships and runs on Java 14, so we’re now more ready for this version of Java out of the box. Of course, you can continue to work with and compile against earlier versions of Java.

Specifically on Java 14, there’s a new Record wizard and template, and support for the new Switch Expressions and text blocks. Do note that some of these are preview features which must be specifically enabled using Configure > Enable preview features from the project’s context menu. 

General Java development has received performance improvements in the form of non-blocking completions for content assist. Our other favorite features are the ability to inspect synthetic variables during debug and the new code clean up options.

For more details, please read the JDT new and noteworthy.

Quarkus

If you haven’t heard of Quarkus yet, now’s the time! It’s a Kubernetes Native Java stack for HotSpot or the GraalVM, using the best Java libraries and standards out there. We’ve integrated Quarkus Tools from JBoss Tools to bring Quarkus support to MyEclipse. What support are we talking about?

The new Quarkus Project Wizard helps you easily select the required dependencies when creating a project.

The application.properites file is where you configure Quarkus applications. The editor provides detailed content assist for properties, based on your project’s configuration and it will also validate the file.

The Quarkus Application launch configuration can be used to run and debug your application.

Docker and OpenShift

Need to manage the scores of Docker images you have and containers you have running? Look no further than the integrated Docker Explorer. You can download images using the Pull Wizard, customize how you run them with the launch configuration, and a handy Dockerfile editor to easily configure your container. Our Docker support comes from Eclipse’s Linux Tools Project and you can find out more about the tooling here.

Now, if you’re developing on OpenShift, we’ve integrated Open Shift tooling from JBoss Tools – a wizard to create new OpenShift applications, Server view integration allowing you to start and stop your container as well as a dedicated Open Shift Explorer are just the highlights of this feature set.
In the coming weeks watch out for more content from us, helping you make the most of MyEclipse for container development and deployment.

Wild Web Developer

With the integration of Eclipse’s Wild Web Developer (WWD) project, support for a number of additional web languages/frameworks is now available in MyEclipse. Several technologies supported by WWD are already supported by MyEclipse, but you now have the power to choose the tools that suit your needs. To use the WWD support instead of in-built MyEclipse support, bring up the context menu on the file, and choose Open With > Generic Editor.

Enabling Language Servers
You may see a warning about Language Servers being disabled – in this case, please go to Preferences > Language Servers and enable the server you need. Do note that some of these servers need a globally installed version of Node on your system to function, and you could see errors in the IDE about not being able to find Node if you don’t have it installed. We will be working on improving this integration in the coming releases.

Features
WWD provides support for dozens of languages and frameworks, like the Quarkus application.properties file discussed above, to SASS, TypeScript and even Angular. For a full list, go to Preferences > Language Servers. Support provided includes Validation, Content Assist, basic refactoring and analysis. There are also launch configuration that allow you to debug against applications running on Firefox, Chrome or the Node runtime.

Miscellaneous Enhancements and Fixes

Our JBoss AS connectors would often double up as JBoss EAP connectors—this release now includes dedicated JBoss EAP connectors for your use. We have also added a Wildfly 20 connector.

The integrated BuildShip tooling has been updated from version 3.1.3 to 3.1.4—a bug preventing Gradle projects from running with Java 14 has also been fixed.

We don’t know about you, but we love font ligatures and with this release, proper Ligature support comes to Windows. Just make sure you specify a ligature-capable font at General > Appearance > Colors and Fonts > Basic > Text Font. Need a recommendation? Try Microsoft’s Cascadia Code.

How many times have you used the new file wizard only to realize you hadn’t created the folder structure yet? Well, you can now specify new folders in the file wizard too!

In the Git Repositories view, a handy Filter Tags action allows you to see only the tags you’re interested in. When cloning a repository, you have the option of cloning from a local bundle file too.

Integrated version of Spring Tools Suite received a minor bump from version 3.9.12 to 3.9.13.

Due to an improper library configuration, the deployment of JAX-WS 2.1 projects could fail under some circumstances – this has been fixed.

Editing XHTML files in a JSF project could lead to several IOOB exceptions being logged – this no longer happens.

Framework Updates

Wizards for Hibernate, JPA and Spring now include newer versions of these frameworks to help you get started. We’ve added Hibernate 5.4, JPA 2.2 (via EclipseLink 2.7 and Hibernate 5.4) and Spring 5.2. Something to note is that these library versions will only be visible in Maven projects, where the wizards will add the corresponding dependencies to your project’s pom.

New Dashboard

Immediately visible in this new version of MyEclipse is our refreshed and simplified Dashboard. We’ve removed pages that were not being used and the dashboard is now a single, focused tab, with a searchable list of wizards, documentation and our collection of examples.

Spring

In addition to Spring 5.2 mentioned earlier, with this release, we’ve updated our integration of Spring Tool Suite from 3.9.7 to 3.9.12. These updates bring some enhancements to Spring Boot support, like the ability to inspect live environment values from a running Spring Boot application, and enhancements to the Beans tab allowing you to introspect bean relationships at runtime. You can find these enhancements in the Properties view for a running application.

STS 4

We realize some of you may want to work with the STS 4 stream of tools. While previous versions of MyEclipse would prevent the installation of STS 4, it can now be installed into MyEclipse without conflicts. We’re continuing to monitor the STS 4 line of tooling for integration into MyEclipse.

Eclipse 2020-03

We’ve updated the base Eclipse build to 2020-03, along with associated projects in the Eclipse release train like DALI and the Web Tools Project. The biggest capability that this update brings is Java 14 support, but there are dozens of other noteworthy improvements as well.

We’ll list a few of our highlights below:

• If you’ve never used the “Quick Access” functionality before – it’s never too late to give it a try, there is now a dedicated button on the toolbar for it, and you’ll find it’s a much faster way of doing a number of things from opening perspectives and views to launching debug sessions.
• Some resource types can be renamed inline in all explorer views.
• You can choose to stop at an exception breakpoint only the first time.
• Expressions view and conditional breakpoints now allow you to use Lambda expressions and method references.
• Content assist now supports subword patterns, making it much easier to find the completion you need.
• Several new quick fixes have been added to the Java editor, like the ability to surround a selection with a try-with-resources block. There is a corresponding “Surround With” context menu item as well.

Key Fixes & Enhancements

• We now have a connector for Wildfly 19.
• In some circumstances a configuration change would cause the workspace selection prompt to stop appearing. This has been fixed.
• Libraries specified on the Classpath tab of a WebSphere launch configuration are now correctly added to the server’s classpath when it is launched.
• While deployed reports worked fine, the in-product report preview was broken in the last version of MyEclipse. We’ve fixed this so you can now preview reports before deployment.
• For those using our Slack code sharing capability, we’ve fixed the authorization flow and this functionality should now be operational again.
• Importing WSDL files into Spring Boot applications will no longer cause the IDE to hang.
• When using our DevStyle dark themes (Darkest Dark and others), some tree controls across the product would fail to render correctly – you can now see all the branches!
• With all our dark themes, we also fixed a resource leak that could result in a “No More Handles” situation on Windows. If you had this theme enabled, and found MyEclipse mysteriously crashing after a day or two of uptime, this is the fix you are looking for.

Server Connectors

WildFly

This release includes connectors for WildFly 17 and 18, so you can develop and deploy applications against these servers.

WebSphere

Bugs in EJB Deploy that required you to start MyEclipse with Java 8 for EJB Deploy functionality have been fixed. We’ve also fixed  an SSL issue that prevented WAS 9.0.5 from being started from within MyEclipse.

Java Enhancements

There are a host of Java enhancements that we think you will benefit from in this release of MyEclipse.

Chain Completion

Our favourite feature is chain completion suggestions for content assist. Chain template support will traverse reachable fields, local variables and methods, to produce a call chain whose return type is compatible with the expected type.

Java Formatter

Getting blank lines to format just right has always been a challenge – well, the Java formatter now has a number of settings that will help you get your code formatted the way you want it. There are a number of other formatting settings that have been added since 2019.04 too.

Other Java enhancements you might find interesting – history for expressions in the variables view, synchronization between standard and error output in the console, and a new, advanced module dependencies tab for the Java Build path.

Quick Search

Search isn’t exciting, but once you see what Quick Search can do, we’re sure you’ll use it all the time. Just press Ctrl/Cmd + Shift + Alt + L to do a content search across all files in your workspace, with a preview showing matched text. You will probably want to change that binding to something less onerous though!

Miscellaneous Fixes

• Matisse continues to remain popular – a bug prevented new Swing components from being properly created using the wizards, this has now been fixed.
• If you tried to run MyEclipse with Java 12 or higher, you’d face issues with licensing and activation – these are now resolved.
• If you used our dark themes, colors in the SQL editors (both code and visual) were hard to read – the colors in these editors are now better suited to the dark theme.
• Recent versions of Windows Defender have been known to aggressively scan Eclipse-based installations, resulting in a significant delay in MyEclipse startup time. There could be further delays when MyEclipse is running as it could start scanning your workspace as well. MyEclipse will automatically suggest the exclusion of key folders from Windows Defender to avoid this problem. For more details, please see this blog post.

Java Enhancements

Java 11

MyEclipse ships with an integrated OpenJDK 11 build, so not only does it run on Java 11, it has full support for Java 11 development as well. There are quick-fixes for dealing with var types, or to easily change your compliance if you want to use Java 11 features. Check this page for more details.

Formatter

For those of you who are particular about how their source code looks, there are several new formatting capabilities, like this enhanced ability for column alignment.

Debug

If you’re debugging a heavily threaded application, you can hide running threads from being shown by using the Java > Show Running Threads toggle in the Debug view’s context menu. This makes it easier to find the thread you’re stopped at.

For more on Java fixes that were picked up, please see the JDT New and Noteworthy for Eclipse 4.9 and 4.10.

Performance Fixes

Maven

We’re aware that the Maven repository index update process that runs on startup can make your startup experience somewhat sluggish, as well as result in a rather large workspace.  We have turned this off by default – you can turn it back on, on the Preferences > Maven page or update the Index manually from the Maven Repositories view.

MyEclipse / Project Explorer

With both the Java Main Sources and Java Test Sources working sets checked, opening files from either of these explorers could result in the UI freezing for upto 30 seconds – this has now been fixed.

Misc

Some of you may have noticed an over-ambitious, “Base URI change job”, running for long periods of time. While not a performance issue itself, it could sometimes lead to the IDE freezing, this will no longer occur.

We’ve also made several changes to some background JavaScript processes to improve the overall performance of MyEclipse.

Server Connectors

We’ve added support for Wildfly 15, 16, and TomEE 8.x.

Additionally, note that servers for which you haven’t specified a custom JDK / JRE, will automatically switch to running with Java 11 with this update. If your server fails to start because it is incompatible with Java 11, please specify a different JRE / JDK in the server configuration page. The server UI will also warn you of known Java-version incompatibilities when you’re configuring a new connector.

WildFly 14

A connector for WildFly 14 has been added to this release, you can now manage the server, deploy, and run/debug your applications with ease.

Maven

The embedded version of Maven would run with the same JDK that MyEclipse was running with, ignoring the Maven JDK preference. Especially with Java 10, this would result in dependencies resolving differently than expected, among other issues.

With this release, we’ve ensured that this preference will be respected – if you need to run the embedded Maven with a different JDK, please go to Preferences > Maven and change the value in the drop-down. Note that only JDKs can be selected here.

Wildfly 11, 12 and 13

We’ve added support for these servers with new server connectors. Java EE 8 support is available with both Wildfly 12 and 13, if you use the ee8.preview.mode=true setting in the server configuration.

A number of minor issues were fixed around compatibility with older versions of WebSphere, specifically versions without fix packs installed.

Java EE 8 Form Editors

Form based editors are now available for Java EE 8 configuration files, like web.xml, application.xml, web-fragment.xml, etc.

Java 10, Java 9 and Java EE 8

Java 10 & Java 9

This release includes support for both Java 9 and 10.  A good example is the support for Java 10’s new var keyword, with intelligent content assist, popups that indicate the actual type, and even quick fixes that allow you to convert to and from var local variable declarations.

Modules, which were introduced in Java 9, are well supported too, you can easily modularize existing projects, customize classpaths on a per-module basis, and again, use handy quick fixes that will take care of module imports, with corresponding additions into your module-info.java file.

MyEclipse also ships with JDK 10, which is used to run the IDE. You will have access to a Java 10 JDK out of the box.

There are dozens of great improvements in the Java space, check these links for more details.

Java EE 8

If you’re raring to get started with Java EE 8, we’ve added support for this version across a number of our Java EE project wizards, from Application Client projects to Web Service projects built with JAX-RS . Creating a Java EE 8 project will add the corresponding API libraries to your project and create corresponding configuration files if so desired.

Java EE 8 projects can be deployed to Glassfish 5, Tomcat 9 and tcServer 4, the last being a new server connector added to this release of MyEclipse.

Note that all new Java EE 8 projects created with MyEclipse will be Maven based. You are free to work with non Maven Java EE 8 projects as well, though you will have to create the project yourself.

Java EE 8 Enhancements Coming Soon

• Form based editors for JAVA EE configuration files like web.xml, application.xml, etc.
• Additional connectors for servers which support Java EE 8, like Payara 5 and Wildfly 13

DevStyle

DevStyle brings “Developer Ergonomics” to MyEclipse, with an enhanced startup experience, additional themes, and an inline search. DevStyle was released on the Eclipse Marketplace about a year ago – since then, it has been significantly enhanced, and we’re happy to make it part of the MyEclipse 2018 release.

Deep Black

Last year, we brought the ultimate Eclipse dark theme, Darkest Dark, to MyEclipse. However, some of our users wanted a theme that went darker still, and so, we bring to you, Deep Black. Enjoy!

Tweaked your theme, and want to share your creation with the world? Use the new short code on the Preferences > DevStyle > Color Themes page.

Enhanced Startup Experience

DevStyle replaces the classic Eclipse startup dialog with an enhanced Startup Experience. Use the Launch page to easily start a recent workspace, or get started with a recent file. You can manage multiple workspaces from the Workspace page.

Inline Search

The Inline Search replaces the traditional Eclipse Find dialog, providing a search experience that is far more efficient and unintrusive – this tool won’t interrupt your development workflow or get lost on your desktop.

Note: Go to Preferences > DevStyle  and Preferences > DevStyle > Inline Search to control the enablement of these features.

Code Mining

With our Code Mining support for Java, instantly see references to fields and methods, and implementations of interfaces or abstract classes, without having to specifically search for these references. You can see these values alongside your code, resulting in a much richer source view. If you need more details, simply click to invoke a detailed search.

Similar support also exists for Git, allowing you to see who made changes in the file you are editing, and when they were made.

We’ll be continuing to enhance our Code Mining support over the next few releases – let us know where you think it would be most beneficial.

Angular & TypeScript

Angular 6

We’ve made changes that keep our tooling compatible with the latest Angular and Angular CLI releases – you can create and deploy Angular 6 projects with this release of MyEclipse. Angular support will see continued and significant improvement in upcoming releases.

TypeScript

The quick fix and content assist capabilities for imports have been enhanced and in case you’ve missed the option, the Open TypeScript Symbol dialog will now list types from *.d.ts files by default. All TypeScript editor keybindings can now be customized on the Keys preference page.

TSLint

TSLint made a change whereby every linting issue was an error by default. If this has overwhelmed you, we now have a setting whereby rule failures will always show as warnings. Change this on the Preferences > Files and Editors > TypeScript > TSLint page

Spring Boot

Use the new Boot Dashboard to manage your boot projects, and use the properties view to analyze locally running boot applications. There are several additional launch options for Spring Boot launches, like a new Fast Startup option. This option, as well several other Spring Boot preferences can now be configured on the Preferences > Frameworks > Spring > Boot page and sub pages.

The new Spring Starter Project wizard has an improved UI, and also allows you to specify custom initializer URLs if you have such services running in-house.

CodeMix

Some of you have heard about CodeMix, or may have already installed it into MyEclipse. For those of you not in the know, Genuitec’s CodeMix plugin brings core VS Code technology to Eclipse, allowing most Code OSS extensions to work in Eclipse too – and CodeMix can be installed into MyEclipse 2018 as well. This gives you an enhanced development experience – from basics like HTML and CSS, to making it easy to work with frameworks like React and Vue.js, or even opening up your IDE for development in Python, PHP, or Go!

To get started with CodeMix in MyEclipse, go to File > New > Other > CodeMix, choose any of the listed wizards and click the link to initiate the install. Alternatively, you can install directly from the Eclipse Marketplace. Best of all, CodeMix is free with your MyEclipse license! In the near future, CodeMix will be a part of the MyEclipse distribution, to give you the best possible experience out of the box.

Read this post or visit the CodeMix Journey for more information.

More Java!

Java Debugging Enhancements

Trigger Points
A breakpoint can be made a trigger point, and all other breakpoints will be skipped until the trigger point is hit.

Return Values
The last method result (per return or throw) that was observed during Step Into, Over or Return, is shown as first line in the Variables view. Similarly, the value that would be returned (or thrown) is also shown when you’ve stopped at the corresponding point in your code. It’s unbelievable how much this small feature enhances your debugging experience.

Launch Groups
While not strictly related to Java or Debugging, launch groups can be used to launch multiple launch configurations sequentially, with configurable actions after launching each member in the group. You can delay subsequent launches or wait for console output for instance, before proceeding to the next launch.

Miscellaneous Java Enhancements

There are literally boatloads of additional enhancements in the Java space, far too many to list here, so we’re highlighting our favorites:

• There is advanced support for the recently released JUnit 5.1 framework, along with a number of enhancements to the JUnit view that make it much easier to use.
• When you paste text into a string literal, it will be automatically escaped.
• An attribute, Contains test sources, can be set for source folders when appropriate. These source folders can be configured to appear differently in the package explorer, and their dependencies can be separately configured and managed.
• An optional New Java Index can make for a much faster Java search experience if enabled, especially in workspaces where there are a large number of JAR dependencies. Turn it on at Preferences > Java.
• Organize imports has a Skip button, allowing you to skip types without cancelling the entire operation.

Angular & TypeScript

Several fixes have been made in the content assist area – bugs around missing types, case sensitivity, and ordering have been fixed, for a much more reliable and robust assisted coding experience.

The Problems / Markers view would report incorrect line numbers when it came to TypeScript validation, this has been addressed.

In localized code, in some cases, users would experience various failures around our Angular support – this has been fixed.

Bugs around the use of quick-fixes for unused imports have been fixed, stay tuned for further enhancements that make dealing with modules easier in future releases.

If you have TypeScript project, but for some reason do not want support from our tooling, the facet can safely be removed from the project’s Project Facets property page.

We also fixed an issue with array handling in the JSON editor.

DevStyle

Inline Search

Several usability fixes have been made to Inline Search – thanks to continued feedback from our users. The dialog will now automatically close to stay out of your way, the find next/previous actions will use the last searched string from the Inline Search, and we’ll reuse your search area when it makes sense to do so. Please keep your requests and suggestions coming.

Themes

If you enjoy the DevStyle themes, both light and dark, but don’t like the new-style scrollbars, add

-Ddevstyle.enable.themedScrollbar=false

to your myeclipse.ini file (in the -vmargs section) to go back to the native bars.

Angular & TypeScript

Angular 5

Yes, Angular v5 is finally here, and we’ve made sure you’re ready to hit the ground running with this version whenever you choose.

If you select version 1.5.0 of the CLI during project creation, an Angular 5 project will be created, and thanks to our support for Angular 5 language services, you will continue to get the entire range of our Angular support, from content assist and validation, to being able to serve and debug applications with ease.

The Angular 5 release has brought with it dozens of changes, several in the performance space. For example, the build optimer is on by default for production builds, resulting in smaller bundles. The Angular compiler has improved support for incremental compilation, along with an integration of a new version of Webpack, which has performance improvements too. An ahead-of-time (AOT) compiler is also available, though that’s currently not on by default.

Another thing to watch out for is that a number of properties deprecated in version 4 have now been removed, so these will show up as errors in your source. At the same time, new elements introduced in Angular 5 will be listed in your content assist proposals and will be correctly validated. For more details on what’s new with Angular v5, please read this article.

TypeScript 2.5

While Angular v5 doesn’t necessarily need TypeScript 2.5, we’ve added support for this version too. You have access to a few new quick fixes and a compiler which will do a better job with handling multiple resolutions of the same file. For more details, please read this article.

We have also added validation for the tsconfig.json file – invalid configurations will now be detected as errors and will show up in the editor and Problems view.

Servers

MyEclipse now includes new server connectors for TomEE 7 and Glassfish 5 – we also support the deployment of Java EE 7 projects to Weblogic 12.2.1 and later versions.

DevStyle

MyEclipse now includes DevStyle, so its advanced theming capabilities and power ups are available to MyEclipse users as well.

Themes

Make your workbench a work of art. DevStyle allows you to define a theme that’s uniquely you! What is your idea of the perfect theme? Light and bright? Dark with pops of color? Fine tune your workbench, even down to specific hues and custom icons that speak to you.

If you didn’t catch it already – yes, we now have awesome looking  light themes too!

Tip: Darkest Dark theme settings in the Preference dialog have been moved from General > Appearance > Darkest Dark to DevStyle > Color Themes.

Inline Search

Find the modal search dialog cumbersome? We’ve replaced this with a very capable inline search – we’re sure you’ll find it far more efficient, and unintrusive, it won’t interrupt your workflow.

Tip: Press Ctrl + F twice to bring up the regular search dialog. You can disable the Inline Search on the Window > Preferences > DevStyle preference page.

Note: The enhanced Startup Experience, that is part of DevStyle for Eclipse, is not available in MyEclipse at this time.

Key Fixes

Theming / Darkest Dark

Core fixes:

• Our themes will now work fine even with the Oomph activated – there were several problems caused by how Oomph managed preferences affected the functioning of our themes. Similarly, our themes will also work better if you have an installation of Eclipse Color Themes.
• Pressing Ctrl + Shift + M in the PHP editor could cause the IDE to hang on exit, this has been fixed.
• Custom HSL settings will now be respected.
• A rare issue, where an error dialog relating to the user of JNIWrapper would display on exiting the IDE, has been fixed.
• Syntax color preferences changes in the Java editor are respected.
• Exceptions will no longer be logged when opening the JavaDoc view

Rendering fixes:

• HiDPI icons would only correctly work in our dark themes, and were N/A in the light themes.
• Configure contents dialog of the Problems / Markers view will now render correctly.
• The expand / collapse control for Tree controls will now be shown at the right position.

Color corrections:

• Table headers in the Tasks view
• QuickDiff in the EGit history view
• JUnit test coverage in Java classes
• Java Call Hierarchy view
• Comment text in Git Staging view

’

Angular & TypeScript

• Several validation issues around the use of ngFor in Angular Templates have been fixed.
• References to properties via shorthand notation is now no longer marked as an error.
• TypeScript code will now be correctly indented on paste.
• The toggle comments action will now correctly toggle single line comments even if the comment was indented.
• Attempting to use the quick fix functionality to implement an interface would sometimes result in the IDE hanging. This has now been fixed.

’

Terminal+

• Command history functionality has been restored for Terminal+ on macOS.
• Terminal+ will work, no matter what your local shell shell on macOS is. Previously there were failures if you had zsh or ksh for instance.
• Running Node / npm processes could sometimes prevent the IDE from gracefully shutting down. This has now been fixed.

’

Core

• An issue where too many connections were opened in some network environments was fixed.
• On macOS High Sierra, the top level application menu is now enabled and works as expected.
• The Enter key on the number pad can also be used to initiate an inline search.
• The “dependencies only” Maven container now works as expected.
• The Run As > Maven Build action will now use the project relative path to the pom.xml as the base directory.
• Importing some older Spring / JPA projects into MyEclipse would result in a ADD_SPRING_JPA_SUPPORT error being shown. This is now fixed.

Angular & TypeScript

• Renaming or moving an HTML or CSS file that’s associated with an Angular component will result in references to these files being correctly updated too.
• TypeScript 2.4 is now fully supported.
• The integrated version of TSLint 5 has been updated to 5.6.0; as always, we will only use this version if you aren’t explicitly using another version within your project.

We’ve made several fixes in this area as well:

• Stopping the Angular server will now ensure the Node process is terminated as well. This ensures you won’t have a port blocking problem when restarting the server – this was an issue on Windows.
• On a Mac Pro, or any other systems with multiple ethernet cards, much of our Angular server tooling was defunct, including status monitoring and debugging. This has now been fixed.
• Several bugs around TypeScript refactoring have been fixed.
• Several issues around synchronization of source code with our internal TypeScript and Angular models have been fixed. We’re continuing to make improvements in this area.
• Using an advanced setting on the TypeScript preference page, you can turn off the automatic detection of TypeScript projects.
• Performance issues around editing large TypeScript files have been fixed.
• An empty baseUrl property in tsconfig files is now correctly handled, fixing related validation issues.
• In a TypeScript project, TSLint will now validate js, jsx and tsx files too.

Miscellaneous Fixes

• Our Eclipse Buildship version has been updated to 2.1.2 to provide better support for building software with Gradle.
• When you import a standalone Maven project, a project migration process will not be triggered.
• An IllegalArgumentException thrown during the initialization of some Spring projects has been fixed.
• If your perspective contained multiple Open TypeScript Symbol buttons in the toolbar, please switch to a new Window, using Window > New Window to get a perspective without these buttons. The problem will not recur.
• The quick diff popup, as well as the XSD editor will now appear with appropriate colors when using the Darkest Dark theme.

Angular & TypeScript

Typescript 2.3
If you’ve been waiting to try the new features in TypeScript 2.3, like Async Generators, or the new for..await..of statements, this release has you covered. We’ve also added support for new flags like –strict.

Open Type
We’ve added the much awaited Open Type functionality to our tooling, which allows you to easily and quickly navigate to any symbol of interest, across your workspace or in specific projects. Use the toolbar button, or Ctrl + Shift + T, to bring up this dialog and tell us what you think!

Miscellaneous Fixes
A couple of issues around hyperlink navigation, validation, as well as being able to use the quick fix from the Markers view have been fixed.

WebSphere Portal Server 9

MyEclipse now includes a connector for WebSphere Portal Server 9. You can now manage this server from within MyEclipse, along with the usual deployment and debug support, of course!

Angular & TypeScript

CLI Support

We now support the creation of projects with the latest stable and beta CLIs, 1.1.0 and 1.2.0 respectively.

Node and NPM

When creating an Angular project, you can now elect to use pre-installed versions of Node and NPM that you may already have installed on your system. Our project wizards will also allow the selection of more recent versions of NPM (was limited to 3.x earlier), though please note that there appear to be problems with NPM 5.x and Angular.

Refactoring

In CI 5, we added inline refactoring as well as the ability to rename files. In this release, we’re extending rename refactoring to handle folders too, as well as adding the ability to move both files and folders – corresponding imports will be automatically updated, of course.

TSLint 5

There were a number of issues in our TSLint 5 support, we’ve added a number of fixes to this release which should provide robust support for this version of TSLint. Through our new properties page, you can now explicitly choose the version of TSLint used to validate your project.

Miscellaneous Key Fixes

• Odd issues with the auto-insertion of braces, a regression in CI 5, have been fixed. We’re continuing to work on other such typing issues.
• In rare cases, with specific environments, creation/serving Angular projects would fail with various “command not found” errors; this has now been fixed.
• Importing projects which have their tsconfig.json file in the project root now works.
• In projects using Angular 2.x and TypeScript 2.2, the false negative, “Pipe signature not found”, has been fixed.

Darkest Dark

Icon color sets come to Darkest Dark with Simply White and Pastel tones allowing you to decide how toolbars and icons look throughout your IDE. We also are making available over 750 more replacement icons thanks to a huge contribution by bettmaeyer, and efforts by Lukasz and others. Finally, a few more editor themes are bundled!

TypeScript

TSLint 5

Working on cutting edge projects which are already using TSLint 5? We’ve got you covered with support for TSLint 5 – including support for severity levels on linting rules. As always, we respect the version of TSLint you’re using in your project.

Refactoring

Inline refactoring
We’ve always had refactoring for TypeScript variables, fields, methods and functions – but you were required to go through a dialog. Now you can now refactor these elements inline!

Note: If you’re working with TypeScript in Angular projects, these rename actions do not yet ripple into Angular templates, but we’re working on adding this to upcoming releases.

File renames
You can also rename TypeScript files and we’ll take care of correcting imports of this file in other TypeScript source. Again, Angular intelligence is coming soon.

Refactoring preview
Whether you rename TypeScript identifier, or a file, you can now examine the results of refactoring before applying them to your code.

Path Content Assist for Imports

We will provide you with content assist in import statements making it easy to find and import the file or library you need.

Miscellaneous Fixes

A big thank you to users who have been sending in feature requests, diligently reporting issues, and providing test cases and examples, helping us improve our TypeScript support as well as fix several bugs. We will be continuing to focus on fixes in core areas over the coming releases.

The following key issues have been addressed in this release:

• Added smart caret positioning.
• Quick fix added for “new line at end of file”.
• The Pipe (|) in TypeScript 2.2 source will no longer be reported as an error when correctly used.
• TSLint can now load custom rules.
• Several performance issues have been fixed for a smoother coding experience.
• When keying in imports manually, you may have encountered an error logged or displayed – this annoyance has now been fixed.
• Problems with automatic importing of classes from typings definition files have been fixed.

Angular

Simplified Perspective

We’ve toned down the “busyness” of the Angular perspective, for a much cleaner and focused coding experience.

Custom Arguments

We’ve added a feature to provide custom arguments to the Chrome process when launching the Angular application.

Angular 4 Support

Hot on the heels of the Angular 4 release, we’re proud to announce that our Angular 4 support has arrived.

Upgrade Assist
If you want to upgrade to Angular 4, select your Angular 2 project and click on the Upgrade action in our toolbar. Our upgrade wizard will upgrade a whole lot of configuration files, as well as fix some of your code, if necessary. At the end of the process, we’ll give you a set of manual steps that you may need to take to complete the process.

Even outside the automated upgrade process, you can use several new quick fixes to update your TypeScript classes and Angular templates, piecemeal, to Angular 4 standards.

Note: Due to some Eclipse limitations, some of these quick fixes are only currently accessible from the Markers view.

Documentation

Documentation rendering has been vastly improved, we’re capable of handling both JSdoc as well as Markdown based documentation, which will be displayed when you hover over relevant elements. This also applies to documentation that’s shown for content assist proposals.

Inline Templates

Support for inline Angular templates has been improved, we’ve added content assist support, as well as all the documentation updates listed above.

TypeScript 2.2

This version adds initial support for TypeScript 2.2. If you are working with this version of TypeScript, new quick fixes will become available, like fixes for unused variables, unimplemented abstract methods, etc.

We’re continuing to work on our TypeScript 2.2 support, with support for TypeScript plugins coming soon.

Darkest Dark

Now it’s simple to customize your editor colors when using the Darkest Dark theme. Simply go to Preferences>General>Appearance>Darkest Dark and select the editor colors you prefer.

Angular Enhancements

• Angular support has been upgraded to fully support more recent versions of Angular, like version 2.4.x.
• We now support the newer Angular CLI package, @angular/cli. The older, angular-cli package is supported too.
• Validation and content assist have been improved.
• HTML templates can be referenced using ES6 shorthand.
• Hyperlink navigation is now supported in HTML templates, allowing you to easily navigate to other parts of the template, and even other TypeScript files.

Darkest Dark Theme

Our new Darkest Dark theme delivers a fully dark UI with icons designed specifically for a dark theme. To use the Darkest Dark theme, simply select it from Preferences>General>Appearance. The Darkest Dark theme defaults to our own Darkest Dark color theme, but you can use the Eclipse Color Theme to tailor the editor colors or select from a number of other popular themes.

CodeLive for Angular

CodeLive now includes support for Angular. CodeLive can be enabled per project from the Angular CLI Server in the Servers view. With CodeLive you can jump to your source code in the editor directly from the browser. Display the CodeLive Dashboard  to view all active Angular components on the web page. When you hover over a component, an icon displays to the right of the component for each type of corresponding file: TypeScript , HTML template  and CSS . Click the file you wish to view. 

In addition, you can use the Inspector  to view specific components on the web page. Hover over a component on the page to view the component name. Click the component to view the dashboard list filtered for the selected component, and then select the file you wish to view.

TypeScript Enhancements

TypeScript 2.1

We now fully support projects which use TypeScript 2.1 – including new types, constructs, and support for tslib. With configuration inheritance, you can split your configuration across several files, making it much easier to develop against multiple targets.

TypeScript Editor

On-Save actions will now execute automatically when you save a TypeScript file. The actions currently available allow you to automatically format your document, correct whitespace issues and remove unused imports when your file is saved. These actions can be configured globally, as well as at a per-project level.

Editor features like occurrence highlighting, word wrap, block edit and whitespace display can be controlled from the toolbar.

TSLint 4

With this release, we’ve upgraded our TSLint support to support both TSLint 3 and 4. If you have TSLint installed in your project, we will use that version to ensure expected, consistent linting behavior. If you don’t have TSLint installed, we will automatically use TSLint 4.3, giving you access to a number of new linting rules and capabilities.

Of course, users who experienced issues with projects using this version of TSLint will no longer experience any problems.

Eclipse Neon

This release is based on Eclipse Neon 1 (4.6.1), and benefits from new Neon capabilities like improved startup performance, visual enhancements which include a full screen mode and better support for High DPI displays, and editors with word-wrap (Alt + Shift + Y) and the ability to auto-save your files!

As usual with every major, we’ve also refreshed integrations and updated to newer versions of third party tooling on which MyEclipse is built, like m2e, BIRT, Webtools, eGit, STS, etc.

Angular 2 Support

Angular 2 Quickstart—A key capability of our Angular support, especially for beginners, is that there are virtually no prerequisites — we’ll download everything from Node to the Angular CLI for you, automatically. So if you were concerned about getting your environment set up right and downloading dependencies in advance, don’t bother! While our wizards will suggest recommended defaults, you are free to choose other versions of Node, NPM, or the Angular CLI. You can start with a basic project or a template based on the popular SB Admin theme.

Angular 2 HTML Template Intelligence—When you’re developing Angular 2 applications, you need an IDE that can support you when you’re developing templates. Our tooling provides Angular 2 validation, so that you’ll know if you’ve mistyped an Angular element or attribute, or called a non-existent method. Our auto-complete support will provide suggestions for Angular tags, attributes and even expressions. Within expressions, we support the Angular Template syntax, so expect to see content assist for variables, methods, fields, functions, etc., from your referenced components.

Angular CLI Integration—Our tooling is built on top of the Angular CLI, for servicing Angular 2 applications, and includes best-practices compliant generation of services, components and more. An enhanced terminal ensures paths and environment are ready for rapid development.

• Seamless launching of ng serve from the IDE
• Display of server build problems alongside the code
• Automatic detection of external ng serve invocations
• Generate services and components from wizards

Angular 2 Deployment & Debugging—To deploy your application for testing, simply bring up the context menu on the project and choose Run As > Server for Angular CLI Project. Alternatively, you can open the Servers view and find your project under the Angular CLI node, from where you can easily start and stop deployment, or even start a debugging session. Not only is your application being served for local testing in a browser, a LiveReload server is also started. With LiveReload, any time you change a source file and save it, the application is rebuilt, the deployment is updated and the browser page, if you have it opened, is automatically refreshed as well.

To debug, you can use the Servers view or the Debug As > Server for Angular CLI Project context menu item. You can place breakpoints in HTML, JavaScript and TypeScript files too — our debugger will allow you to step through the original TypeScript source during a live debugging session.

Improved TypeScript Support

Import Support for TypeScript Symbols—One of the biggest pain points when working with TypeScript, is having to manually import classes, interfaces, namespaces, functions, … in short, any type of TypeScript symbol into your source file. Well, we have good news for you! Content assist suggestions will include symbol suggestions too, and when selected, not only will we complete the name for you, but we’ll also import it.

Beyond this, we also have quick fix support, so invoking a quick fix on an undefined identifier will result in the symbol being correctly imported into your source.

Content Assist Improvements—If you’ve gotten tired of typing this. for every field/method when coding, just initiate content assist. Not only are the proposals better sorted than before, it will also list fields and methods too (without you having to type this. first), and will insert the this. bit automatically on completion.

Since we write a fair bit of TypeScript internally, we’ve been “dogfooding” these features and our productivity has increased significantly – we’re sure your experience will be similar.

TSLint Integration—TSLint is an extensible linter for TypeScript. While our existing TypeScript validator will already find syntax errors in your code, TSLint checks your code for readability, maintainability, and functionality errors – allowing you to fix them before running into them in production, at runtime.

So, how does our integration work? For Angular projects, a tslint.json is created in your project’s root folder; we use the settings in this configuration file when linting your project. Issues noticed are marked as warnings in the editor’s ruler area and in the Problems view. This ensures your Angular project conforms to NG best practices.

A key feature is our quick fix support – you can fix the problem automatically, remove the linting rule if you don’t like it, or simply turn off linting for the entire project. The number of quick fixes available right now are limited, but we’re working on adding more to the tooling soon.

TSLint can catch a number of potential problems – from style issues like whitespace and indentation, to functionality issues like duplicate variables, unused expressions or variables used before they are declared. For a more complete list, please see: https://palantir.github.io/tslint/rules/.

We’re also working on adding better support for the tslint.json file, so it’s easy to get to the linting settings you really want for your team.

TypeScript 2.0—With this release, we fully support TypeScript 2.0, along with all the newer properties like types, typeRoots, lib, and the different ways in which TypeScript files can be added to your project’s source. We’ve also added in a few templates to making coding more efficient.

Our fundamental TypeScript support remains rock solid, with support for as-you-type validation, auto-completion, hyper-link navigation — even to Angular 2 templates, and full, bi-directional support for settings configured in the tsconfig.json file.

Enhanced Local Terminal

The Terminal+ gives you a bash based local shell, even on Windows! It has in-built support for NPM, Node and Git, along with special smarts when you’re working with the Angular CLI.

The terminal is project context aware, so when you switch projects, the view will automatically update its open tabs to match the state you were last in, when working with the selected project. It will also set up your shell environment to the use the versions of Node and NPM specified on the project’s CLI Tool Management property page – even downloading those versions if you don’t already have them. This ensures that you and your teammates can work in the same environment.

Embedded Tomcat Server

The embedded Tomcat server has been upgraded from version 7.0 to 8.5, finally giving you a server on which you can deploy Java EE 7 web applications out of the box. If your projects were using the 7.0 runtime, our migration wizard will help you move to the 8.5 runtime in 2017.

Gradle Integration

We’ve integrated the Gradle tooling from the Eclipse Buildship project. This gives you the ability to create Gradle projects, an editor for Gradle files, and the ability to execute and monitor Gradle tasks. MyEclipse currently makes no modifications to this tooling, but do let us know how we can enhance your Gradle experience, especially when dealing with Java EE development.

TypeScript Fixes & Enhancements

• TypeScript source scopes are now dynamically handled according to rules used by TypeScript compiler. This results in correct validation of imports and types, and accurate content assist based on the “files”/”excludes” properties in tsconfig.json.
• Large performance improvements in all areas of the tooling – faster editor startup, source validation, file compilation, and lower memory usage.
• A bug where referenced non-TypeScript projects could cause TypeScript functionality to break has been fixed.
• Can place breakpoints in TypeScript files for debugging with JSjet.

TypeScript

TypeScript is a typed superset of JavaScript that compiles to plain JavaScript—if you love JavaScript but have a hard time dealing with its loosely typed nature, TypeScript is the answer!

TypeScript support in MyEclipse includes a TypeScript editor, along with robust content assist, validation and code navigation capabilities. TypeScript code is intelligently transpiled to JavaScript when necessary, and all features are customizable, from validation to syntax coloring in the editor.

For those of you already using TypeScript, you’ll be happy to know that our support is centered around the tsconfig.json file—our TypeScript tooling will load and store values to this file, so that it will respect settings you may already have, without needing to configure them again in the IDE. Conversely, changes you make in MyEclipse will be accessible on the command line and in other environments as well.

For more details on our TypeScript support, please read this document.

WebSphere 9

Our new WebSphere 9 connector brings you the same robust WebSphere support you’ve grown to expect from the MyEclipse WebSphere connector family. As always, you can start and stop the server from within the IDE. Additionally, MyEclipse will detect external launches and update the server status accordingly, allowing you to perform operations on a server that is already running. The fast in-workspace deployment mode is available as well.

Beyond basic functionality, we also support JAX-WS/RPC web service generation, remote connections, Application Client and Java Connector projects for this server too.

DevSearch

Tired of jumping to an external browser each time you run into a problem? Use the new DevSearch view for a less disruptive search experience.

Key in your query into the view, or use the context menu action to run queries directly from other views and editors. DevSearch will search the Eclipse help system, StackOverflow and GitHub in the background, and bring up results in the view when available.

CodeLive's Magic Wand

Lose your way in a project with dozens or hundreds of HTML files? Enable the Magic Wand in the CodeLive dashboard and it will show you the path to the source file in your MyEclipse workspace! It gets better – “Want to go to there”? Just click that element to open the source file in MyEclipse with the source corresponding to that element selected.

JSJet - Linting and Validation

Interested in achieving high levels of JavaScript code quality? If so, using a JavaScript linter is essential, and you may already be using one. While we did support Linters with the first release of JSjet, this release makes the feature more robust, accessible and easier to use.

Choose from linters like JSHint, ESLint or JSCS – use the default linting settings, customize them within the IDE or use an external configuration file; JSjet is smart at picking those up automatically too.

We’ve also added the ability to customize JavaScript validation with a few validation settings.

Tomcat 9

Tomcat 9 is still in beta, but we have a connector ready in case you want to get a head-start with this server.

Live Preview with CodeLive

This release of MyEclipse introduces CodeLive. Live Preview is the first feature included in CodeLive, with additional features coming in future releases.

To use Live Preview, you will now need to turn on CodeLive per server, and then select the files you want to use CodeLive. The first time you view you web project in a browser, you can select the files that will utilize CodeLive. This change in Live Preview optimizes performance by injecting only the necessary files. More Information

Bootstrap Your App Development with Templates

If you ever wanted to quickly get started with a great looking UI for your web application, but didn’t know how to get started—we can now help with our new template support!

Select a template from the Template tab in the dashboard and simply follow the wizard to get a Java EE application, bootstrapped with the chosen template. You can then easily customize the template as per your requirements.

While the current set of templates are based on the Bootstrap framework and produce Java EE applications, as we add support for additional web frameworks and project types to MyEclipse, we’ll be expanding our template support accordingly. Beyond Bootstrap, we could have Angular or React templates (for example) and in addition to Java EE projects, we could support Node.js, PHP, Static Web projects, etc.

Do give our template support a spin and tell us what you think!

All-Around JSjet Improvements for Better JavaScript Support

This release brings with it a host of fixes and improvements to our JavaScript support with JSjet.

• JavaScript search now works—detailed searches for methods, fields, types, etc., are possible. You can also limit the results to read/write accesses, or declarations only, for instance.
• You can now format just selected blocks of JavaScript code as opposed to only being able to format the entire file.
• Several fixes have been made to the code Outline and Quick Outline views. The Outline view will follow you as you code and it is now easier to navigate with the Quick Outline.
• Fixes in the Call Hierarchy view to better handle some advanced JavaScript code were made.
• JSDebugger—Source maps will now work when debugging a Node.js 6.x application.

Terminal, Snippets View, and Docker Commands

Having a hard time remembering complex CLI commands? The Snippets view and the Terminal have both been enhanced to allow snippets representing commands to be dragged and dropped into the terminal for immediate execution or quick editing. You can even DnD commands from a text file!

If you’re a Docker user, you’ll like the set of Docker commands that we’ve added to the Snippets view.

JSjet

Syntax Highlighting

Tired of how dull a rich, dynamic language like JavaScript looks in Eclipse? JSjet significantly improves the syntax highlighting in JavaScript code, vastly improving readability.

Call and Type Hierarchies

The Call Hierarchy view enables you to easily visualize the flow of your code by viewing all calls to and from a selected function. JSjet takes this handy view a step further by allowing you to view hierarchies for methods, fields and variables.

Another invaluable view is the Type Hierarchy. JSjet provides strong support for type hierarchies. This view will likely become a favorite if you are taking advantage of the new classes capability in ES6.

ES6 Support

JSjet is ECMAScript 6 aware, so all JavaScript features, ranging from fundamentals like syntax highlighting and code folding, to features like the call/type hierarchies, and the formatter work correctly, even when dealing with ES6 code.

Besides these, JSjet includes a faster and more accurate validator, a more complete and detailed outline, better occurrences highlighting and navigation, and a source formatter that doesn’t balk at ES6 code. A few JavaScript linters like JSHint and ESLint are available too! For more details, please see this page.

JSjet thanks Eclipse for providing a superb IDE to build on top of. In addition, a special shout out to Angelo Zerr and the Tern community for some awesome building blocks.

Slack for Eclipse

Slack for Eclipse is now using the OAuth flow and no longer requires you to get a token from Slack before using the feature. Now you simply need to give Slack for Eclipse permission to access your Slack account. You are prompted for authorization the first time you share code with Slack or you can give permission at any time from Windows>Preferences>MyEclipse>Slack for Eclipse. All you have to do is click Add to Slack and you are ready to start sharing code with your teammates!

The following commands are now available in Slack when you use Slack for Eclipse:
/code-open filename [lines] [locator-id]—Open files in Eclipse directly from Slack (e.g., /code-open MyClass.java 5-10 5zO+3Q)
/code-invite—Tell others on the current channel about using Slack for Eclipse

Live Preview

The Live Preview technology has been fundamentally improved, resulting in significantly faster deployment times when enabled. In CI 1, some deployments would take too long to complete when Live Preview was enabled, this has now been fixed.
We now also support live editing of files over HTTPS.

Remote Node Debugging

Have an externally deployed Node application that you would like to debug? Use the new Node.js/V8 connector under the Remote Javascript debug configuration to debug against this instance. If you have the same files that are being deployed to Node.js in your workspace, the debugger will automatically pick up these files as source.

Live Preview

You can instantly view changes to your HTML and CSS within your normal JavaEE development workflow—no browser plugin or active debug session required.  Plus, you can view these changes in multiple browsers and simulated mobile devices simultaneously. Maybe you use JSP to create dynamic web content. With the first release of Live Preview, JSP support is included as an experimental preview feature and limited to static blocks. Further enhancements will be included in future CI releases.

Remote WebSphere Connectors

Ever want to work with a WebSphere server that is not on your development machine? With our refreshed Remote WebSphere support, you now can. You can set up the connector in a way that is similar to a local WebSphere connector, but deploy to a remotely hosted server instead. You can even debug and hot-sync code against this remote instance, as you would with any local WebSphere installation.

Please see this doc for more details on Remote WebSphere support.

Note: For older users of MyEclipse, the Remote WebSphere support was last present in MyEclipse 2014 and has been re-written for MyEclipse 2016 to be more robust, capable, and work seamlessly with your Java EE development processes in the IDE.

JavaScript Debugging: Source Maps

The JavaScript debugger now supports source maps, so you can step through and debug against your original source during a debug session, even though, at runtime, your application is using transpiled or minified source, or source that is modified in some other way. For instance, you can now place breakpoints and step through .ts (TypeScript) or .coffee (CoffeeScript) files too!

Source map support is automatic and does not need to be explicitly enabled. Our JavaScript debugger loads the maps in your runtime scripts and uses them to reference the original source from your workspace if possible; if not, you can still debug against the uncompressed source that is present in the map itself.

For the best experience with source maps, please ensure that you build your project with the right source map related flags. For more details, please read this doc.

JavaScript Debugging: Hot-Swap

Need to modify your JavaScript in the middle of debugging session? No problem – once you modify and save your changes, the JavaScript debugger picks up these changes and you can continue debugging against the modified code, without needing to restart the debugging session. Hot-swap is only available for Web Application debugging where it is turned on by default. It is not currently available for Node debug sessions.

Hibernate 5.1

Hibernate 5.1 may only be a month old, but we’ve added support for Hibernate 5.1 projects in MyEclipse. Hibernate 5.1 can be used in standalone Java applications, Java EE applications or even as a JPA 2.1 provider. We’ve included libraries for new Hibernate capabilities like Hibernate Search as well.

CSS 3

It’s now easy to set the CSS spec level for your workspace using the CSS Source preference page. This preference can be overridden at the project level too – MyEclipse 2016 uses CSS 3 as the default CSS specification level.

We’ve also updated the CSS 3 property and keyword definitions to give you more complete and up-to-date content assist.

Eclipse Mars

MyEclipse is now built on Eclipse Mars 1 (4.5.1). Beyond upgrading the base version of Eclipse, we’ve also refreshed integrations and updated to new versions of third party tooling that MyEclipse is built on, such as STS, m2e, BIRT, Webtools, eGit, etc.

The Mars integration brings in hardcore Java enhancements like improved compiler performance and better support for Lambda expressions, a better looking UI with support for today’s high resolution displays, and several performance and usability fixes across the board.

Command-line Terminal

If you’ve ever wanted to jump to the command-line but find leaving MyEclipse disruptive, you’ll be happy with our new integrated command-line support. MyEclipse now includes the TM Terminal plugin, which supports both local consoles as well as remote shells. 

Press Ctrl+Alt+T to open a local command prompt. Previous sessions are remembered and automatically reconnect on restart.

Miscellaneous Key Fixes

• For PhoneGap 5.3, local PhoneGap release builds will now work.
• Errors with Application Id validation in the PhoneGap editor have been fixed.
• Emmet version updated to latest release, version 1.3.

Wildfly 10

MyEclipse now includes a connector for Wildfly 10. You can now manage this server from within MyEclipse along with the usual debug and deployment support, of course!

Phonegap 5.3

While we are still embedding PhoneGap 3.6.3, we’ve fixed issues reported building PhoneGap 5.3 applications. You can now build apps using this version of PhoneGap for both iOS and Android.

Note: Local release builds for PhoneGap 5.3 on Android currently fail with signing issues, we are looking into this problem. There is also more work to be done in completing 5.3 support, which will come in a future release.

Server Import / Export

You can now import / export servers configurations from MyEclipse 2015, a capability that was missing until now. You can also import server configurations from 2014 and earlier versions, of course.

Breadcrumb Navigation

The Breadcrumb toolbar allows you to quickly navigate through your workspace and open files for editing. The crumb trail that led to the current file in the source editor displays in the Breadcrumb toolbar. Click on any crumb in the trail to navigate to a different resource in your project.

JavaScript Debug Hover Improvements

Hover behavior during JavaScript debugging has been improved – the hover will now evaluate expressions, and the object being examined will also be highlighted in the source editor.

Slack Integration

Webclipse now integrates with Slack.  Simply register a Slack token and then you are ready to send and receive code snippets. You can even view shared code directly in Eclipse without needing to access Slack to view the code.

Gerrit Workflow

If you use Gerrit for code review and repository management for Git, you’ll be excited to see the process streamlined with our Gerrit Workflow. Now, it’s a breeze to instantly fetch changes and switch between multiple feature and stable branches. Plus, you’ll ensure a high quality of code and test against regressions before submitting code to stable branches.

JavaScript

We’ve integrated the latest version of Tern Java with this release, bringing a number of enhancements to our JavaScript capabilities.

Support for existing JavaScript frameworks has been improved, with support for new frameworks added.

Content assist continues to improve with support for multiple types in assist proposals; you will also see framework icons in your content assist proposals, making it much easier to use.

The JavaScript source tab’s (Project Properties > MyEclipse > JavaScript Resources) include/exclude rules now support bash-like regular expressions through minimatch, if you ever need that much flexibility. The same expression support is now being used in several popular JavaScript frameworks.

Finally, on our road to ES6 support, content assist for Promises has been improved with better then value completion. Improved ES6 support is coming soon.

JavaScript Debugging - Externally Deployed Debugging Support

If you ever wanted to debug an application that has already been deployed, or step through some code in a website online, the new externally deployed debugging support now allows this. JavaScript debugging is no longer limited to Java EE applications.

If you have source in your workspace you’d like to debug against, simply bring up the context menu on an HTML file and choose Debug As > JavaScript in Externally Deployed Web Application.

If you want to debug a website, simply create a new JavaScript debugging launch configuration with Externally Deployed as the type.

In addition, we now have better handling for sites with invalid SSL certificates.

REST Explorer Displays MIME Types

The REST Explorer now indicates both input and output MIME types for your endpoints within the view itself; you no longer need to browse the source to figure this out. Also, the REST Explorer can now handle multiple JAX-RS methods at the same resource path, this condition is no longer interpreted as an error.

Additional REST Inspect Fixes

• When you select an endpoint and click Open in REST Inspect, that endpoint is made visible in the endpoints section of REST Inspect.
• In Windows, the REST Inspect window gains focus when brought to the foreground.

New Server Connectors

• MyEclipse now includes connectors for Jetty 8, Jetty 9, Payara 4 and Wildfly 9! Deploy and debug against these servers with ease.

WebSphere

You can now launch jython and JACL admin scripts from within MyEclipse using a launch configuration. 

WebSphere server state detection (stopped, starting, started, etc.) is now more robust; several bugs around incorrect state detection have been fixed.

In the in-workspace deployment mode, dependencies to web fragments, specified via Maven, were not being deployed; this has been fixed.

The JAX-RPC and JAX-WS web service client generation process can now optionally generate a proxy class.

Miscellaneous Key Fixes

• A regression in CI 14, where merged deployment would cause dependent projects to always be JARed, even when exploded deployment was specified, has been fixed.
• Content assist proposals for attributes of JSF 2 composite components are now displayed.
• For Glassfish versions 3 and later, the Open in Browser action now allows you to open deployed web applications directly in a browser.
• On OS X, an instability caused by certain scripts that run in the MyEclipse Web Browser, on closing, has been fixed.
• A Matisse focus jumping issue has been fixed.

JavaScript Debugging

With MyEclipse CI 14, you can now debug both modern Web applications and Node.js applications!

Node.js support allows you to debug against Node versions 0.10, 0.11 and 0.12, and all Java EE versions are supported, naturally.

Our launching shortcuts make it easy to initiate debugging and all Eclipse debugging features like Conditional breakpoints, Hit counters, Expressions view, etc., are available. Familiar commands such as Step Into, Drop to Frame and Skip All Breakpoints allow you to effectively control the debug process.

Existing users of MyEclipse will be happy to learn that our new JavaScript debugger now works on all platforms and architectures – yes, including the oft requested Windows 64-bit OS.

REST Features

The new REST Inspect application allows you to discover, create and test endpoints. You can also save endpoints with different parameters to be used as test data for you and your team.  Another way to benefit from REST Inspect is to use it as a “sandbox” to test remote web services included in your project.

The improved REST Explorer view now has a much more intuitive display of endpoints and is deployment aware as well. This view works with REST Inspect, allowing you to explore the endpoint further in REST Inspect or execute previously tested services directly from within MyEclipse.

We’ve also added a new editor for RAML files with validation support. A structured outline is provided for easy navigation, and both REST Inspect and the REST Explorer are RAML aware.

Minimap Provides Source File Overview

When you’re working with a large amount of code, the Minimap makes it easy to navigate through your source. Most developers have a “mental map” of how their code is formatted. This new view shows you the bigger picture at a glance and allows a quick jump to the section you need.  The Minimap works for all source editors including Java, JavaScript, HTML, etc.

Tomcat Server Connector Fixes

A number of fixes were made to the Tomcat server connector to make both auto-deployment and context deployment robust and more intuitive. Several issues around the storage of configuration files in the workspace and  changes to the server working directory were fixed.

Additional Connection Protocol for WebSphere

In addition to IPC, SOAP is now available as a connection protocol for all WAS servers.

Several issues have been fixed with the in-workspace deployment mode.

Context Root Added to Deployment Assembly Properties

The deployment page has been reworked for Web projects to handle the context root setting. This puts all Web project related settings like the WebRoot folder, context root and the archive name on a single Properties page.

Improved Performance of the PhoneGap Plugin Wizard

The PhoneGap plugin wizard has been reworked so that it is immediately usable on invocation (prior to this fix, the wizard could take a few minutes to be usable). The list now shows a fixed number of plugins based on your filtering criteria.

JavaScript Performance Improvements

JavaScript in CI 12 is more efficient than prior versions of MyEclipse 2015. We’ve improved the performance of our JavaScript analysis out of the box. If you have a very large project, it should not affect the overall performance of MyEclipse like prior versions of 2015.

In addition, you can play with a performance/quality setting or set a scope for the JavaScript analysis to improve performance further. Finally, if you don’t care for these features, you can simply turn it all off. These settings are available both globally and at a per project level (See Window>Preferences>MyEclipse>JavaScript>Performance).

Given the large number of false negatives in the JavaScript validator, we decided that developers are better served by disabling the JavaScript validator at a global level. You can enable it at Window>Preferences>MyEclipse>Validation  – turn on the Client-side JavaScript Validator. You can also control this setting at the project level to turn it on/off for individual projects. The MyEclipse team is working on improving the JavaScript validation experience.

Emmet Integration

Do you find yourself working with a lot of HTML? Maybe CSS or XML? It can often be tiresome to type in loads of markup or simply make the edits you need easily and quickly, especially when dealing with a large amount of content. This is where Emmet comes in!

Unlike regular snippet functionality, with Emmet you can type CSS-like expressions which are dynamically parsed and then expanded immediately into well formed markup, saving you loads of typing.

For example, in an HTML file, if you type: nav>ul>li and press Ctrl + Alt + Enter, you will get

<nav>
   <ul>
     <li>
     </li>
   </ul>
</nav>

A more complicated example, ul>li.item$*5 will result in

<ul>
   <li class="item1"></li>
   <li class="item2"></li>
   <li class="item3"></li>
   <li class="item4"></li>
   <li class="item5"></li>
</ul>

Now, a couple of CSS examples:

bd:n expands to border: none;

ff:v expands to font-family: Verdana, Geneva, sans-serif;

There are literally hundreds of additional abbreviations – in MyEclipse, bring up the context menu in a supported file and choose Emmet>Emmet Cheat Sheet for a list. Also, there are dozens of useful keyboard shortcuts and everything is customizable, of course. If you don’t like Ctrl + Alt + Enter, you could switch to any other key combination (perhaps the Tab key?) by editing the key bindings in Window>Preferences>General Keys.

Beyond code expansion, Emmet also helps with code navigation and selections too. Emmet works in (X)HTML, CSS, XML, XSL and JSP files. It will even give you CSS specific expansions in the CSS sections in HTML files or HTML support at appropriate locations in JSP files.

See the MyEclipse HTML Editor doc for a quick demo.

A big hat tip to Sergey Chikuyonok for his fantastic work on both Emmet and Emmet-Eclipse. For tech folk out there, the version of Emmet we’re using internally is 1.2.2.

Icon Preview of Images

If you work with images, you’ll find the new icon preview really handy. Instead of seeing the boring, standard icon for images, we now render an icon sized version of your image right in the explorer tree.

Note: To keep things efficient, we only render thumbnails for images that are 100KB or smaller in size. Images larger than that typically have dimensions that reduce the utility of the 16×16 scaled down versions.

A hat-tip, again, to Jeeyul for his pde-tools plugins from which we bring you this functionality.

Integrated Version of Tern Java 0.8.0

This latest integration of Tern adds the following enhancements to JavaScript coding:

Completion Guess Support
When a content assist proposal is applied, a second set of proposals will automatically display probable matches based on the type of the function parameter.  Learn more about Guess Support.

Completion String Support
This feature gathers short strings in your code, and string completion suggestions include previously seen strings. Learn more about String Support.

ECMAScript 6
Switch to ECMAScript 6  for Promise support.

RequireJS Object Literal Completion
For the RequireJS config object, applying completion generates a property key/value pair.

Additional Frameworks
We have also added support for a couple of additional frameworks like Jasmine, Protractor, and snabbit.js.

To enable these additional features, open the project properties, expand MyEclipse, and select JavaScript Resources. Select the features you want to use. You can also change the defaults for new projects by selecting Window>Preferences, expanding MyEclipse>JavaScript>Tern>Development, and selecting Repository.

As always, a shout out to Angelo Zerr and the Tern JS/Java community for their continued work in this area.

PhoneGap Ionic Templates

When creating PhoneGap mobile application projects, you have more template options to choose from. Ionic templates give you a starting point for your Ionic UI design. The templates are available from the PhoneGap Application Project wizard.

Ionic Palette in the Visual HTML Designer

The Visual HTML Designer now has an Ionic palette and corresponding wizards that make it easy to add Ionic widgets to your pages – big hat tip to JBoss Tools.

Improved Dark Theme

We know many developers prefer a dark theme when coding. We made improvements to the look of our dark theme so it’s easier on the eyes. Access the new MyEclipse Dark Theme from the General>Appearance preferences. Or, access from the  icon on the main toolbar.

Permissions Settings in the PhoneGap Config

When configuring your Android projects for builds, you can now easily specify required Android permissions in the config.xml file. This is especially helpful if you are migrating your HTML5 application projects to PhoneGap application projects.

Additional PhoneGap improvements include:

• Java KeyStore files are now supported for signing Android builds.
• When adding a plug-in, both the version and the source are now saved in the config.xml file to ensure the same plugin is used for both local and remote builds.
• Paths to icons and splash screens in config.xml are now validated. We let you know if you’re pointing to missing resources.
• Remote debugging can now be enabled either during project creation or from the config.xml editor.

Update to MyEclipse Reports

MyEclipse Reports is now based on the latest stable version of BIRT – 4.4.1. It is the automatic MyEclipse Report Web Runtime version when you create a reporting project.

Intelligent Merged Deployment

MyEclipse intelligently detects whether merged deployment can be enabled for your web project’s modules. In 2015 CI 9, you can now turn merged deployment on or off for each module as opposed to having to make the decision at the Web project level.

PhoneGap 3.6

PhoneGap projects created with CI 8 will automatically use PhoneGap 3.6 out of the box; with support for both local and remote builds.You can still use the earlier version of PhoneGap we have included, of course – or install the version of your choice externally.

The PhoneGap config.xml editor has also been improved with better support for images; the source pane will provide both content assist and validation for the widget and gap namespaces, making editing these files a breeze.

Finalizing Our Application Server Support for 2015

Much work has been done to improve application server and deployment support over the course of the MyEclipse CI stream this year. MyEclipse CI 8 continues with more enhancements in this area.

Pivotal tc Server 3.0 Support
You can now deploy to and debug against the Pivotal tc Server 3.0.

Deployment Mode Flexibility for Tomcat App Servers
Some users on the CI stream had problems with the Tomcat connector’s new deployment mode in 2015. With CI 8, we’ve re-introduced the deployment mode used by MyEclipse 2014 and earlier versions.

With the “auto deployment” option, MyEclipse publishes the project to the auto deploy folder where Tomcat’s auto-deployment mechanism will detect and deploy it. This is the deployment mode used by MyEclipse 2014 and earlier versions.

If you use the “context deployment” option, MyEclipse publishes the project to the specified deploy path and adds the corresponding context entry to Tomcat’s configuration file. This is the deployment mode used by the Eclipse JEE distribution; it had been the only deployment option in MyEclipse 2015, until this release.

Custom Deployment Server
You can now set up a connector to an app server that you control outside of MyEclipse using external tooling or the server’s own shortcuts. Once configured, you can deploy MyEclipse resources to the custom server just as with other servers configured in MyEclipse.

Module Deployment to WAS
MyEclipse CI 8 restores the ability to deploy EJB and Web modules directly to WebSphere without needing to wrap them in an EAR manually.

New PhoneGap Configuration Editor

The PhoneGap configuration editor is now a form-based editor that makes setting up for PhoneGap builds much easier.

Continuation of JavaScript Improvements

New JavaScript properties introduced in CI 6 have been better integrated into the MyEclipse environment. Easily include JavaScript technology modules from the MyEclipse menu.

Find Tern modules, which provide JavaScript editor content assist for additional technologies, on the JavaScript Resources project properties page. Other JavaScript preference nodes have been renamed for clarity.

Updated TomEE Server Connector

The TomEE server connector now supports version 1.7 as well as 1.5 and 1.6.

Faster Resource Filtering

The introduction of the MyEclipse Explorer in CI 1 brought you a resource filter for quickly finding specific resources in your projects. CI 7 improves this filter by providing faster results for filename searches, even in massive workspaces.

New Maven Dependencies-Only Mode

Although most older Maven projects (10.x and below) continue to work in modern versions of MyEclipse, this new mode supports the exceptions. In addition, use this new facet if you want to benefit only from Maven’s dependency management system rather than using the full Maven-based build capabilities. See Maven as Dependency Manager Only for technical details of this new mode.

Initial Support for AngularJS

AngularJS is a hot topic, and MyEclipse 2015 CI 7 includes basic support to help you get started with this exciting technology. You’ll find project and general properties for AngularJS, content assist, and a new Angular Explorer view. Stand by – we will add more AngularJS integration in subsequent releases!

Special Thanks
We would like to extend special thanks to Angelo Zerr, whose Tern.js and Angular JS plugins are the basis for our support of these technologies. Thank you!

Custom Integration of tern.java

In MyEclipse 2015 CI 6, we’ve given our JavaScript support a boost by using tern.js under the covers with a custom integration of tern.java. JavaScript content assist provided in both standalone JS files as well as HTML files has been significantly improved in terms of the number and validity of the proposals provided. We also provide easy  access to content assist for a large number of third party libraries. 

This is our first integration of Tern into MyEclipse. Over the next couple of releases, we will be polishing the integration and leveraging Tern to enhance other areas of JavaScript in MyEclipse beyond content assist.

Updated Spring Support

You can now add Spring 4.1 support to your projects! Our Spring-JPA and Spring-Hibernate tooling have also been updated to handle this new version.

In addition to the core Spring framework, we have updated Spring Web Flow to version 2.4.0 and Spring Security to version 3.2.5.

As always, if you use Maven for your project configuration, we’ll set up the right dependencies in your POM.

Coding Report

A new report is available that provides you information about how much coding time you spend and in what areas of MyEclipse. Access this report on the #CoderLIfe tab of the MyEclipse Dashboard.

REST Web Services Project Explorer

The REST Project Explorer view gives you an overview at a glance of the web services you’ve defined for a specific project. Quickly navigate between methods and resources; double-clicking a method in the REST Project Explorer view opens the resource file to the selected method. The same REST services information also appears in the MyEclipse Explorer view.

PhoneGap Project JQuery Mobile Templates

Starting PhoneGap mobile projects is now easier with JQuery Mobile templates built into the New Project wizard.

Notable Improvements

• Included additional PhoneGap support improvements.
• Fixed display issues on Retina displays due to Incorrect rendering of fonts.
• The Servers project in the MyEclipse Explorer is now hidden by a filter, and the Tomcat configuration files are instead accessed from a Configuration files node in the Servers view.
• Corrected inability to properly deploy a Web Fragment JAR.ectors.
• Fixed issue where projects deployed in exploded mode were being reloaded unnecessarily after hot sync already occurred.
• Server toolbar icon now remembers the last server launched and can be used to relaunch same server.
• Mobile application build errors are reported in the console for easier viewing. A pop-up notification reports the error and prompts the user to consult the error log for more details.

MyEclipse Built on Luna

Eclipse 4.4, the Luna release, is here! From Java 8 and Lambda expressions to the much awaited ability to enable split editors, MyEclipse is built on the Luna GA release, ready for you to take advantage of the latest features from Eclipse. To learn about some of the highlights of the Luna release, visit http://genuitec.com/luna.

Server Connectors Updated to the WTP Framework

Ever since our first release, MyEclipse has shipped custom server connectors. Over the past decade, we’ve added support for more than a dozen server families ranging from Apache’s Tomcat to IBM’s WebSphere, with multiple versions supported per family.

With 2015, we’re merging our connector framework with the Web Tools server framework, giving you the best server tooling across both camps. All the servers we have ever shipped are still supported, but they now offer additional control & configurability, something that will only get better as we march toward our GA release.

Key features:

• Deploy multiple projects simultaneously.
• Multiple versions of the same server are formally supported.
• Finer grained server status reporting.
• Packaged deployed mode still supported across all connectors.
• Install third party connectors from the Eclipse marketplace or elsewhere into MyEclipse and have them work seamlessly with our server tooling.

WebSphere-specific enhancements:

• The fast in-workspace deployment mode is now the default deployment mode; it supports the deployment of all project types.
• You can now start and stop individual modules.
• MyEclipse automatically detects running WebSphere instances and provides instant access to its services and up-to-date module deployment status.

In prior versions of MyEclipse, we had legacy WebSphere connectors in the Pro edition, as opposed to the new WebSphere connectors in the Blue edition. With the unified product (read more below), we have removed our legacy WebSphere connectors in favor of the newer Blue connectors. You must have a Blue license to use WebSphere in MyEclipse.

New REST Explorer Provides More Flexibility

The new MyEclipse REST explorer has been written from the ground up to allow you to explore REST web services through WADL files. You can even create WADL files from scratch and use the explorer to hit the end points immediately.

The REST API node in the MyEclipse Explorer view includes a few predefined REST services that you can explore in the REST Explorer. These services require authentication; both OAuth 1 and OAuth 2 (code grant flow) are currently supported – feel free to add your own services to the list.

This explorer does work on all OSs and architectures and is miles ahead of the explorer we had in earlier releases.

Dashboard and Other Tools Make Tasks Easier

The MyEclipse dashboard allows you to create new projects easily or import existing projects from version control or your file system. Each dashboard section includes key project management actions and relevant documentation, giving you a jump-start on development in MyEclipse.

The MyEclipse Explorer view presents a framework-centric view of your project without losing the Java focus of the Package Explorer. The explorer includes the ability to filter resources displayed based on name, and enables easy file content search. It also includes additional nodes like the REST API and Servers nodes.

Mobile Tooling - PhoneGap Support

The new PhoneGap Application Project wizard enables development of hybrid HTML5-Native mobile apps using PhoneGap 3.3 (Cordova 3.3) for both Android and iOS. Manage plug-ins using the Plug-in wizard, test apps in the Mobile Web Simulator, and then use PhoneGap Build Services to build your app for testing on devices or for final release.

Note: HTML5 Mobile app tools are deprecated in MyEclipse 2015.

Try Upgraded Features with Integrated Upgrade Trials

MyEclipse 2015 CI is a unified MyEclipse product with license levels allowing you to access all MyEclipse features. Instead of downloading and installing separate products (MyEclipse Blue, MyEclipse Spring or MyEclipse Bling), the license level you purchase provides you with access to features such as advanced WebSphere and Spring, all from one product.

With the unified MyEclipse 2015 CI, you can easily try out all features without losing your existing license setup. When you run across a feature that requires an upgrade from your current license, MyEclipse notifies you that the feature is an upgrade and provides you the opportunity to try a free 30-day upgraded license.