The release candidate of JBoss Tools and Developer Studio is now available - mainly with bugfixes but also a few nice improvements for AS 7, OpenShift and Maven integration.

jbosstolsdevstudio.png

CR1

Developer Studio: [Download] | Tools: [Download] [Update Site] | [What's New] [Forums] [JIRA] [Twitter]

 

JBoss Tools is a set of plugins for Eclipse that complements, enhances and goes beyond the support that exists for JBoss and related technologies in the default Eclipse distribution.

 

JBoss Developer Studio is a fully bundled Eclipse distribution which not only includes majority of JBoss Tools but also all its needed dependencies and 3rd party plugins allowing for an easy one-click and no-fuss installation.

 

If you are into doing your own bleeding edge eclipse plugin assembly, JBoss tools is for you; if you are more into having something that "Just Works" then JBoss Developer Studio is the way to go.

 

Installation

 

JBoss Developer Studio comes with everything pre-bundled in its installer. Simply download it and run it like this:

 

java -jar jbdevstudio-<installername>.jar

 

Note: if you are on Windows or Mac OSX 64-bit we recommend you ensure to select the 32-bit option in the multi-platform installer to get Visual Page editor working and use much less memory.

 

 

JBoss Tools requires a bit more:

 

This release requires at least Eclipse 3.7.2 but we recommend using the Eclipse 3.7.2 JEE Bundle since then you get most of the dependencies preinstalled.

 

Once you have installed Eclipse, you either find us on Eclipse Marketplace under "JBoss Tools (Indigo)" or use our update site directly.

 

The update site URL to use from Help > Install New Software... is:

http://download.jboss.org/jbosstools/updates/development/indigo/

 

Note: SOA tooling for BPEL, Drools, Guvnor, jBPM, ESB, Modeshape, pi4soa, Savara, SwitchYard & Teiid are no longer included in the JBoss Tools release. They will be available separately.

 

JBoss AS 7

The server adapter for JBoss AS 7 had a series improvements done in its handling of remote management and JMX connections. One thing that is relevant is that because of AS 7.1 Secure by default approach when you launch remotely the management services are not autoatmically exposed. We keep that secure-by-default in the tools, but now also provides a simple checkbox to allow you to expose the management service when we launch it to actually remotely manage the server.

 

https://issues.jboss.org/secure/attachment/12354382/JBIDE-11921.png

 

Of course just exposing the port does not make it fully available before you have added a user to the server. You can read about how to do that in this blog.

 

And finally the server adapter now works with IPv6, allows deploying outside of the deployments folder and it does not choke on a space in the server part - Hurray!

 

OpenShift, now faster and more patient

One of the most common bug report we got in the Beta's (thank you for the feedback!) was that when creating OpenShift applications our wizard would time out and you would have to manually import the project again. We now have extended the timeout period to three minutes to accomodate for overloads, network latency etc. but also given you the option to wait some more for the OpenShift provisioning to be fully done.

 

A new feature of the application creation wizard is also to be able to set the size of the Gear your application will run on and to enable scaling for your applications.

http://docs.jboss.org/tools/whatsnew/openshift/images/gears-and-scaling.png

Mind you that the list of possible gears depends on your users permissions.

 

Various actions like Tail Files, Environment variables and Port Forwarding which previously were only available in OpenShift Explorer is now also available from the OpenShift server adapter.

 

http://docs.jboss.org/tools/whatsnew/openshift/images/server-adapter-actions.png

 

And for those users with large set of applications or slow networks we've made the loading of OpenShift metadata more incremental giving you faster feedback,especially on networks far away from the OpenShift servers.

 

Maven and Endorsed Libraries

If you have ever had to fight with using JavaEE 6 Webservices on Java 6 with Maven and Eclipse at the same time you know what a pain having to use that combination can be because JavaEE 6 Webservices are actually using libraries that are not available before Java 7. Meaning you have to configure and setup endorsed libraries in Eclipse, which actually does not have such a feature exposed on projects, but only at the JVM level setup. Thus its "easy" for running applications but not when compiling.

 

In Maven there are various tricks to solve this and none of them are obeyed/understood by m2eclipse - but not anymore.

 

http://docs.jboss.org/tools/whatsnew/images/endorsed_libs.png

 

We've added a Maven configurator which will look for the common tricks to set and configure endorsed libraries and when they are found inject an "Endorsed Library" classpath container with the approprate classpath entries.

 

Allowing you to not have to worry about this anymore when using Maven + Eclipse. Fred writes more in detail about how this works in What's New

 

Pixel Density

And an example of where the little details matters comes that BrowserSim now has controls for pixel density allowing you to get a better and closer representative layout of your mobile applications.

 

http://docs.jboss.org/tools/whatsnew/vpe/images/3.3.0.CR1/pixel-ratio.png

 

 

...and more

 

As usual screenshots and more explanation of what is new are available from the What's New site!

 

Let us know what you think and remember that Xavier and I will be showing a lot of these features at JUDCon and Red Hat Summit w/JBoss World end of this month with a GA release. See you there ?

 

Have fun,

Max