JBoss Tools is a set of plugins for Eclipse that complements, enhances and goes beyond the support that exist 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 installation and no-fuzz 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.
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 Mac OSX 64-bit we recommend you start it with -d32 to enable 32-bit to allow you to get the Visual Page editor and use a lot less memory.
java -d32 -jar jbdevstudio-<installername>.jar
Similar if you are on Windows 64-bit then use a 32-bit JDK to get 32-bit version running.
JBoss Tools requires a bit more:
This release requires at least Eclipse 3.7.1 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:
Note: SOA tooling such as Drools, jbpm, ESB, Teeid etc. are not included in this release - they will be available separately.
Below is my favorite features this time around from our long list of fixes and feature improvements for this Beta.
Control JBoss Hot-redeployment
JBoss server adapter normally lets the JBoss Server or Eclipse JDT figure out when it is time to load newly deployed content or update class files via the debugger, but in some cases it is nice being able to say you would like a restart of your application when certain file changes.
We do it automatically for updates to jar files, but you might want it to be more agressive and even do it on individual class file changes or when you update .jsp's or similar files.
If you enable the "Customize application reload behavior on changes to project resources" you now can enter a regular expression to match which resources it should trigger a reload of the module on.
Here are some examples:
|Expression||When it will reload|
|\.jar$|\.jsp$||on a jar or jsp file change|
|.*||on any resource changes (unnecessary!|
|\.jar$|\.class$||on a jar or class file change|
|.jar$|.*\.model\..*.class$||on a jar change or on when a .class file inside a package containing ".model." in its name (useful for only reloading on JPA annotation changes)|
Cheatsheet for regular expression syntax used above: \. matches a . (dot), $ means end of line, | means 'or' allowing to group content.
This of course means more often redeploys but that can very often be just the thing you need for your specific workflow.
Skinned and Intelligent BrowserSim
The mobile browser simulator now looks like a mobile browser and will now try intelligently to detect which URL to open with based on what is the current selection/editor in Eclipse.
Redesigned OpenShift UI
To handle more complex scenarios such as supporting deploying openshift applications already associated with another git repo and to make OpenShift easier to get started with we have redesigned the OpenShift wizards and views.
OpenShift Express Console
We've added view called OpenShift Express Console which gives you a nice overview of your OpenShift account(s), your applications/cartridges and provides easy access to common operations.
OpenShift Source and binary deployment
It is now possible to drag existing deployable resources such as WTP projects and resources marked as deployable to the OpenShift server and if the resource is part of the related github project it will just be associated with the server, but if the resource is not part of the OpenShift project then it will be placed inside the /deployments folder of the project as a binary.
Once you publish to OpenShift the binary deployments will be deployed together with your source project which will be built by OpenShift.
Updated JBoss Central content
JBoss Central now refreshed all the main wizards for JavaEE, Richfaces, html5.
We are also now featuring GWT Web project which has Errai in it showing of their event bus to communicate between multiple browsers.
Note, that Google Eclipse plugins are not installed by default - it will be offered when you click the GWT web project.
EAP 6 Enterprise Maven Repository
All of the examples above works with the upcoming EAP 6 release which includes a Enterprise Maven repository.
To enable this target an EAP 6 server adapter or set the "enterprise" flag in the wizard to true.
From this the project will generate projects that uses the proper enterprise supported binaries over the community binaries.
We found and fixed a memory and CPU issue that caused import of bigger projects to be slow and in some cases even stall.
With this issue fixed projects import much faster even for our small test projects it wins 4 seconds and for larger projects it should be even bigger gains.
As always let us know if you see slowness that seems unwarranted and we will love to help trace it down and fix the problems.
Seam tooling now accepts and work with Seam 2.3. Seam 2.3 is still in development but it will eventually allow deploying Seam 2 applications on JBoss 7 and Enterprise Application Platform 6.
The Forge tooling now bundles Forge 1.0.0.Final and adds a good set of usability features.
Link with editor makes any file opened in the current editor be picked up by Forge - meaning you don't have to manually type the resource location into Forge. Forge will already be there.
"cd" and "pick-up" support, is kind of the opposite, here things you do in Forge gets Eclipse to open/select the used resources.
Maven + JPA
Maven now detects if your project is using JPA and enables JPA/Dali/Hibernate tooling support on your project.
JAX-RS + Webservice Tester
The JAX-RS REST Web Services node in Project Explorer now supports "Run As..."-style launching of the Webservice tester.
Meaning you can right click on a URL path under JAX-RS and run as on your server and it will if, necessary deploy the application, start the server and then open the web services tester
with the selected URL and give you easy acces to test and explore the returned output.
The above are just a fraction of the 750+ issues we have fixed this time around - you can see more highlights and screenshots here, but I encourage you to try out this Beta of JBoss Tools or Developer Studio instead of just taking my word for it - and let us know in the comments or forum what you think about it!