A JBoss Project
Red Hat

Latest posts

JBoss Tools team is so lucky to have a great QE team who assist in testing and verifying the Eclipse plugin stack continues to function as expected. In that process they have over the years been putting together a eclipse (SWT) testing library called RedDeer.

This RedDeer project released version 0.8 just recently.

RedDeer provides various utility testing, junit and SWTBot extensions and some quite unique tools specifically liked by QE to find errors/issues during their Eclipse testing.

We are planning on contributing this to Eclipse.org in the future, but would like to get early feedback on it.

Here is what Jiri Peterka recently wrote about it in his announcement on RedDeer:

Today, version 0.8.0 was released and RedDeer is again a step closer to version 1.0. RedDeer 0.8 supports Eclipse Mars (EE). This version is mainly about architecture improvements, related re-factoring and lot of bug fixes. In terms of these changes lots of underlying functionality went into o.j.r.common and mainly to o.j.r.core plugin. This helped us to keep architecture cleaner and to avoid cross dependency issues we have faced. Still you can also find multiple API and tooling features and enhancements in this release, for example:

When you start writing test plugin you can also use org.jboss.reddeer.go as an aggregate plug-in for a start in your MANIFEST.MF instead of thinking what set of the individual plugins is right for you.

Besides that, many (~70) bug fixes and other issues (~180 in total) were resolved. Thanks to all who helped again to push RedDeer project forward.

That’s it. Enjoy your testing with new RedDeer.

— Jiri Peterka
on behalf of RedDeer dev team

More info

You can find more info at these locations:

There is complete list of RedDeer public resources:

Let us know if you like what you see and feel free to leave a comment on this blog or reach out to the RedDeer project to give them feedback.

Have fun!
Max Rydahl Andersen
@maxandersen

Today a new beta is available from our download and update sites!

jbosstools bower
Remember that since Beta1 we require Java 8 for installing and using of JBoss Tools. We still support developing and running applications using older Java runtimes. See more in Beta1 blog.

Installation

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 (Mars) but we recommend using the Eclipse 4.5 Mars JEE 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 "JBoss Developer Studio".

We are now using Eclipse Marketplace feature of having just one market place entry for all old versions.

For JBoss Tools, you can also use our update site directly if you are up for it.

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

Note: Integration Stack tooling will become available from JBoss Central at a later date.

What is new ?

Full info is at this page. Some highlights are below.

Bower

We’ve added support for easy setup and invocation of Bower using your locally installed bower command line tool on Windows, OS X and Linux.

We provide a Bower Init wizard for getting started.

bower-init-wizard-page

Once your project has a bower.json file you can now easily run bower update by right-clicking on the file and selecting Run ▸ As…​ ▸ Bower Update.

We are working on contributing this and additional Javascript integration to Eclipse JSDT. We will keep you posted!

OpenShift v3

We continue to work on improving OpenShift v3 tooling and this release has a few new features and important bug fixes but overall OpenShift v3 tooling is still in very early stages.

Manage your OpenShift v3 Projects

You can now create and delete OpenShift v3 projects.

manage-projects

manage-projects-wizard

If you try to create a new application, but you have no project yet, the tools will prompt you to create one first. Once you are done you can always get back and manage your OpenShift projects via a link in the application wizard.

Manually Trigger Builds

You can manually trigger builds when selecting your Build Configs in the OpenShift Explorer.

start-build

Once you triggered you should see a new build appear in the Builds category in the OpenShift Explorer. You can see its state next to its name or in the Properties view. Refreshing the Explorer will show you when the build completes.

Port Forwarding

Assuming that your application exposes ports you can now forward those to your local machine with JBoss Tools 4.3.0.Beta2.

port-forwarding-wizard

More details of new OpenShift v3 features are at Whats New.

Java EE Batch Tooling

The batch tooling now has hyperlink support for @BatchProperty to navigate between classes and their relevant job .xml files.

openon

There are more news at Whats New.

Exploded nested jars

In WildFly 8.2 there is now support for hotloading resources from exploded jars inside deployments, i.e. a jar inside your WEB-INF/libs.

This allows you to have faster reload times for module web applications using resources from nested jars.

Thanks to patch from Vsevolod Golovanov we now support this when you are using our server tools. Thanks Vsevolod!

Deploy Hybrid project to FeedHenry

You can now take a hybrid mobile project created with Thym and deploy it to a FeedHenry cloud.

NewApplicationWiz

Enjoy!

Alexey Kazakov

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