Warning ! This site is currently under development, and may contain inaccurate and misleading information. Report an issue
| Status: Red. Known issues: | None

A JBoss Project
Red Hat

Posts tagged with 'jbosstools'

Fuse Tooling goes Final in the Stack!

jbosstools jbdevstudio blog header

The Integration Stack for JBoss Tools Developer Studio is a set of plugins for Eclipse that provides tooling for the following frameworks:

  • BPEL Designer - Orchestrating your business processes.

  • BPMN2 Modeler - A graphical modeling tool which allows creation and editing of Business Process Modeling Notation diagrams using graphiti.

  • Drools - A Business Logic integration Platform which provides a unified and integrated platform for Rules, Workflow and Event Processing.

  • JBoss ESB - An enterprise service bus for connecting enterprise applications and services.

  • Fuse Apache Camel Tooling - A graphical tool for integrating software components that works with Apache ServiceMix, Apache ActiveMQ, Apache Camel and the FuseSource distributions.

  • jBPM3 - A flexible Business Process Management (BPM) Suite - JBoss Enterprise SOA Platform 5.3.x compatible version.

  • Modeshape - A distributed, hierarchical, transactional and consistent data store with support for queries, full-text search, events, versioning, references, and flexible and dynamic schemas. It is very fast, highly available, extremely scalable, and it is 100% open source.

  • Savara (JBoss Tools only) - A tool for ensuring artifacts defined at different stages of the software development lifecycle are valid against each other, and remain valid through the evolution of the system.

  • SwitchYard - A lightweight service delivery framework providing full lifecycle support for developing, deploying, and managing service-oriented applications.

  • Teiid Designer - A visual tool that enables rapid, model-driven definition, integration, management and testing of data services without programming using the Teiid runtime framework.

All of these components have been verified to work with the same dependencies as JBoss Tools 4.1 and Developer Studio 7, so installation is easy.


To install the Integration Stack tools, first install JBoss Developer Studio from the all-in-one installer, bundled and configured out of the box with everything you need to get started. Alternatively, if you already have eclipse-jee-kepler installed, you can install JBoss Developer Studio or JBoss Tools from the Eclipse Marketplace via Help > Eclipse Marketplace…​

jbtis b1

Once Developer Studio is installed, restart Eclipse and select the Software/Update tab in the JBoss Central view and look for the JBoss Developer Studio Integration Stack installation section. Select the items you’d like to install:

jbtis b2

If you want to try out Savara you will need to use the JBoss Tools Integration Stack URL instead:

Note: If you installed into your own Eclipse you should bump up the launch resource parameters:

--launcher.XXMaxPermSize 256m --launcher.appendVmargs -vmargs -Dosgi.requiredJavaVersion=1.6 -XX:MaxPermSize=256m -Xms512m -Xmx1024m

What’s New?

Fuse Apache Camel Tooling has gone .Final

The previous release of the JBoss Developer Studio Integration Stack had a candidate release of Fuse Apache Camel Tooling. The support is now complete and ready to run with the Fuse Active MQ 6.1 release.

Updated Components

Fix release versions of BPMN2 Modeler, SwitchYard and Teiid Designer are also available in this release.

The new JBoss Tools home is live

Don’t miss the new Features tab for up to date information on your favorite Integration Stack component: /features

We have been working for a while on doing a refresh of our website, and today we are happy to announce tools.jboss.org.


We had a few goals for the website:

  1. Make it simple and clear how to download the plugins

  2. Explain what features are in the tools

  3. Include New and noteworthy

  4. Make it easier to update/fix the content

and I think we reached all of them.

Make it simple and clear how to download the plugins

Our old download page had grown organically over the last 7 years and, despite all good intentions, we had ended up with a download page with way too many options presented by default. With the new site, we went for simplicity first, and so the Downloads page now simply presents you with two options: Download either latest stable JBoss Tools or Developer Studio.

newsite downloads

