Red Hat JBoss Developer Studio 11.0 Release Notes and Known Issues Highlighted features in 11.0 Last Updated: 2017-10-05
Red Hat JBoss Developer Studio 11.0 Release Notes and Known Issues Highlighted features in 11.0 Misha Husnain Ali mhusnain@redhat.com Supriya Takkhi sbharadw@redhat.com
Legal Notice 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 11.0.
Table of Contents Table of Contents. CHAPTER......... 1... INTRODUCTION.............. TO... RED.... HAT..... JBOSS...... DEVELOPER............ STUDIO..................................... 3. 1.1. ABOUT RED HAT JBOSS DEVELOPER STUDIO 3 1.2. USE CASES OF JBOSS DEVELOPER STUDIO 3 1.2.1. Web applications 3 1.2.2. Web applications optimized for mobile devices 4 1.2.3. Hybrid mobile applications 4 1.2.4. Applications for cloud deployment 4. CHAPTER......... 2... ABOUT....... THIS.... RELEASE...................................................................... 5.. CHAPTER......... 3... ECLIPSE........ AUTOMATED............ REPORTING........... INTERFACE...........(AERI)....................................... 6.. CHAPTER......... 4... NEW.... FEATURES........... AND.... ENHANCEMENTS.............................................................. 7. 4.1. FUSE TOOLING 7 4.1.1. Devstudio Installer 7 4.1.2. Bean Support 7 4.1.3. Seam Component Deprecation 10 4.2. FORGE TOOLS 10 4.2.1. Forge Runtime updated to 3.7.2.Final 10 4.3. OPENSHIFT 10 4.3.1. oc client Selection Per Connection 10 4.3.2. OpenShift Server and Kubernetes Server Versions Displayed 13 4.4. FREEMARKER 15 4.4.1. Freemarker Component Deprecation 15 4.5. HIBERNATE TOOLS 15 4.5.1. Hibernate Search Support 15 4.5.1.1. Functionality 15 4.5.1.2. Index Rebuild 16 4.5.1.3. Index Toolkit 18 4.5.1.3.1. Analyzers 18 4.5.1.3.2. Explore Documents 18 4.5.1.3.3. Searching 19 4.5.1.3.4. Demo 19 4.6. SERVER TOOLS 19 4.6.1. EAP 7.1 Server Adapter 19 4.6.2. Removal of Event Log and Other Deprecated Code 20 4.7. DOCKER TOOLS 20 4.7.1. New Basic Security Option 20 4.7.2. Docker Tooling JDT Integration 21. CHAPTER......... 5... RESOLVED.......... ISSUES...................................................................... 23... CHAPTER......... 6... KNOWN....... ISSUES......................................................................... 24... CHAPTER......... 7... APPLY...... THIS..... RELEASE..................................................................... 25.. 1
Red Hat JBoss Developer Studio 11.0 Release Notes and Known Issues 2
CHAPTER 1. INTRODUCTION TO RED HAT JBOSS DEVELOPER STUDIO CHAPTER 1. INTRODUCTION TO RED HAT JBOSS DEVELOPER STUDIO 1.1. 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 Hibernate, CDI, JAX-RS, JSF, Seam, 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). 1.2. 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: 1.2.1. 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. 3
Red Hat JBoss Developer Studio 11.0 Release Notes and Known Issues 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. 1.2.2. 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. 1.2.3. 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. 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 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. 4
CHAPTER 2. ABOUT THIS RELEASE CHAPTER 2. ABOUT THIS RELEASE Red Hat JBoss Developer Studio 11.0 is an update of Red Hat JBoss Developer Studio 10.4 and it has the following features: It includes Eclipse Oxygen. 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/documentation/enus/red_hat_jboss_developer_studio/11.0/html/components_and_supported_configurations/ on the Red Hat Customer Portal. 5
Red Hat JBoss Developer Studio 11.0 Release Notes and Known Issues CHAPTER 3. 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. 6
CHAPTER 4. NEW FEATURES AND ENHANCEMENTS CHAPTER 4. NEW FEATURES AND ENHANCEMENTS 4.1. FUSE TOOLING 4.1.1. Devstudio Installer Fuse Tooling was previously a part of Red Hat JBoss Developer Studio Integration Stack. For easier availability of development of Fuse integration projects, it is now a part of Red Hat JBoss Developer Studio. For an overview, see https://tools.jboss.org/features/fusetools.html. Fuse Tooling is now also available in Red Hat Central. Figure 4.1. Fuse in DevStudio 4.1.2. Bean Support We are happy to finally announce support for Beans (Spring/Blueprint). Using the Route Editor you can now access Spring / Blueprint Beans in your Camel Context through the Configurations tab. 7
Red Hat JBoss Developer Studio 11.0 Release Notes and Known Issues Figure 4.2. Bean Support In the Configurations tab you can see all global configuration elements of your Camel Context. You can add, edit and delete elements using the buttons on the right side. Figure 4.3. Edit Elements Click Add or Edit to open a wizard to guide you on creation of the Bean. 8
CHAPTER 4. NEW FEATURES AND ENHANCEMENTS Figure 4.4. Add or Edit Wizards In the wizard you can select an existing bean class from your project or create a new bean class. You can also specify constructor arguments and bean properties. Once created you can then modify the properties of that Bean in the Properties view. Figure 4.5. Modify Bean Properties 9
Red Hat JBoss Developer Studio 11.0 Release Notes and Known Issues 4.1.3. Seam Component Deprecation The Seam component has been marked deprecated because the Seam project has been stopped. It is still available in Red Hat Central and may be removed in the future. 4.2. FORGE TOOLS 4.2.1. Forge Runtime updated to 3.7.2.Final The included Forge runtime is now 3.7.2.Final. For the official announcement, see this. 4.3. OPENSHIFT 4.3.1. oc client Selection Per Connection Some operations (logs, file synchronization) require the use of the oc CLI client. You could specify a single instance of the used oc CLI tool for the whole workspace. This could cause trouble when working simultaneously with several OpenShift clusters (that may have different version levels). It is now possible to specify the oc CLI tool on the connection level. This is optional and the default is to use the oc CLI tool specified at the workspace level. The connection specific oc CLI tool is accessible through the Edit OpenShift Connection dialog box using the Advanced button. 10
CHAPTER 4. NEW FEATURES AND ENHANCEMENTS Figure 4.6. Advanced Button Enable the Override 'oc' location' flag and select a specific oc CLI tool for this connection through the Browse button. 11
Red Hat JBoss Developer Studio 11.0 Release Notes and Known Issues Figure 4.7. Browse Button for CLI OpenShift connections created by the CDK server adapter will automatically have a specific oc CLI tool set as the CDK installs locally an oc CLI tool that is aligned with the embedded OpenShift version. 12
CHAPTER 4. NEW FEATURES AND ENHANCEMENTS Figure 4.8. An Automatically Set oc CLI Tool 4.3.2. OpenShift Server and Kubernetes Server Versions Displayed The OpenShift server and Kubernetes server versions are now displayed in the OpenShift connection properties. This information is retrieved using an un-authenticated request and logging in to the OpenShift cluster is not required. This allows the user to verify the OpenShift and Kubernetes level when interacting. Here is an example based on an OpenShift connection against CDK3: 13
Red Hat JBoss Developer Studio 11.0 Release Notes and Known Issues Figure 4.9. OpenShift and Kubernetes Server Versions Displayed No values are displayed if the cluster is not started or accessible. 14
CHAPTER 4. NEW FEATURES AND ENHANCEMENTS Figure 4.10. No Values Displayed 4.4. FREEMARKER 4.4.1. Freemarker Component Deprecation The Freemarker component has been marked deprecated as there is no more maintenance on the source code. It is still available in Red Hat Central and may be removed in the future. Related JIRA: JBIDE-24484 4.5. HIBERNATE TOOLS 4.5.1. Hibernate Search Support We are glad to announce the support of the Hibernate Search. The project was started by Dmitrii Bocharov in the Google Summer Code program and has been successfully transferred in the current release of the JBoss Tools from Dmitrii s repository into the jbosstools-hibernate repository and has become a part of the JBoss family of tools. 4.5.1.1. Functionality 15
Red Hat JBoss Developer Studio 11.0 Release Notes and Known Issues Two options were added to the console configurations submenu: Index Rebuild and Index Toolkit. These option are available when you use hibernate search libraries (they exist in the build path of your application, e.g. via maven). Figure 4.11. Index Rebuild Menu Option 4.5.1.2. Index Rebuild When introducing Hibernate Search in an existing application, you have to create an initial Lucene index for the data already present in your database. The option Index Rebuild will do this by re-creating the Lucene index in the directory specified by the hibernate.search.default.indexbase property. 16
CHAPTER 4. NEW FEATURES AND ENHANCEMENTS Figure 4.12. Creating the Lucene Index 17
Red Hat JBoss Developer Studio 11.0 Release Notes and Known Issues Figure 4.13. hibernate.cfg.xml File 4.5.1.3. Index Toolkit The Open Index Toolkit submenu of the console configuration opens an Index Toolkit view, which has three tabs: Analyzers, Explore Documents, Search. 4.5.1.3.1. Analyzers This tab allows you to view the result of the work of different Lucene Analyzers. The combo-box contains all classes in the workspace which extend org.apache.lucene.analysis.analyzer, including custom implementations created by the user. While you type the text you want to analyse, the result immediately appears on the right. Figure 4.14. Analyzers Tab 4.5.1.3.2. Explore Documents After creating the initial index you can now inspect the Lucene Documents it contains. All entities annotated as @Indexed are displayed in the Lucene Documents tab. Click the checkboxes as needed and load the documents. Iterate through the documents using arrows. 18
CHAPTER 4. NEW FEATURES AND ENHANCEMENTS Figure 4.15. Index Toolkit Tab 4.5.1.3.3. Searching The plugin passes the input string from the search text box to the QueryParser which parses it using the specified analyzer and creates a set of search terms, one term per token, over the specified default field. The result of the search pulls back all documents which contain the terms and lists them in a table below. Search Tab image::search.png[search Tab] 4.5.1.3.4. Demo To see a demo of the Hibernate Search Pluging, see the demo. 4.6. SERVER TOOLS 4.6.1. EAP 7.1 Server Adapter 19
Red Hat JBoss Developer Studio 11.0 Release Notes and Known Issues A server adapter has been added to work with EAP 7.1. It s currently released as a Tech-Preview feature, since the underlying WildFly 11 continues to be under active development with substantial opportunity for breaking changes. This new server adapter includes support for incremental management deployment like it s upstream WildFly 11 counterpart. Related JIRA: JBIDE-24508 4.6.2. Removal of Event Log and Other Deprecated Code The Event Log view has been removed. The standard eclipse log is to be used for errors and other important messages regarding errors during server state transitions. Related JIRA: JBIDE-22717 4.7. DOCKER TOOLS 4.7.1. New Basic Security Option Support has been added to the Run a Docker Image wizard to add a basic security option. When chosen, this option behaves the same as using docker run --cap-drop=all --readonly --tmpfs /run -- tmpfs /tmp. In addition to dropping extraneous capabilities, the basic option makes all non-mounted directories read-only and mounts /run and /tmp into tmpfs which is cleared on each start of the container. Figure 4.16. Run a Docker Image Wizard 20
CHAPTER 4. NEW FEATURES AND ENHANCEMENTS 4.7.2. Docker Tooling JDT Integration The Eclipse Docker Tooling Feature now contains a plugin that integrates with the Java Development Tools (JDT). This permits the running and debugging of Eclipse Java projects within containers. The functionality is provided through the context menu under the Run As and Debug As options. The daemon connection used, as well as the image chosen are configurable through launch configurations. Figure 4.17. Debug As and Run As Menu Options This is intended to work in the same way that a regular run/debug session works. 21
Red Hat JBoss Developer Studio 11.0 Release Notes and Known Issues Figure 4.18. Debugging a File 22
CHAPTER 5. RESOLVED ISSUES CHAPTER 5. RESOLVED ISSUES To view information about resolved issues in this release of JBoss Developer Studio, see the Resolved Issues. 23
Red Hat JBoss Developer Studio 11.0 Release Notes and Known Issues CHAPTER 6. KNOWN ISSUES To view information about known issues in this release of JBoss Developer Studio, see the Known Issues. The following 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-3069: Ungraceful shutdown results in multiple errors on startup JBIDE-24754: Redhat Central screen does not show due to JS error JBDS-4442: Central page does not work on Fedora 26 if package webkitgtk3 is not installed JBIDE-25146: Eclipse annotation processing not enabled by default can result in errors 24
CHAPTER 7. APPLY THIS RELEASE CHAPTER 7. APPLY THIS RELEASE JBoss Developer Studio 11.0 is available from a number of sources: To install JBoss Developer Studio 11.0, use the universal installer available from the Red Hat Customer Portal. To install JBoss Developer Studio BYOE 11.0 in Eclipse Oxygen, 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 JBoss Developer Studio Documentation page. 25