MyEclipse 2017 CI Stream Delivery Log

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.