red hat jboss developer studio 10.4 release notes and ......inspect the page source of web pages...

Misha Husnain Ali Supriya TakkhiRed Hat Developer Group DocumentationTeam

Red Hat JBoss Developer Studio10.4Release Notes and Known Issues

Highlighted features in 10.4

Red Hat JBoss Developer Studio 10.4 Release Notes and Known Issues

Highlighted features in 10.4

Misha Husnain [email protected]

Supriya [email protected]

Legal Notice

Copyright © 2017 Red Hat, Inc.

The text of and illustrations in this document are licensed by Red Hat under a Creative CommonsAttribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA isavailable athttp://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you mustprovide 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 Infinitylogo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and othercountries.

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 Statesand/or other countries.

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

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

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

All other trademarks are the property of their respective owners.

AbstractThis document lists and briefly describes new and improved features of Red Hat JBoss DeveloperStudio 10.4.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table of Contents

CHAPTER 1. INTRODUCTION TO RED HAT JBOSS DEVELOPER STUDIO1.1. ABOUT RED HAT JBOSS DEVELOPER STUDIO1.2. USE CASES OF JBOSS DEVELOPER STUDIO

1.2.1. Web applications1.2.2. Web applications optimized for mobile devices1.2.3. Hybrid mobile applications1.2.4. Applications for cloud deployment

CHAPTER 2. ABOUT THIS RELEASE

CHAPTER 3. ECLIPSE AUTOMATED REPORTING INTERFACE (AERI)

CHAPTER 4. NEW FEATURES AND ENHANCEMENTS4.1. IMPROVED OPENSHIFT 3 AND DOCKER TOOLS

4.1.1. OpenShift Server Adapter Enhanced Flexibility4.1.2. Security Vulnerability Fixed in Certificate Validation Database

4.2. CDK 3 SERVER ADAPTER4.3. OPENSHIFT CONTAINER PLATFORM 3.5 SUPPORT

4.3.1. OpenShift Server Adapter Extensibility4.3.2. Pipeline Builds Support

4.4. UPDATE OF DOCKER CLIENT4.4.1. Run Image Network Support4.4.2. Refresh Connection

4.5. SERVER TOOLS4.5.1. API Change in New Connection Wizard of JMX UI

4.6. HIBERNATE TOOLS4.6.1. Hibernate Runtime Provider Updates4.6.2. Hibernate Runtime Provider Updates

4.7. FORGE TOOLS4.7.1. Forge Runtime Updated to 3.6.1.Final

CHAPTER 5. RESOLVED ISSUES

CHAPTER 6. KNOWN ISSUES

CHAPTER 7. APPLY THIS RELEASE

3333444

6

7

888

101114141416161718181818181919

20

21

22

Table of Contents

1


2

CHAPTER 1. INTRODUCTION TO RED HAT JBOSSDEVELOPER STUDIO

1.1. ABOUT RED HAT JBOSS DEVELOPER STUDIO

JBoss Developer Studio is a set of Eclipse-based development tools. It contains plug-ins thatintegrate 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 applicationdevelopment tools are integrated in one IDE. JBoss Developer Studio can also assist yourapplication 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 WebTools and Mobile Web Tools

Experience browsers automatically refreshing in response to modified application resources withLiveReload Tools

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

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

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

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

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

1.2. USE CASES OF JBOSS DEVELOPER STUDIO

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

1.2.1. Web applications

Red Hat Central provides wizards that generate skeletons and sample projects, enabling you tofocus on developing the functionality of your applications. The wizards create web applicationsbased 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 programminglanguages, including HTML, XHTML, and JSF.

CHAPTER 1. INTRODUCTION TO RED HAT JBOSS DEVELOPER STUDIO

3

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

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

1.2.2. Web applications optimized for mobile devices

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

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

1.2.3. Hybrid mobile applications

Hybrid Mobile Tools provides support for developing and building Cordova-based hybrid mobileapplications for iOS and Android platforms. The Hybrid Mobile application wizard assists you toquickly generate new projects, while the Cordova Configuration Editor and Cordova Plug-inDiscovery wizard help you to efficiently modify the capabilities of your projects. Hybrid Mobile Toolsprovides actions that simplify your workflow, for example calling your system installed Android andiOS SDKs from within the IDE to emulate or run your hybrid mobile applications. With wizards toexport workspace projects to Cordova-enabled native projects or ready-to-sign applications, youcan 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 iOSsimulated mobile devices so that you can ensure they look and work as expected. You can interactwith your mobile applications through BrowserSim and use the device input panel to provide sampledata to your applications for device functions like cameras and accelerometers. An advantage ofCordovaSim is that it does not require native SDKs to be installed on your system, unlike native SDKemulators. Additionally, by teaming the device control panel with BrowserSim, you get all of thegreat functionality of BrowserSim, such as skins and LiveReload, while simulating your hybrid mobileapplications.

