Red Hat JBoss Developer Studio 10.2

Release Notes

Highlighted features in 10.2

Misha Husnain Ali

<mhusnain@redhat.com>

Supriya Bharadwaj

<sbharadw@redhat.com>

Red Hat Developer Group Documentation Team <devtools-docs@redhat.com>

Copyright © 2017 Red Hat, Inc.

The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.

Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.

Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.

Linux® is the registered trademark of Linus Torvalds in the United States and other countries.

Java® is a registered trademark of Oracle and/or its affiliates.

XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.

MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.

Node.js® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.

The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.

All other trademarks are the property of their respective owners.

Abstract

This document lists and briefly describes new and improved features of Red Hat JBoss Developer Studio 10.2.

Chapter 1. Introduction to Red Hat JBoss Developer Studio

About Red Hat JBoss Developer Studio

JBoss Developer Studio is a set of Eclipse-based development tools. It contains plug-ins that integrate with Eclipse to extend the existing functionality of the integrated development environment (IDE).

JBoss Developer Studio is designed to increase your productivity when developing applications. You can focus on building, testing, and deploying your applications because JBoss application development tools are integrated in one IDE. JBoss Developer Studio can also assist your application development with its unique features in the following ways:

Develop new applications using the wizards and project examples of Red Hat Central

Add powerful functionality to applications with minimal effort using Forge Tools

Build web interfaces with ease using the visual editing and drag-and-drop utilities of Visual Web Tools and Mobile Web Tools

Experience browsers automatically refreshing in response to modified application resources with LiveReload Tools

Incorporate JSF, Seam, JAX-RS, Hibernate, CDI, and other popular APIs into applications with simplicity using the tool-driven interface

Preview and test mobile web applications on a variety of simulated mobile devices using BrowserSim

Create, build, and test Cordova-based hybrid mobile applications for iOS and Android platforms using Hybrid Mobile Tools and CordovaSim

Deploy applications to JBoss runtime servers and the cloud using JBoss Server Tools and OpenShift Tools

JBoss Developer Studio is built around Eclipse and packaged with all the necessary dependencies and third-party plug-ins for simplified installing. For developers already running Eclipse, JBoss Developer Studio can also be installed through Eclipse Marketplace. Installing JBoss Developer Studio in an existing Eclipse installation is referred to as BYOE (Bring Your Own Eclipse).

Use Cases of JBoss Developer Studio

JBoss Developer Studio assists Java EE developers by integrating JBoss technology and APIs in a single development environment. Here are a few ways that JBoss Developer Studio helps make development easier:

Web applications

Red Hat Central provides wizards that generate skeletons and sample projects, enabling you to focus on developing the functionality of your applications. The wizards create web applications based on different APIs and technologies, showing the usage and advantages of each. JBoss Developer Studio also offers project file templates in a range of popular programming languages, including HTML, XHTML, and JSF.

Palettes in JBoss Developer Studio give access to the core elements of the JSF, RichFaces and Seam APIs, for use in developing the user interfaces of your applications. Elements of these APIs can be dragged and dropped directly into your project so that you can create richer user interfaces quickly. Visual Web Tools offers graphical and source viewing of files and defaults to dedicated editors for different file types. JBoss Developer Studio supports the Java EE specification and provides tools for JAX-RS, Hibernate, and CDI APIs so you can develop the server-side components of your applications effortlessly.

LiveReload Tools automatically refreshes browsers of local or deployed applications as you modify project resources to avoid needing to manually refresh. You can experience automatic refreshing when viewing applications in browsers on external and mobile devices, with application web addresses easy to navigate to with QR codes.

Web applications optimized for mobile devices