If you want other versions, combinations, add-ons etc. you can follow the Overview link which will give all the dirty details.

Explain what features are in the tools

For this we created the Features page. This page gives an overview over all of the various projects and technologies we support and if you click on the images you get more information about each feature.

newsite features

Try it out - you might be surprised how much we actually do.

Include New and noteworthy

For every release/milestone, we get the JBoss Tools team to write up what is New and noteworthy for their components. We use that when doing blogs and sharing with the whole community what changes are coming up. In the past, that was a very tedious process of getting multiple people to submit changes to a bunch of html files that then needed to be manually cleaned up and published. It was a chore, and it took longer and longer as we added or updated more and more features.

That is now a story of the past - in the new site, component developers just add a single document for their release and the magic of publishing the site does all the right wiring. Removing all the chore and reducing the actual lines of code needed substantially. Asciidoc for the win.

newsite whatsnew

You can go look at what is new and improved over at What is new - it currently gives you a sneak preview of upcoming JBoss Tools 4.2.0 Beta1.

Make it easier to update/fix the content

The old website was "hidden" behind a magnolia CMS system. It has served us well and it does what it is supposed to do. In the age of github and pull-requests though it was more a burden than a help. The new system uses a simple github repo which uses Awestruct to render the page automatically via Travis when we push to certain branches.

The content is primarily Asciidoc making it so the content is very compact - no additional boiler plate markup to worry about and best of all, you do not need to even run awestruct locally to get an idea of the rendering. Github’s rendering of asciidoc is close enough to make it trivial for anyone with a github account to help do fixes to this site.

If you find some errors (we left some in for you to find) just open a PR on https://github.com/jbosstools/jbosstools-website :)


The design and launch of this website have been long under way - we started 1+ year ago but we are finally here :)

The primary person to thank for this is Xavier Coulon who helped on the initial design of the site and then fought, battled and sometimes cried over having to implement and play with Ruby and Haml. But he persevered and today we are here with his great help!

But he and I were not alone in this; we got help from a bunch of other people to write and update content, give feedback, find bugs and help setup the infrastructure. Here they are in random importance, but ordered alphabetically:

  • Alexey Kazakov - for contributing to Features

  • Andre Dietisheim - for contributing to Features

  • Aslak Knutsen - for inspiration and help with Awestruct

  • Barry LaFond - for contributing to Features

  • Bob Brodt - for contributing to Features

  • Bob McWhirter - for reacting at weird hours on #awestruct and for not caring how his name is spelled

  • Brian Fitzpatrick - for contributing to Features

  • Cheyenne Weaver - for design help

  • Dan Allen - for help with asciidoc and especially for including the video support we made

  • Daniel Florian - for contributing to Features

  • Fred Bricon - for contributing to Features

  • Gorkem Ercan - for contributing to Features

  • Ilya Buziuk - for contributing to Features

  • James Cobb - for design help and bugfixing

  • Jason Porter - for awestruct fixes and especially finding that nasty performance bug we had made

  • Koen Aers - for contributing to Features

  • Kris Verlaenen - for contributing to Features

  • Lars Heinemann - for contributing to Features

  • Mark Newton - for enabling the infrastructure

  • Michelle Murray - for bugfixes!

  • Nick Boldt - for helping setup downloads and bugfixing!

  • Paul Leacu - for contributing to Features

  • Pete Muir - for review!

  • Rob Cernich - for contributing to Features

  • Rob Stryker - for contributing to Features

  • Rysiek Kozmik - for help with jboss.org theme

  • Snjezana Peco - for contributing to Features

  • Vineet Reynolds - for contributing to Features

  • Vladimir Vasilev - for setting up redirects to ensure we didn’t break the internet!

In case I missed someone - let me know or submit a PR on https://github.com/jbosstools/jbosstools-website

I hope you like it and please leave a comment below to test the new commenting system too :)

Have fun!

Max Rydahl Andersen

Looking for older posts ? See the Archived entries.
back to top