1.2.4. 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 toOpenShift within the IDE. In addition to using the OpenShift Application wizard to create and deploynew OpenShift applications, OpenShift Tools can import applications already deployed on


4

OpenShift so that you can further develop them and manage their deployment from the comfort ofthe IDE.

CHAPTER 1. INTRODUCTION TO RED HAT JBOSS DEVELOPER STUDIO

5

CHAPTER 2. ABOUT THIS RELEASE

Red Hat JBoss Developer Studio 10.4 is an update of Red Hat JBoss Developer Studio 10.3 and ithas the following features:

It includes Eclipse Neon.

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 supportedby this release, see https://access.redhat.com/site/articles/427493 on the Red Hat Customer Portal.


6

https://access.redhat.com/site/articles/427493

CHAPTER 3. ECLIPSE AUTOMATED REPORTINGINTERFACE (AERI)

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

CHAPTER 3. ECLIPSE AUTOMATED REPORTING INTERFACE (AERI)

7

http://tools.jboss.org/usage/#error-reporting

CHAPTER 4. NEW FEATURES AND ENHANCEMENTS

4.1. IMPROVED OPENSHIFT 3 AND DOCKER TOOLS

4.1.1. OpenShift Server Adapter Enhanced Flexibility

OpenShift server adapter is a great tool that allows developers to synchronize local changes in theEclipse workspace with running pods in the OpenShift cluster. It also allows you to remotely debugthose pods when the server adapter is launched in the Debug mode. The supported stacks are Javaand NodeJS.

As pods are ephemeral OpenShift resources, the server adapter definition was earlier based on anOpenShift service resource and the pods were then dynamically computed from the service selector.

This has a major drawback as it allows to use this feature only for pods that are part of a service,which may be logical for Web based applications as a route (and thus a service) is required in orderto access the application.

It is now possible to create a server adapter from the following OpenShift resources:

Service (as before)

Deployment config

Replication controller

Pod

If a server adapter is created from a pod, it will be created from the associated OpenShift resourcein the preferred order:

Service

Deployment config

Replication controller

The OpenShift Explorer used to display OpenShift resources that were linked to a service. Thishas been enhanced. It now displays resources linked to a deployment configuration or replicationcontroller. The following image shows an example of a deployment with no service i.e. a deploymentconfiguration.


8

An OpenShift server adapter can be created from different kind of resources. The type of associatedresource is displayed when creating the OpenShift server adapter.

Once created, the type of OpenShift resource adapter is also displayed in the Servers view.


9

This information is also available from the server editor.

Related JIRA: JBIDE-23490

4.1.2. Security Vulnerability Fixed in Certificate Validation Database

When you use the OpenShift tooling to connect to an OpenShift API server, the certificate of theOpenShift API server is first validated. The connection is established if the issuer authority is aknown one. If the issuer is an unknown one, a validation dialog is first shown to the user with thedetails of the OpenShift API server certificate and the details of the issuer authority. The connectionis established if the user accepts it. There is also an option to store the certificate in a database sothat next time a connection is attempted to the same OpenShift API server, the certificate will beconsidered valid and no validation dialog will be show again.


10

https://issues.jboss.org/browse/JBIDE-23490

Security vulnerabilty existed due to the wrongly stored certificate. Not all attributes, but it waspartially stored; we may interpret that in these cases a certificate that was not meant to be validatedwas validated.

The format of the certificate database was changed. As the certificates stored in the previousdatabase were not entirelly stored, there was no way to provide a migration path. As a result, afterthe upgrade, the certificate database will be empty. So, if you had previously accepted somecertificates, then you need to accept them again and fill the certificate database again.


4.2. CDK 3 SERVER ADAPTER

The CDK 3 server adapter that was released as Technology Preview because CDK 3 was notofficially released, is now officiallly available. While the server adapter has limited functionality, it isable to start and stop the CDK virtual machine via its minishift binary. Press Ctrl+3 (Cmd+3 on OSX)and type CDK to display a command to setup and/or launch the CDK server adapter. You shouldsee the old CDK 2 server adapter along with the new CDK 3 one, labeled Red Hat ContainerDevelopment Kit 3.


11


To set a new server, set the credentials for your Red Hat account, the location of the CDK minishiftbinary file, and the type of virtualization hypervisor.


12

After its creation, the new CDK Server adapter is created and listed in the Servers view.

After the server is started, Docker and OpenShift connections appear in their respective views,allowing the user to quickly create a new Openshift application and begin developing theirAwesomeApp in a highly-replicatable environment.


13


4.3. OPENSHIFT CONTAINER PLATFORM 3.5 SUPPORT

OpenShift Container Platform (OCP) 3.5 is announced by Red Hat. For details, see Red Hat BringsKubernetes to New Application Workloads with Latest Version of Red Hat OpenShift ContainerPlatform. JBoss Developer Studio is validated against OCP 3.5.

4.3.1. OpenShift Server Adapter Extensibility

