JBoss Tools 4.3.1 and Red Hat JBoss Developer Studio 9.1 for Eclipse Mars.2 are now generally available!
|
Caution
|
Java 8 is required for installing and using JBoss Tools. We still support developing and running applications using older Java runtimes. See more in Beta1 blog. |
JBoss Developer Studio comes with everything pre-bundled in its installer. Simply download it from our JBoss Products page and run it like this:
java -jar jboss-devstudio-<installername>.jar
JBoss Tools or Bring-Your-Own-Eclipse (BYOE) JBoss Developer Studio require a bit more:
This release requires at least Eclipse 4.5.2 (Mars.2) but we recommend using the Eclipse 4.5.2 Mars.2 Java EE Bundle since then you get most of the dependencies preinstalled.
Once you have installed Eclipse, you can either find us on the Eclipse Marketplace under "JBoss Tools" or "Red Hat JBoss Developer Studio".
For JBoss Tools, you can also use our update site directly.
http://download.jboss.org/jbosstools/mars/stable/updates/
There is also a new installer available for 64-bit Windows. See details in New Developer Studio Platform Installer for Container Based Development section.
This release is based on Eclipse Mars.2 and our focus was mainly on OpenShift and Red Hat Container Development Kit tools improvements. Besides that there is a bunch of new features and a lot of fixed bugs. The full list of what is new you can find on this page.
A new installer for 64-bit Windows is now available. This installer is quite different from the good old Developer Studio universal installer. This will help you install Developer Studio with a full development environment for container based development using Red Hat Enterprise Linux and OpenShift.
Developer Studio Platform Installer Beta currently works on 64-bit Windows only and is available as a Technology Preview.
It helps to install and configure the following components to work together on your machine:
-
Red Hat JBoss Developer Studio
-
Red Hat Container Development Kit
-
Vagrant
-
VirtualBox
-
OpenJDK
-
Cygwin
-
OpenShift Client (OC) Tools
You can see how this installer works in this short screen cast:
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.
New OpenShift Server Adapter for easier and faster deployment, debug mode, integration with Red Hat Container Development Kit and more notable features were added. More than 300 issues and enhancements were also tackled in this version. See the full list of the new OpenShift tooling stuff on New and Noteworthy page.
Tooling for Docker is available in Eclipse Mars under the Linux tools umbrella. Despite this name, this works on all major developer platforms. It is mirrored on JBoss Tools update site.
The Docker tools was introduced in Developer Studio 9.0 and has been improved in Developer Studio 9.1:
-
New Docker Machine Support
-
Improved Run Image Launch Configuration
-
TM Terminal Support for Interactive Shells
-
Build Docker Images improvements
More details in New and Noteworthy.
Hibernate 5 is now supported. Two new runtime providers for Hibernate were added in this release. Both these new versions can be selected in the relevant wizards.
The included Forge runtime is now 3.0.1.Final. Read the official announcement here.
With your permission, Eclipse and Red Hat JBoss Developer Studio can now 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.