Mobile Web Tools provides support for HTML5 and jQuery Mobile to enable you to create web applications optimized across desktop and mobile clients. The HTML5 Project wizard in Red Hat Central generates a sample application using HTML5 and jQuery Mobile technologies and, together with HTML5 and jQuery Mobile project file templates, helps you to get up and running with these APIs and technologies quickly. HTML5 and jQuery Mobile widgets can be dragged from the jQuery Mobile palette into your project files and, in conjunction with the widget wizards, enable you to effortlessly develop customized user interfaces for your mobile web applications.

BrowserSim allows you to view your web applications on a variety of simulated mobile devices so that you can ensure they will be correctly formatted. LiveReload also extends to BrowserSim allowing you to experience automatic browser refreshing as you develop your mobile web applications. The integration of Firebug Lite and Weinre capabilities with BrowserSim assists you to inspect the page source of web pages with familiar tools.

Hybrid mobile applications

Hybrid Mobile Tools provides support for developing and building Cordova-based hybrid mobile applications for iOS and Android platforms. The Hybrid Mobile application wizard assists you to quickly generate new projects, while the Cordova Configuration Editor and Cordova Plug-in Discovery wizard help you to efficiently modify the capabilities of your projects. Hybrid Mobile Tools provides actions that simplify your workflow, for example calling your system installed Android and iOS SDKs from within the IDE to emulate or run your hybrid mobile applications. With wizards to export workspace projects to Cordova-enabled native projects or ready-to-sign applications, you can quickly be ready to share your hybrid mobile projects and applications.

CordovaSim enables you to view and test your hybrid mobile applications on Android and iOS simulated mobile devices so that you can ensure they look and work as expected. You can interact with your mobile applications through BrowserSim and use the device input panel to provide sample data to your applications for device functions like cameras and accelerometers. An advantage of CordovaSim is that it does not require native SDKs to be installed on your system, unlike native SDK emulators. Additionally, by teaming the device control panel with BrowserSim, you get all of the great functionality of BrowserSim, such as skins and LiveReload, while simulating your hybrid mobile applications.

Applications for cloud deployment

OpenShift Tools deploys your applications directly to the cloud on the Red Hat OpenShift platform. You can create and manage your OpenShift account and manage the deployment of applications to OpenShift within the IDE. In addition to using the OpenShift Application wizard to create and deploy new OpenShift applications, OpenShift Tools can import applications already deployed on OpenShift so that you can further develop them and manage their deployment from the comfort of the IDE.

About this Release

JBoss Developer Studio 10.2 is an update of JBoss Developer Studio 10.1 and it has the following features:

It includes Eclipse Neon.

It can be installed using RPM packages on Red Hat Enterprise Linux 7 (Technology Preview feature)

It includes Red Hat JBoss EAP 7 in the bundled installer.

It requires a minimum of Java 8 to run.

It introduces new features, which are outlined in the New Features section.

It contains new features for the existing tools.

It resolves issues identified in earlier versions of JBoss Developer Studio.

For more information about operating systems, chip architectures and Java developer kits supported by this release, see https://access.redhat.com/site/articles/427493 on the Red Hat Customer Portal.

Eclipse Automated Reporting Interface (AERI)

To contribute to JBoss Tools, we recommend you to enable the Eclipse Automated Reporting Interface (AERI) in JBoss Tools. To read about configuring error reporting in JBoss Tools, see: http://tools.jboss.org/usage/#error-reporting.

New Features and Enhancements

Installing JBoss Developer Studio from RPM on Red Hat Enterprise Linux

Starting with JBoss Developer Studio 10.2, JBoss Developer Studio can be installed using the standard package management system on Red Hat Enterprise Linux 7.2 and higher. RPM packages that use the Software Collections format are provided in the rh-eclipse46-devstudio-stable-10.x repository. See the Installing JBoss Developer Studio Using RPM section of the Red Hat JBoss Developer Studio 10.2 Installation Guide for instructions.

Note

The RPM package method for installing JBoss Developer Studio is being released as a Technology Preview for JBoss Developer Studio 10.2. For information on support for features released as Technology Preview, see Technology Preview Features Support Scope.

Forge Tools