The OpenShift server adapter had support for EAP/Wildfly and NodeJS based deployments. Thisserver adpater also synchronizes local workspace changes to remote deployments on OpenShiftwhich have been standardized through images metadata (labels). But each runtime has its ownspecifics. For example, Wildfly/EAP deployments require that a re-deploy trigger is sent after thefiles have been synchronized.

In order to reduce the technical debt and allow support for other runtimes (many in the microserviceworld), the OpenShift server adapter is refractored so that each runtime specific is now isolated andthat it will be easy and safe to add support for new runtime.

For in-depth description, see this wiki page.


4.3.2. Pipeline Builds Support


14


https://www.redhat.com/en/about/press-releases/red-hat-brings-kubernetes-new-application-workloads-latest-version-red-hat-openshift-container-platform

https://github.com/jbosstools/jbosstools-openshift/wiki/Openshift-server-adapter-profile-and-its-subsystems


Pipeline based builds are now supported by the OpenShift tooling. When creating an application, ifusing a template, if one of the builds is based on pipeline, you can view the detail of the pipeline.

When your application is deployed, you can see the details of the build configuration for the pipelinebased builds.


15

We are improving the pipeline support in the OpenShift tooling.


4.4. UPDATE OF DOCKER CLIENT

The level of the underlying com.spotify.docker.client plug-in used to access the Docker daemon hasbeen upgraded to 3.6.8.

4.4.1. Run Image Network Support

A new page has been added to the Docker Run Image wizard and Docker Run Image Launchconfiguration that allows the end-user to specify the network mode to use. A user can choose fromDefault, Bridge, Host, None, Container, or Other. If Container is selected, the user must choosefrom an active Container to use the same network mode. If Other is specified, a named network canbe specified.


16


4.4.2. Refresh Connection

Users can now refresh the entire connection from the Docker Explorer view. You can refresh theconnection in any one of the following two ways:


17

Using the right-click context menu from the connection

Using the Refresh menu button when the connection is selected

4.5. SERVER TOOLS

4.5.1. API Change in New Connection Wizard of JMX UI

Extenders must be aware that the API for adding connection types to the New JMX Connectionwizard in the JMX Navigator has changed. Specifically, the org.jboss.tools.jmx.ui.providerUIextension point is changed. Previously it had a child element called wizardPage. It now requires awizardFragment.

A wizardFragment is part of the TaskWizard framework first used in WTP’s ServerTools, which isused throughout JBossTools. This framework allows wizard workflows where the set of pages to bedisplayed can change based on what selections are made on previous pages.

This change was made as a direct result of a bug caused by the addition of the Jolokia connectiontype in which some standard workflows could no longer be completed.

This change only affects adopters and extenders, and should have no noticable change for theusers, other than that the bug has been fixed.


4.6. HIBERNATE TOOLS

4.6.1. Hibernate Runtime Provider Updates

A number of additions and updates have been performed on the available Hibernate runtimeproviders.

4.6.2. Hibernate Runtime Provider Updates


18


The Hibernate 5.0 runtime provider now incorporates Hibernate Core version 5.0.12.Final andHibernate Tools version 5.0.5.Final.



Related JIRAs: JBIDE-24281, JBIDE-24279, JBIDE-24272

4.7. FORGE TOOLS

4.7.1. Forge Runtime Updated to 3.6.1.Final

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



19




http://forge.jboss.org/news/jboss-forge-3.6.1.final-is-here


CHAPTER 5. RESOLVED ISSUES

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

"(project in (JBDS) AND fixVersion in (10.4.0.AM1, 10.4.0.AM2, 10.4.0.AM3, 10.4.0.GA) OR project in (JBIDE) AND fixVersion in (4.4.4.AM1, 4.4.4.AM2, 4.4.4.AM3, 4.4.4.Final)) AND type in (Bug) AND resolution in (Done)"


20

https://issues.jboss.org/issues/?jql=


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

(project in (JBDS) AND (affectedVersion <= 10.4.0.GA OR affectedVersion is EMPTY) AND (resolution in (Unresolved) OR resolution in (Done) AND fixVersion > "10.4.0.GA") OR project in (JBIDE) AND (affectedVersion <= 4.4.4.Final OR affectedVersion is EMPTY) AND (resolution in (Unresolved) OR resolution in (Done) AND fixVersion > "4.4.4.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


21

https://issues.jboss.org/issues/?jql=






https://issues.jboss.org/browse/JBDS-3645




CHAPTER 7. APPLY THIS RELEASE

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

To install JBoss Developer Studio 10.4, use the universal installer available from the Red HatCustomer Portal.

To install JBoss Developer Studio BYOE 10.4 in Eclipse Neon, use Eclipse Marketplace, theJBoss Developer Studio update site or the update .zip file available from the Red Hat CustomerPortal.

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


22

https://access.redhat.com/documentation/en/red-hat-jboss-developer-studio/?version=10.4/

red hat jboss developer studio 10.4 release notes and ......inspect the page source of web pages...

Documents