The Import wizard that you can access via File > Import Projects from Folder…, File > Import… > General > Projects from Folder or File > Import… > Git > Projects from Git (auto-import) allows more user control. You can now see a proposal for the import (what will be imported and how) and select which sub-projects to import or exclude.
Performance is also significantly improved, and importing a Maven project will now suggest installation of m2e connectors when necessary.
A new feature has been added to safely store your credentials for various domains in a central location. As our tools grow, credential re-use by several different features is required. Having a central place to store, for example, your Red Hat Access credentials or JBoss.org credentials, for re-use by our server adapters or download-runtime features helps to prevent you from having to constantly type the same usernames and passwords in multiple locations. It also helps to ensure that if you change your password on some remote server, you only need to update one location in eclipse.
To access the central credential storage, browse to Window > Preferences > JBoss Tools / Credentials. From there, add custom domains for which you wish to store credentials, or add username/password combinations to the two pre-existing domains: access.redhat.com and jboss.org.
At this time, only
Download Runtimes and the new (experimental)
CDK Server Adapter use this new framework. However, usage is expected to increase in the future across the toolset as the tool matures.
A new Windows installer is available now to help you install Developer Studio with a full development environment for container based development using Red Hat Enterprise Linux and OpenShift.
The Installer currently only works on 64-bit Windows only and is currently available as a Technology Preview.
The Red Hat JBoss Developer Studio Platform installer sets up the following components on your machine:
Red Hat JBoss Developer Studio
Red Hat Container Development Kit
OpenShift Client (OC) Tools
Please register on developers.redhat.com to get access to the Platform.
Here is a short demo of the new installer: https://youtu.be/dMWAguol3as
Important: Ensure that Virtualization is enabled in the BIOS settings for your machine. This is required to run VirtualBox and Vagrant. For further information, consult your system’s documentation for instructions to change BIOS settings.
Hybrid mobile tools now use Cordova CLI for Cordova plugin management and platform builds. This allows us to provide accurate build and Cordova plugin management that is compatible with the latest Apache Cordova releases.
This new feature uses Cordova CLI installed on your system and guides you through installation if they are missing.
When running an image, a launch configuration is created based on the selected image. This is useful when users want to try tweaking a previous run for various reasons (e.g. binding in new volumes or changing command parameters, etc.)
Running a container from an image can now be also done via a launch configuration.
Docker Machine is now supported for the creation of a new connection. Simply click the "Search…" button and you will be prompted to select an active Docker Machine connection, if one exists.
Containers created with a pseudo TTY allocated (-t) will open within a TM Terminal. This is much more fully featured interaction when compared with the previous standard console. In particular, the Terminal view recognizes the color code on logs and displays messages in appropriate colors.
A shortcut to build a Docker image from a Dockerfile is available. On the first call, it will prompt for the Docker connection to use and an optional name (repo/tag) to give to the image.
The launch configuration also now supports most of the build options available from CLI.
If your mouse pointer hovers a label, you will see the same tooltip as when the mouse hovers over the input field.
Forge now supports choosing a technology stack when creating a project:
In addition to setting up your project, choosing a stack automatically hides some input fields in the existing wizards, such as the JPA Version in the
JPA: Setup wizard:
The included Forge runtime is now 3.0.1.Final. Read the official announcement here.
CMD in OSX) +
4 are pressed and the file is changed but not yet saved, Forge will display a confirmation dialog asking the user to save the current open file:
You can check the
Always save before opening the command dialog checkbox to avoid displaying the confirmation dialog. This setting can be changed anytime in the
Preferences dialog under the
Freemarker library included in the Fremarker IDE was updated to latest available version 2.3.23.
Related JIRA: JBIDE-20908
Two new runtime providers for Hibernate where added with in 4.3.1.Final. Both these new versions can be selected in the relevant wizards.
This runtime includes the 5.0.8.Final version of Hibernate ORM and the 5.0.0.Alpha3 version of Hibernate Tools Core which was build using the 5.0.8.Final version of Hibernate ORM.
This runtime includes the 5.1.0.Final version of Hibernate ORM and the 5.1.0.Alpha1 version of Hibernate Tools Core which was build using the 5.1.0.Final version of Hibernate ORM.
Related JIRA: JBIDE-22091
JST / JSF / HTML Editor
Read more about their New and Noteworthy features here:
Note: These features are available via JBoss Central - Early Access as a part of AngularJS for Web Tools
Related JIRA: JBIDE-21180
OpenShift 3 was introduced as a technology preview feature in JBDS 9.0.0.GA. We’re happy to see it graduate to the level of supported feature in this release. More than 300 issues and enhancements were tackled in this version, here is an excerpt of the most noteworthy bits:
The explorer view has been simplified (and made much more robust) and focuses on an application-centric view.
Multiple OpenShift projects are included under a single OpenShift 3 connection. Under each project, application deployments,
each associated with one service, are displayed. When relevant, the default route displays next to the service name.
It can be conveniently opened from the
Show In > Web Browser menu.
Under a service deployment, the node displays running Pods and/or Builds in progress.
More details on OpenShift resources are accessible in the Properties view.
Opened via the
Properties menu in the OpenShift Explorer, or
Ctrl+I shortcut (
Cmd+I on Mac), the Properties view is
dynamically linked to any selected OpenShift resource in the workspace.
When selecting a Project or Service, it displays a series of tabs, each matching a set of OpenShift
resources linked to the one selected in the OpenShift Explorer.
In each tab, you can, via a right-click, edit or delete a resource, open it in the Web Console or access more
The OpenShift Explorer and the Properties view are listening to server side events, so they’re immediately refreshed, when a new build or deployment has been triggered, even from the command line or the web console. Try it, it’s pretty uncanny!
You can now deploy existing workspace projects to OpenShift 3 instances. You can either create a new OpenShift application,
using an OpenShift 3 connection and then select the workspace project to deploy, or you can start by right-clicking on a project
and use the
Deploy to OpenShift… menu.
The project needs to be shared with git and declared a remote git repository using the HTTP(S) protocol. That repository needs
to be accessible from the target OpenShift instance. Once a project is selected, a selection of compatible templates will be
displayed, matching the type of the project. The remote git URL is injected as a value for the
GIT_URI) template parameter.
Related JIRA: JBDS-3489
A new OpenShift 3 server adapter is available. Its goal is to allow incremental deployment of workspace resources directly into the deployed pods on OpenShift, bypassing the build step, to provide a much quicker turnaround.
Publishing files to a remote pod requires to add the OpenShift binary (version 1.1.1 or higher) to your OpenShift preferences
From the OpenShift Explorer, right-click on a deployed Service and select the
Server Adapter… menu: it will either
create a new Server adapter or display one in the Servers view if it already exists.
|The application must be fully built and deployed on OpenShift before creating the server adapter, else an error will occur.|
If the OpenShift Service has a Build Config with a git URL matching the git remote URL of one of the workspace projects, that project will be pre-selected. If no match is found, you will need to select the project manually.
Once created, the Server Adapter will start publishing the workspace project content to the remote running Pod via RSync.
The OpenShift 3 server adapter respects the auto-publish settings as declared in the server editor, so when enabled, every changed file in your project will automatically be published to the pod.
Support for Java EE projectsWhen the workspace project associated with the OpenShift 3 server is a Dynamic or Enterprise Application project, the server adapter builds an exploded version of the archive to a temporary local directory and replaces the version deployed on the remote OpenShift pod. A
The OpenShift 3 server adapter supports running in debug mode. When you click on the debug button, a series of actions are performed under the hood:
the Deployment Configuration on OpenShift is modified to enable debug mode if necessary
the server adapter waits for a new pod to be redeployed, if the deployment configuration was modified
once the remote pod is ready, port forwarding is enabled if necessary, binding the remote ports to local ones
local resources are synchronized to the remote pod
a remote debugger attempts to attach itself to the local port bound to the remote debug port (port 8787)
This provides a similar level of debug support as a locally-run application server. So you will be able to set breakpoints in your source files, dynamically change the value on variables on the remote JVM, and even be able to perform some limited hot class reloading.
Debug mode has been tested to work on EAP based applications deployed on OpenShift. Let us know if you have trouble running it in other use cases.
The OpenShift 3 server adapter supports LiveReload, accessible from the
Show In > Web Browser via LiveReload Server menu. When a file
is published to the server adapter, the Browser(s) connected to the LiveReload server instance will automatically refresh.
This is particularly effective in conjunction with the Auto Publish mode for the OpenShift 3 server adapters, as all it takes to reload a web resource is saving the file under edition.
Related JIRA: JBIDE-21429
When connecting to an OpenShift instance, a dialog opens to allows users to accept/refuse untrusted SSL certificates.
Those authorizations can now be reviewed and potentially revoked in a preferences page
Preferences > JBoss Tools > OpenShift 3 > SSL Certificates.
Edit… menu is available in the OpenShift Explorer or the Properties view, allowing you to edit any resource (except Builds) as JSON
in a text editor. This is equivalent to the
oc edit command in a terminal. If a JSON editor is installed,
it will be used to open the configuration, else the standard text editor will be called. When saving the configuration changes in the editor,
its content will be sent to the OpenShift instance to update the underlying resource. This can be useful to, for instance,
add label to resources or edit the git source URL.
This feature can be used to, for instance, set the number of replicas in a Deployment Config, or change the url in a Route.
|Be aware this is a very powerful tool, to use with caution, as you might risk accidentally corrupting your OpenShift project.|
Related JIRA: JBIDE-20761
A new server adapter has been added to help start and stop the Red Hat Container Development Kit (CDK), a set of tools meant to quickly set up an OpenShift instance inside a Docker container running inside a virtual machine. While the server adapter itself has limited functionality, it is able to start and stop the CDK virtual machine via its Vagrantfile.
Cmd+3 on OSX) and type CDK, that will bring up a command to setup and/or launch the CDK server adapter.
All you have to do is set the credentials for your Red Hat account and the location of the CDK’s Vagrantfile. Once you’re finished,
a new CDK Server adapter will then be created and visible in the Servers view.
Once the server is started, Docker and OpenShift connections should appear in their respective views, allowing the user to quickly create a new Openshift application and begin developing their AwesomeApp in a highly-replicatable environment.
The connection created for the local OpenShift instance uses the
Right-click on a running CDK server adapter and select an option in the
Show In menu to display the OpenShift or Docker Explorer:
We’ve updated our schema catalog to include all bug-fixes or new versions, so that now your example projects targeting WildFly 10 will benefit from the same code-completion proposals that past versions have.
In addition, several schema had small updates, bugfixes, and documentation changes. All of these will be available in the XML Catalog now.
Windows often locks files when it shouldn’t, and this causes a big problem for filesystem-based deployments that look to make changes on-the-fly. We’ve managed to improve our integration with the WildFly application server, and to make sure we won’t make changes to files while they’re still locked by the server. Other upstream bugs in WildFly or the JDK directly are being investigated, and we look forward to having patches there in the near future.
With your permission, Eclipse and Red Hat JBoss Developer Studio can inspect errors logged inside the IDE and inform project committers about the issues you’ve experienced. This optional service, called Automated Error Reporting Initiative (AERI), can report issues to both the Eclipse Bugzilla and the JBoss JIRA.
When the first error is logged, you’ll be asked if you’d like to participate in error reporting, which is by default completely anonymous and only happens if an error occurs.
Should you want to configure how the service operates, or provide your email address so that you could be contacted regarding any reports you submit, open
Preferences > General > Error Reporting. You can then click
Configure Projects… to enable or disable reporting to Eclipse or JBoss.
As always, neither Eclipse nor JBoss will use any information unless a user has opted in, nor is there ever any personal information sent unless it is provided on the Preferences page.
Related JIRA: JBIDE-21654