New Menu in Forge Console view to trigger the Command Selection Dialog

Users can now open the Command Selection Dialog menu (Ctrl/Command + 4) by choosing the Open Command Selection Dialog menu in the Forge Console view.

Forge Runtime updated to 3.4.0.Final

The included Forge runtime is now 3.4.0.Final. Read the official announcement here.

OpenShift

Common namespace is now configurable

When looking for Openshift resources (builder images, templates), a common namespace is browsed. Earlier hardcoded openshift namespace is now configurable with default value openshift.

You can access and modify it through the connection extended properties:

Related JIRA: https://issues.jboss.org/browse/JBIDE-23014

CDK server using native terminal for better user interactions

The CDK server adapter now uses a native terminal that allows better interaction with the user. In case the credentials are not passed in the Vagrant environment, the user will be asked to ENTER the login credentials (similar to the standard Vagrant CLI) and in case of registration failures, retries will be performed.

First, ensure that your CDK server adapter is configured not to pass credentials:

Start the CDK server adapter and a new terminal window will open asking for registration:

If you answered y to the previous questions, the terminal window will ask for the username:

The terminal window will then ask for the password:

If the registration fails, the terminal window will retry and ask for the username and password:

Related JIRA: https://issues.jboss.org/browse/JBIDE-23039

User controlled hostname when creating routes

When an application is being deployed to Openshift, a route is optionally created if required by the user. Openshift/CDK is used to create an xip.io based hostname. User can now set the hostname. This allows for both, changing the DNS to local IP provider (nip.io) and using your own enterprise DNS naming strategy. The hostname can be accessed from the Services and Routing Settings page when deploying an application:

Related JIRA: https://issues.jboss.org/browse/JBIDE-23147

Create routes targetting a specific service port

When an application is being deployed to Openshift, a route is optionally created if required by the user. It is now possible to target a specific port (exposed by a to-be-created service). When the ports are being displayed, it is possible to select one of them and then this selected port can be used by the route. By default, none of the ports are selected (this round robin is performed). The route port can be accessed from the Services and Routing Settings page when deploying an application:

Related JIRA: https://issues.jboss.org/browse/JBIDE-23015

Node.js Debugger

Users can now debug Node.js applications deployed to Openshift. All you need to do is create a Server Adapter for the application and run it in the Debug mode. A new V8 debug session will then be created:

Put some breakpoints in the code and then you can start debugging.

Steps by steps instructions

Step 1: deploy the nodejs:latest builder

Using the Openshift Explorer, deploy a new application using the nodejs:latest builder image. Once deployed, the Openshift Explorer should look like this:

Import the application source code into your workspace so that you can set breakpoints.

Step2: create the server adapter

Select the nodejs service, right click and select the Server adapter menu item. An Openshift Server Adapter Settings dialog will display, click the Finish button. The server adapter will be created and the Servers view will look like this:

Step 3: restart the server adapter in debug mode

In order to debug Javascript code, the server adapter must be restarted in debug mode. Select the server adapter, right click and select the Restart in Debug menu item. The Servers view should look like this:

Step 4: Add a breakpoint into the server code

Open the server.js file located in the nodejs-ex project that you imported in Step 1. Around line 79, the handler for the pagecount is defined so you can add a breakpoint in the following lines (line 82 for the first instruction).

Step 5: Open the web browser

In the Openshift Explorer, select the nodejs service, and select Show in → Web Browser. The home page for the application will be displayed:

Step 6: Debug your Javascript code

Add pagecount at the end of the URL in the location toolbar and press ENTER. This will trigger Javascript debugging as you setup a breakpoint in Step 4. Depending on your Eclipse settings, you may see a dialog asking to switch to the debug perspective:

If you see this dialog, press ENTER and the debug perspective will be shown. If you don’t see this dialog, then the debug perspective is directly shown.

Changing the code during the debug session is also supported. To change the code, save the file and new changes will be applied automatically. Here is a short demo video that shows the debugging process in action.

