MyEclipse 2015 CI 19 is a bug-fix release including fixes in the PhoneGap and Server areas. Our integrated version of Emmet has also been updated.
Included in this release:
- Miscellaneous Key Fixes
MyEclipse 2015 CI 19 is a bug-fix release including fixes in the PhoneGap and Server areas. Our integrated version of Emmet has also been updated.
This is a bug-fix release taking us to the end of 2015. We have a new Wildfly 10 connector and several fixes in the server, PhoneGap and licensing areas.
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!
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.
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.
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.
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.
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.
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.
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.
In addition, we now have better handling for sites with invalid SSL certificates.
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.
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.
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.
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.
The CI 13 release contains a new Minimap productivity tool and several improvements to servers and deployment.
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.
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.
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.
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.
MyEclipse continues to be based on the latest Eclipse releases – CI 12 is based on Eclipse Luna SR2 (4.4.2), an upgrade from SR1 (4.4.1) used in prior versions.
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
A more complicated example, ul>li.item$*5 will result in
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.
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.
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.
Switch to ECMAScript 6 for Promise support.
RequireJS Object Literal Completion
For the RequireJS config object, applying completion generates a property key/value pair.
We have also added support for a couple of additional frameworks like Jasmine, Protractor, and snabbit.js.
As always, a shout out to Angelo Zerr and the Tern JS/Java community for their continued work in this area.
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.
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.
Want to create a project with the latest PhoneGap 4.2 CLI? CI 11 fixes a minor bug in this area that makes this possible. To use for building your applications, first download PhoneGap 4.2 CLI. Once downloaded, configure it by selecting Window>Preferences, expanding MyEclipse>Mobile Tools, and selecting PhoneGap Runtime.
The CI 10 release is the production-grade release of MyEclipse 2015! We will continue the CI stream for MyEclipse 2015, similar to service releases. A couple more additions have been included to round out the production release features.
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.
Support for the iOS platform is coming soon.
Also, the console will now display build output for remote builds.
The CI 9 release continues improvements to the PhoneGap configuration editor, and includes a MyEclipse Reports update.
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:
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.
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.
The CI 8 release of MyEclipse marches on toward finalizing MyEclipse 2015. The major activity around this release involves final testing, fixing and polishing, with the addition of a few more enhancements discussed below.
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.
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.
The PhoneGap configuration editor is now a form-based editor that makes setting up for PhoneGap builds much easier.
The TomEE server connector now supports version 1.7 as well as 1.5 and 1.6.
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.
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.
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!
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!
The MyEclipse 2015 CI 5 release continues work on updating server frameworks, adds updated Spring support, plus a few other additions and fixes.
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.
The MyEclipse 2015 CI 4 release focuses on a new addition to REST web services and PhoneGap project improvements.
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.
Starting PhoneGap mobile projects is now easier with JQuery Mobile templates built into the New Project wizard.
PhoneGap projects now support PhoneGap version 3.5.0 (internally Cordova 3.5.1). This update includes security fixes for both local and remote builds. MyEclipse users simply need to create their projects with PhoneGap 3.5 and both remote as well as local builds will include the fix.
For more information, please see:
Please note that PhoneGap 3.5 project creation requires a working Internet connection. This constraint will be removed in CI 5.
The MyEclipse 2015 CI 3 release includes 22 bug fixes and improvements. A couple of highlights are:
The MyEclipse 2015 CI 2 release includes a number of bug fixes, improving the features released in CI 1.
MyEclipse 2015 CI 1 is the first release in the CI stream. Many new features are added in this release and will continue throughout the stream.
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.
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.
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.
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.
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.
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.
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.
Our embedded Derby server has been updated from version 10.9.1.0 to 10.10.2.0 in order to support Java 8 environments.
The integrated version of Spring Tool Suite has been updated to version 3.5.1 from 3.3.0.
Linux / GTK 3
With Luna, Eclipse has enabled GTK3 support by default on Linux. While this is a major step forward in supporting modern Linux OSs, the GTK3 support is still not complete. During our Luna integration tests we have experienced some bugs related to GTK3, like missing menu shortcuts, flickering during control refresh, color scheme issues, sporadic keybindings problems and, in rare occasions, crashes. We expect Luna SR1 to include fixes to all critical issues, a small sampling of which can be found here: 340067, 424596, 431160.
Users who are dissatisfied with GTK3 support can force GTK2 mode by setting up an environment variable as shown below:
$ export SWT_GTK3=0