Related JIRA: https://issues.jboss.org/browse/JBIDE-22225

Server Tools

Support for Jolokia JMX Connections

For some users, accessing a remote test server via standard JMX may require opening ports that, for one reason or another, cannot be opened. In these cases, a user may choose to deploy a jolokia agent to their server. Jolokia is a deployable war archive that exposes JMX over http, typically using JSON. This feature is handy as an added tool for debugging a development application, but is not really suitable or safe to expose on production. With that in mind, the workflow is as follows:

Download the Jolokia war file from jolokia.org, and place it in the proper deployments folder for your application server. For wildfly, this folder is: 'standalone/deployments'.

Start the server via the method you typically use. If your usecase allows it, use the Servers view to create and start a server adapter. If this workflow doesn’t work for you, you may wish to start the server manually.

Once the server is started, open the JMX Navigator.

Right-click User-Defined Connections , and select New Connection.

Select Jolokia Connection.

Give the connection a name, and the url at which jolokia can be reached. Then finish the wizard.

You can now browse your JMX tree in the JMX Navigator.

Most other JMX operations will work. You can double-click an MBean node to open the editor, check properties, or invoke operations. Notifications, however, are not supported.

Related JIRA: https://issues.jboss.org/browse/JBIDE-23429

Issues

Resolved Issues

To view information about resolved issues in this release of JBoss Developer Studio, see https://issues.jboss.org/issues/?jql= on the JBoss issue tracking system and enter the following advanced search query as one line:

(project in (JBDS) AND affectedVersion < 10.2.0.AM1 AND fixVersion in (10.2.0.AM1, 10.2.0.AM2, 10.2.0.AM3, 10.2.0.GA) OR project in (JBIDE) AND affectedVersion < 4.4.2.AM1 AND fixVersion in (4.4.2.AM1, 4.4.2.AM2, 4.4.2.AM3, 4.4.2.Final)) AND type in (Bug) AND resolution in (Done)

Known Issues

To view information about known issues in this release of JBoss Developer Studio, see https://issues.jboss.org/issues/?jql= on the JBoss issue tracking system and enter the following advanced search query as one line:

(project in (JBDS) AND (affectedVersion <= 10.2.0.GA OR affectedVersion is EMPTY) AND (resolution in (Unresolved) OR resolution in (Done) AND fixVersion > "10.2.0.GA") OR project in (JBIDE) AND (affectedVersion <= 4.4.2.Final OR affectedVersion is EMPTY) AND (resolution in (Unresolved) OR resolution in (Done) AND fixVersion > "4.4.2.Final")) AND type in (Bug)

The following customer-reported known issues are highlighted:

JBIDE-20985: XML Schema validation fails when importing external schema

JBIDE-20983: cannot use oracle service name in datasource creation

JBIDE-19633: Not able to create 'non-bare' repository in JBDS 8.1.

JBIDE-17176: Unable to browse and select PortletBridge runtime liberaries in JPP 6

JBIDE-12957: Xhtml files appear garbled when it’s reopened in the JBDS editor

JBDS-3645: Installation of JBoss Developer Studio to a network drive fails

JBDS-3470: Toolbars + Icons unusable on UHD screens

JBDS-3186: JBDS crashes when editor is opened on RHEL 6

JBDS-3069: Ungraceful shutdown results in multiple errors on startup

Apply this Release

JBoss Developer Studio 10.2 is available from a number of sources:

To install JBoss Developer Studio 10.2, use the universal installer available from the Red Hat Customer Portal.

To install JBoss Developer Studio BYOE 10.2 in Eclipse Neon, use Eclipse Marketplace, the JBoss Developer Studio update site or the update .zip file available from the Red Hat Customer Portal.

In all cases, for more information see the Red Hat JBoss Developer Studio Installation Guide at the Red Hat JBoss Developer Studio Documentation page.