1 2 3 Previous Next

JBoss Tools

121 posts

We have moved this blog to our new website at http://tools.jboss.org

 

We will keep this blog for historical entries - but all new blogging will happen at tools.jboss.org/blog

 

All old urls should continue to work - if you find some broken let us know!

 

See more about this new site at our first new entry.

 

Have fun!

On behalf of the JBoss Tools and Developer Studio team, I am extremely proud to announce the general availability of the JBoss Tools 4.1.2.Final and Red Hat JBoss Developer Studio 7.1.1.GA releases.

 

 

JBoss Tools 4.1.2.Final and Developer Studio 7.1.1.GA

One more for the road!

Developer Studio: [Marketplace] [Download] | Tools: [Marketplace] [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.

 

Red Hat JBoss Developer Studio is a fully bundled Eclipse distribution which not only includes the 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

 

If you already have JBoss Tools 4.1.1 or Developer Studio 7.1 installed using 'Help > Update' will give you this release automatically.

 

If you want a new installation, then JBoss Developer Studio is available as a one-download-installer with everything bundled and configured out of the box.

 

You can also install JBoss Developer Studio or JBoss Tools from Eclipse Marketplace via "Help > Eclipse Marketplace..."

 

When installing from Eclipse Marketplace we recommend using a fresh Eclipse 4.3.2 JEE Bundle since then you'll have most of the dependencies pre-installed.

 

Last one before Luna

 

JBoss Tools 4.1.2 and JBDS 7.1.1 are primarily focused on building on top of the latest Eclipse Kepler SR2 release, fixing 30 issues along. We keep on trying to make the life of Angular JS users easier, as you can see below.

This is the last planned release of the JBoss Tools 4.1.x and JBDS 7.1.x streams, based on Eclipse 4.3.x. Cool kids already play with the next milestones for Luna.

 

 

No mo' warnings

 

We backported one of the features we contributed to Eclipse Luna (Milestone 6), that is the ability to ignore non-standard HTML attributes. This is typically needed when developing Angular JS applications as the HTML validator considers Angular JS ng-* attributes as invalid html (which is actually correct since the proper syntax to be 100% compatible with the html5 spec is to use data-ng-*).

 

You can now quick-fix these warning (Ctrl+1) and choose to ignore specific or all similar attributes :

better-angularjs-support.png

And if you're really into Angular JS, we recommend you try the AngularJS Eclipse plugin. We're currently evaluating it ourselves for inclusion in the next major version of JBoss Tools and Developer Studio.

 

 

Giving Feedback

 

Please don't hesitate to use our forum to ask questions, or, if you have ideas to better improve JBoss Tools / Developer Studio, or found a bug, then open an issue in our issue tracker.

 

What's Next ?

 

We're currently hard at work preparing the next iteration of JBoss Tools (4.2)  and Developer Studio (8.0), targeted at Eclipse Luna. Brace yourself for the upcoming Beta releases in the next 2 to 3 weeks, with more awesome/cool/hip stuff ;-)

 

Fred Bricon

 

http://twitter.com/fbricon

gercan

Thym Project Proposal

Posted by gercan Mar 11, 2014

When we started working on the Hybrid Mobile (Cordova) tools about a year ago, we predicted that there is a need for a good, open source IDE for developing Cordova based mobile applications. After our initial releases, we started to see the interest to use, build on and contribute to the project. With this interest, the next logical step for us was to take Hybrid Mobile tools to Eclipse Foundation to form an even greater community.


Last week, We have put the Thym (The HYbrid Mobile) project proposal online. Please take a moment to look at the proposal. At this stage, we are collecting the interested parties for the project. If this is a topic of interest for you or your organization or you simply have questions, please let me or the community at large know. Being an interested party on an Eclipse proposal means this is a project that is interesting for you and nothing more.


Once the Thym project is established our activities around mobile will NOT cease to exist on JBoss.org. Our plan is to utilize the Thym project and continue building tools that will make mobile development easier by utilizing projects and technologies such as Aerogear, Openshift etc.


Exciting times are ahead for mobile developers.

 

If you are planning to attend EclipseCon, I will be having a session around Hybrid Mobile Tools. Also, do not miss the other Red Hat sessions.

One question (and complaint) that has been raised after the release of multiple cargo version support is "How to use custom Cordova engines together with JBoss Hybrid Mobile tools?" Well, we heard you and we are already on it. In the next release, JBoss Tools 4.2.0 Beta 1, we are adding the ability to search Cordova engines from local directories and use them. Here is a video showing how this works, which is still subject to changes of course.

 

 

There are some caveats with this feature though. Unfortunately, we are not able to use "any" Cordova based distribution. In this release, tools are only able to recognize Cordova compatible directory structures. For instance, we rely on files such as VERSION, that is found on Cordova distributions, to recognize Cordova versions. However, If you have a Cordova based distribution that has a significantly different layout, it will be possible to introduce them through an Eclipse extension point. If you're interested in such an extension point, I would be happy to hear about your requirements.


If you wish to try it out, this feature is already part of nightly builds and you can get the information on nightly update site from jbostools-aerogear project site. I recommend updating the 4.2.0 Alpha2 with the nightly update site for best experience.

Its time to start the milestones counting up to the next Eclipse release train this summer. Here is the first tested to work Alpha release targeting Eclipse Luna (Eclipse 4.3) M5.

 

 

JBoss Tools 4.2.0 Alpha2

Fly me to the moon!

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.

 

Installation

 

This release is targeting Eclipse 4.4 M5 (Luna). Best approach is to download and install Eclipse JEE M5 Bundle and use this updatesite: http://download.jboss.org/jbosstools/updates/development/luna/ to install JBoss Tools from.

 

Changes

 

This release targets Eclipse Luna M5 giving you the latest fixes/improvements from eclipse.org plus a bunch of new features/improvements we have been working on.

 

Multiple Cordova Version Support

The Aerogear Hybrid mobile tooling previously supported a singular version of Cordova limiting users

ability to upgrade easily to new versions or stay at the version of Cordova they were targeting.

 

In this version we are introducing multiple cordova runtime support allowing you to use any Cordova 3.x version.

 

engineSelect.png

Arquillian Improvements

 

The arquillian tooling received a good round of bug fixes including more control over the enablement of Arquillian on your project.

addArquillianSupport.png

There are also improvements to various wizards, validation and overall speed of Arquillian tooling.

 

Server Tools rewrite

This alpha2 introduces a lot of internal changes to the server tools implementation.

 

These changes are done to allow us to add support for EAP/WildFly domain mode,

support managed deployments and allow for 100% remote servers (i.e. not require a local runtime).

Besides enabling these specific features in upcoming milestones we should also be able

to add more extensions and better workflows more easily than what we could in past.

 

For now, all existing functionality should still be working but do let us know if you spot something out of whack

and keep eyes on our nightly builds to see the benefits of this rewrite/refactoring.

 

JavaFX brings debugger to BrowserSim

 

BrowserSim can now optionally utilize JavaFX available in Oracle JVM's which allow

you to do "chrome dev-tools" style debugging and inspection of your applications.

 

chrome-debugger.png

Please be aware that this requires an Oracle JVM and currently only works reliably on Windows and OS X.

Linux support is currently problematic because of JavaFX not working on GTK3 based systems (see OpenJDK bug - requires login)

 

JavaScript Console Logging in BrowserSim

To debug syntax errors and early runtime javascript errors we now send javascript messages to the eclipse console view

when running browsersim.

 

eclipse-console-log.png

JQuery 1.4 support

Both JQuery 1.3 and 1.4 is now supported in the palette.

 

jqmPalette14.png

Improved data-* content assist

 

The existing data-* content assist now also support JQuery 1.4

jqmCA.png

And we now also load remote .css files to provide class style content assist.

 

jqmClassCA.png

 

Angular.js attribute content assist

 

To aid in developing of Angular JS applications we've added content assist for ng-* attributes.

ng-ca.png

 

Remove ng-* validation errors

A very common complaint of Angular JS users are that Eclipse (and other IDE's) mark 'ng-*' attributes like 'ng-data' as validation errors.

 

The warning is actually correct since ng-* is not valid according to html5 spec (one should be using data-*), but of course that is a mute

point when most projects uses what is recommended by AngularJS project.

 

Thus you can now go and use a Quick-Fix on the warnings and either ignore specific attributes or ignore all ng-* (or any other invalid attribute) warnings

for your project.

ngvalidationfilter.png

Note: This feature is actually part of Eclipse Luna WTP, but worth mentioning since we contributed it as part of our Alpha1/Alpha2 development.

 

LiveReload reload delay

 

LiveReload now has an option to delay the refresh of the browser.

livereload_reloaddelay.png

This reload delay is especially useful when you have JRebel running against your JBoss Server which because

of it not doing instant reload sometimes takes a few seconds to discover the changes to your html pages.

 

With this reload delay you can avoid having to manually click Refresh.

 

OpenShift Security Certificates

Until now OpenShift tooling was actually ignoring if your server had an invalid or untrusted SSL certificate.

Now OpenShift tooling will show the certificate in case it is not possible to validate it (that is the case for

self-signed certificates as provided by out-of-box configured OpenShift Enterprise installation)

 

certificate-dialog.png

 

Wait - where is Alpha1 ?

 

You might have noticed this is Alpha2 and not Alpha1. We actually built and released Alpha1 in late December but because of a lot of SWT vs GTK3 vs XULRunner vs WebKit incompatibilities (aka. hard crashes) with Luna M4.

We did not announce it widely. With fixes in Luna M5 and in our Alpha2 things are looking better - but there are still known issues with latest GTK3.9 and higher versions which if you are an SWT or GTK expert we would love

to hear from you to help fix

 

Giving Feedback

 

Please don't hesitate to use our forum to ask questions, or, if you have ideas to better improve JBoss Tools / Developer Studio, or found a bug, then open an issue in our issue tracker.

 

Have fun,

Max

 

JBoss Tools Integration Stack 4.1.3.Final and JBoss Developer Studio Integration Stack 7.0.0.GA

 

The Stack Is Really Back!

 

The Integration Stack for JBoss Tools & Developer Studio (formerly JBoss Tools & Developer Studio SOA Tooling) is a set of plugins for Eclipse that provides tooling for the following frameworks:

 

  • BPEL/Riftsaw - A Web Service Business Process Execution Language engine used to describe high level business processes and orchestration.
  • BPMN2 - A graphical modeling tool which allows creation and editing of Business Process Modeling Notation diagrams using graphiti.
  • Drools/jBPM6 - A Business Logic integration Platform which provides a unified and integrated platform for Rules, Workflow and Event Processing.
  • Drools/Guvnor - A centralized repository for Drools Knowledge Bases, with rich web based GUIs, editors, and tools to aid in the management of large numbers of rules.
  • JBoss ESB - An enterprise service bus for connecting enterprise applications and services.
  • Fuse Tooling - A graphical tool for integrating software components that works with Apache ServiceMix, Apache ActiveMQ, Apache Camel and the FuseSource distributions.

         ** Note: Fuse Tooling is currently at version 7.2.0.CR2 - not at .Final.

  • 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.

 

Installation

 

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 installed, you can install JBoss Developer Studio or JBoss Tools from the Eclipse Marketplace via Help > Eclipse Marketplace...

install-jbds-marketplace.png

 

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:

 

jbdsis-install.png

 

You may alternatively launch Eclipse or JBoss Developer Studio, and select:

 

      Help > Install New Software > https://devstudio.jboss.com/updates/7.0/integration-stack/

jbdsis-p2.png

p2-jbdsis-2.png

 

Either way will give you the final release of the tools.

 

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

 

http://download.jboss.org/jbosstools/updates/stable/kepler/integration-stack

 

News

 

Besides the great news of now having updated support for the previously available SOA Tooling, this release also brings two new components to the stack: Tooling for SwitchYard and Fuse.

 

  • SwitchYard is the replacement for JBoss ESB and is a component-based development framework focused on building structured, maintainable services and applications using the concepts and best practices of SOA.  The tooling provides wizard for setting up maven based SwitchYard projects, Configuration of SwitchYard capabilities (i.e. runtime component dependencies; e.g. SOAP, BPM, Apache Camel, etc.), graphical editor for switchyard.xml and more.

 

  • Fuse comes with tooling that enables you to work with Fuse and Apache versions of ActiveMQ, Camel, CXF, Karaf, and ServiceMix.  You can connect and configure Enterprise Integration Patterns to build routes, browse endpoints and routes, drag and drop messages onto running routes, trace message flows, edit running routes, browse and visualize runtime processes via JMX, and deploy your project's code to Red Hat JBoss Fuse and Fuse Fabric containers, to Apache ServiceMix, and to Apache Karaf.

 

There has also been significant development in Drools/JBPM and Teiid Designer.

 

  • The Drools/jBPM6 plugins have been updated to support the 6.0 version of both projects.  The wizards have been updated to the new API and  there is support for Drools6 and jBPM6 runtime libraries.  The jBPM plugin now also uses the new Eclipse BPMN2 Modeler project for editing processes using the BPMN 2.0 XML format.  This editor does support the full BPMN 2.0 specification, and the jBPM profile now supports many new building blocks and properties to use when creating your business processes.

 

  • The Teiid Designer 8.3 release provides additional JBoss Tools server integration as well as numerous bug fixes and a few enhancements.

        Primary drivers for this release:

    • Upgrade to Modeshape 3.6 for DDL import
    • Add LDAP to relational model importer
    • Add support for importing Flat File via URL
    • MongoDB model extension support

 

Lots of new toys - tell us what you think and what new tooling you'd like to see!

Our team has big interest in JavaScript tools in Eclipse. Support for JavaScript is important inside JBoss Tools and JBoss Developer Studio. We rely on JSDT, but we found several important bugs and limitations in it. We had to contribute. We got two people contributing to JSDT (Victor Rubezhny and Denis Golovin) and I (Mickael Istria) been assisting with the release engineering/project setup. We already worked with the existing JSDT team to make many fixes visible in upcoming releases. Some of these are:

 

  • Improved parsing (removes false errors on correct javascript) and better validation
  • More clean and readable code in editor

    JSDT-issues-fixed-411589-a.png

  • Bugfixes for project creation/JS renaming/quickfixes
  • Better handling of runtime errors thrown leading to improved stability

 

In the future we will add more features and fix more bugs.

 

Just as important though is that in the past JSDT was seen as a complex project to contribute too, and suffered from several pitfalls making contributors less productive than they could be. With the help of various people related to JSDT or WTP project, we improved a range of issues making contribution easier.

 

  • There is now a single Git repository to contribute to JSDT. There used to be 3 of them, which scattered the project, made it more difficult to keep things synchronized, and to build all JSDT at once.
  • This repository is handled by Gerrit, so any change can be pushed to Gerrit so it's easier for other contributors to review it
  • You can now build JSDT anywhere with a simple "mvn clean verify -Pbuild-individual-bundles" command, and have as output a p2 repository that you can use to install the latest content in your IDE
  • The same Maven command will also run JSDT automated tests, and will report any failure making it easier to spot regressions
  • It became possible to put JSDT in a continuous integration application, such as Hudson or Jenkins
  • We used Jenkins Gerrit plugin to incoming have Gerrit contributions automatically built and tested, and have Hudson voting on a patch to tell whether it contains a visible regression or not. This either gives more credit to your contribution, or it gives faster feedback if it breaks something.
  • Also, it was easy to create a job with Hudson which generates SonarQube reports. Those reports are quite interesting since they already detected many hotspots where there are very probably bugs and code that has bad performance impact.
  • This have been documented so it's easier for a new contributor to find out how to start
  • With that, we are currently trying to do some code cleanup on JSDT: fix potential bugs, replace bad constructs, improve performance...

 

As you can see, many improvements have been made to make it easy to contribute to JSDT and to give it the necessary infrastructure to increase its quality and agility. You're now very WELCOME to join JSDT and contribute to its evolution. If you want to get started now, the "Clean code" issue is a good starting point and help is very welcome there.

First of all, since it is the period for this, I want to wish everybody a happy and productive new year!

 

Just before the end of the year, the JBoss Tools team have released version 4.1.1 of JBoss Tools and version 7.1 of JBoss Developer Studio. As described in the release blog post there are a lot of interesting improvements and cool new features available. In this post, I want to focus on something that didn't get a lot of attention yet: the availability of Forge 2. As some of you know, Forge is a rapid application development tool that enables you to quickly create new projects (or use existing ones) and enhance them with support for a wide variety of Java frameworks or tools. You can even add support for your own framework or make tedious work simpler by creating your own extensions for Forge.

 

The support for Forge 1 has been included in JBoss Tools for about 2 years now. It's use has been described in one or two of my earlier posts. The fact that not a lot of people know that Forge 2 support has also been around for more than half a year is because it was in fact still pretty much under construction. But the 4.1.1 release of JBoss Tools includes Forge 2.0.0.Beta3 and it is about time that people start to be aware of its possibilities.

 

Installation

 

The installation of Forge 2 is pretty much like it was before. From a fresh install of the Kepler SR1 release of the Eclipse IDE for Java EE Developers, you select 'Help->Install New Software'. In the subsequent dialog you enter the URL of the JBoss Tools Kepler update site: http://download.jboss.org/jbosstools/updates/stable/kepler/. In the filter text you type 'Forge' and then push 'Select All' to select all the remaining items in the table. The process is illustrated in the screenshot below.

install.png

 

You can see that the Forge 2 support is still listed as experimental. This qualification is supposed to disappear soon as Forge 2 is heading towards a Final release. Also, note that the installation of the Forge Tools is needed to install the Forge Tools Extensions. The rest of the installation process is pretty straightforward: you push the 'Next' button twice, accept the license agreements and push 'Finish'. After the installation is finished you will need to restart Eclipse.

 

Start Forge 2

 

When Eclipse is restarted you are able to also start Forge 2. Currently the preferred way to do this is to use the CTRL + 5 (or CMD + 5 on a Mac) key combination. You can change the combination by bringing up the Eclipse preferences and navigating to 'General->Keys'. In the screenshot below you can see what this looks like on my machine.

preferences.png

 

Using the selected key combination for the first time will automatically start Forge 2. A popup that informs you about this will be shown.

startup.png

 

When the popup disappears a new popup takes its place. This new popup contains all the Forge 2 commands that are available in the context of the currently selected item in your workbench.

commands.png

 

You are now ready to start using Forge 2.

 

Using the Forge

 

Forge 2 has introduced a drastic change with respect to its older sibling. The preferred way to issue Forge 2 commands from within the JBoss Tools platform is now not longer to type them at a command prompt but to bring up a Forge wizard. To bring up the list of available wizards, just like when you were starting up Forge 2, issue the CTRL + 5 key combination. When Forge 2 is already started it will immediately show the popup of the available commands. As an example, let us select the 'New Project' command. The Forge 2 wizard for creating new projects will start.

newproject.png

 

I have chosen the name 'test' and kept all the defaults in the wizard page. If you hit 'Finish' the project will be created at the specified location and imported into your Eclipse workspace.

imported.png

If now, while having e.g. the src/main/java folder selected, you hit CTRL + 5 again, you will see that a vast number of new commands are appearing. Indeed, these commands are as I already mentioned earlier, depending on the currently selected item in your workspace. So within the context of a project you can do all kinds of other things like setting up support for one or more of the Java EE specs. This list can become very long so it's interesting to know that you can narrow it down by typing a search string in the text field at the top of the list.

javaee.png

 

It's out of the scope of this blog post to explain each of these possible choices in detail but stay tuned because these will be explained in detail in more posts to come and of course in our documentation.

 

Future Developments

 

While Forge 2 is supported on the command-line, the integration of it in JBoss Tools was not yet completely finished when 4.1.1 was released so you'll have to stick to the wizards for now. However, if you are really curious and want to test it out already now, you should try the JBoss Tools 4.2.x builds.

In the immediate future you can also expect the release of Forge 2.0.0.Final. We invite you cordially to try out this new version of our beloved tool whether included in JBoss Tools or at the command-line and provide us with all the feedback (good or bad) that you think might help us to make it even better.

 

In the meantime: happy Forging!


Cheers,

Koen

On behalf of the JBoss Tools and Developer Studio team, We are extremely proud to announce the general availability of the JBoss Tools 4.1.1.Final and Red Hat JBoss Developer Studio 7.1.0.GA releases.

 

 

JBoss Tools 4.1.1.Final and Developer Studio 7.1.0.GA

Hop in the cloudmobile!

Developer Studio: [Marketplace] [Download] | Tools: [Marketplace] [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.

 

Red Hat JBoss Developer Studio is a fully bundled Eclipse distribution which not only includes the 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

 

If you already have JBoss Tools 4.1 or Developer Studio 7.0 installed using 'Help > Update' will give you this release automatically.

 

If you want a new installation then, JBoss Developer Studio is available with a one-download-installer with everything bundled and configured out of the box.

 

You can also install JBoss Developer Studio or JBoss Tools from Eclipse Marketplace via "Help > Eclipse Marketplace..."

 

When installing from Eclipse Marketplace we recommend using a fresh Eclipse 4.3.1 JEE Bundle since then you'll have most of the dependencies pre-installed.

 

More of the same, only better

 

JBoss Tools 4.1.1 and JBDS 7.1 are built on top of Eclipse Kepler SR1 (4.3.1) and are primarily focused on improving stability (more than 500 issues were fixed). Don't worry, we also added a bunch of new cool features, so make sure to read the complete New and Noteworthy for a detailed and complete overview.

 

We're still riding the Mobile first theme of our previous release, so let's take a look at some of the new feats :

 

 

Resource content assist and file creation

There are now content assist on resources for things like script, img, source, anchors etc.

 

Alexey made a nice video of how it works you can watch here.

 

Furthermore if you type in a resource that does not exist the html editing tools now offer to create the resource for you, making it much easier to quickly create a set of linked resources.

CreateFileHyperlink.png

Angular.js attribute content assist

 

To aid in developing of Angular JS applications we've added content assist for ng-* attributes.

ng-ca.png

We are working on providing better angular support (i.e. content assist for actual values) but that requires more than we can safely include into a bugfix release

 

Another recurrent complaint is that the HTML validation considers Angular JS ng-* attributes as invalid html. This is actually correct since the proper syntax to be 100% compatible with the html5 spec is to use data-ng-* and if you disabled this rule you would loose warnings against you misspelling i.e. class as clas. This issue we can't fix in JBoss Tools alone thus we have submitted patches upstream to eclipse to allow you to choose to ignore ng-* and any other combination of attributes in your specific project. You can follow that here if you are interested.

 

 

Improved Hybrid Mobile (Cordova) tooling

 

The Hybrid Mobile tooling now supports Cordova 3. Gorkem put together a nice video of the Apache Cordova support provided by our Aerogear Hybrid tooling, demonstrating :

  • Project wizard
  • Native Device and Cordova simulators
  • Cordova plugins discovery and installation
  • Project export to native platforms

 

 

More OpenShift 2.0

Recent updates to OpenShift online and OpenShift Enterprise introduced the notion of user accounts having access to multiple domains. This is very useful if you are working together in a team and want to share access to your various applications.

The OpenShift tooling now fully supports multiple domains in the UI. These domains will show up in application creation and editing wizards and as shown below in the OpenShift Explorer.

multi-domain-in-explorer.png

other improvements include :

  • support for Environment Variables management
  • tailing logs of scaled applications

 


Giving Feedback

 

Please don't hesitate to use our forum to ask questions, or, if you have ideas to better improve JBoss Tools / Developer Studio, or found a bug, then open an issue in our issue tracker.

 

What's Next ?

 

Once we recover from all the end-of-year festivities, we'll resume our work on the next generation of JBoss Tools and Developer Studio, for Eclipse Luna.

 

Happy Holidays and remember to Have Fun

 

Fred Bricon & Max Rydahl Andersen

 

http://twitter.com/fbricon

 

http://twitter.com/maxandersen

We are getting closer to the final release - give this candidate release a spin.

 

https://community.jboss.org/servlet/JiveServlet/showImage/38-5273-21204/jbosstools-jbdevstudio-blog-header1.png

 

JBoss Tools 4.1.1.CR1 & Developer Studio 7.1.0.CR1

[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 subset of JBoss Tools including  a full Eclipse and other 3rd party plugins.

 

This update just contain bug fixes and workflow improvements based on issues reported against the previous Beta release

 

Installation

 

JBoss Developer Studio

 

You can download JBoss Developer Studio from our Early Access site. Use this if you just want an easy to install, but fully bundled Eclipse installation.

https://devstudio.jboss.com/earlyaccess/

 

JBoss Tools:

 

If you prefer JBoss Tools with individual plugin installation, you use this update site an install into your existing Eclipse Kepler install:

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

Note, if you already have this enabled you will get updates to your plugins via 'Help > Check for updates' but you will not get new plugins installed - thus if you don't have Cordova tooling installed already you need to use the 'Help > Install' menu to install it.

 

 

 

Giving Feedback

There are more news and screenshots in What's New, and if you have an idea to an improvement or found a bug do not hesitate to open an issue in our issue tracker.

 

What's Next ?

Final release is planned to happen before the holidays - Please try this release out and get your feedback in now

 

...and do not forget that Integration Stack is Back, giving you support for SOA related tech too - we got beta builds for that too here.

 

Have fun!

Max Rydahl Andersen

JBoss Tools Beta!

Posted by Max Rydahl Andersen Nov 11, 2013

Just in time for Devoxx I'm proud to announce another great Beta!

 

https://community.jboss.org/servlet/JiveServlet/showImage/38-5273-21204/jbosstools-jbdevstudio-blog-header1.png

 

JBoss Tools 4.1.1.Beta1 & Red Hat JBoss Developer Studio 7.1.0.Beta1

Moving clouds...

[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 subset of JBoss Tools including  a full Eclipse and other 3rd party plugins.

 

This update makes us feature complete for 4.1.1 release which incl. improvements to html5 editing, testing, Apache Cordova 3 support and big updates for OpenShift.

 

Installation

 

JBoss Developer Studio

 

You can download JBoss Developer Studio from our Early Access site. Use this if you just want an easy to install, but fully bundled Eclipse installation.

https://devstudio.jboss.com/earlyaccess/

For this Beta the Cordova Tooling is a separate install. In the future you will be able to install it directly from JBoss Central.

 

You install the Cordova Tooling from this update site for JBoss Developer Studio via "Help > Install":

https://devstudio.jboss.com/updates/7.0-development/

 

JBoss Tools:

 

If you prefer JBoss Tools with individual plugin installation, you use this update site an install into your existing Eclipse Kepler install:

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

Note, if you already have this enabled you will get updates to your plugins via 'Help > Check for updates' but you will not get new plugins installed - thus if you don't have Cordova tooling installed already you need to use the 'Help > Install' menu to install it.

 

Cordova Version 3

 

The Aerogear Hybrid tools and CordovaSim is now targeting Cordova 3.

cordovasim-cordova-3.png

 

Cordova Plugins

 

With Cordova 3 (almost) everything is a plugin, allowing you to just install/use the plugins you want for your application.

The Aerogear Hybrid tools now support these allowing you to install and remove plugins from a Hybrid project.

 

CordovaPluginDiscovery.png

 

Exporting Cordova Applications

 

The Aerogear Hybrid tools now has a wizard for creating binaries for your favorite platform (currently we support Android and iOS).

This allows you to deploy your application to a native device.

 

Furthermore you can now also export your hybrid project in source form for further editing as an Android (ADT project) or iOS (XCode).

ExportWizard.png

Simulating Touch

BrowserSim now supports simulating touch events making it possible to test features of your application that

only react to touch as opposed to traditional mouse/click/drag events.

 

touch-menu.png

 

OpenShift Domains

Recent updates to OpenShift introduced the notion of user accounts having access to multiple domains. This is very useful if you are working together in a team and want to share access to your various applications.

 

The OpenShift tooling now fully supports multiple domains in the UI. These domains will show up in application creation and editing wizards and as shown below in the OpenShift Explorer.

multi-domain-in-explorer.png

OpenShift Environment Variables

Environment variables for OpenShift applications allow to you to refer to variables in applications instead of hardcoded values - allowing for better reuse and setup flexibility for your application. OpenShift tools now allow you to specify the environment variables when creating applications and editing environment variables for existing applications (Note: depending on your application you might need to restart to see the effect of these edits).

 

environment-variables-wizard.png

 

This feature is really useful together with the option of using your own custom git repository for application creation,

which we introduced in a previous Alpha.

 

Tailing OpenShift Scaled Logs

With scaled applications, it can be challenging to monitor the multiple gears that can be running in parallel.

In Beta1, we are extending the current "Tail Logs" feature to allow you to select which cartridges you want to monitor:

tail-log-files-multiple-gears.png

And when these Cartridges contain multiple gears, you will get a console log view for each of the gears which

you can toggle between or simply close everything except that one node you want to track.

multiple-consoles.png

 

Giving Feedback

There are more news and screenshots in What's New, and if you have an idea to an improvement or found a bug do not hesitate to open an issue in our issue tracker.

 

What's Next ?

We plan on moving to Final on the next update which should just include bugfixes.

 

Please try this release out and get your feedback in Now

 

...and do not forget that Integration Stack is Back, giving you support for SOA related tech too - we got beta builds for that too here.

 

Have fun!

Earlier this month we posted Update to JBoss Tools 4.1 and Developer Studio 7.0 which was done to remedy some of the issues around a regression bug the _40 update to Java caused to Eclipse and hence our tools.

 

Last week Oracle released _45 update for Java 7 which fixes this issue and you should now be able to do updates and installs reliably again in Eclipse based tools.

 

Thanks to Oracle for the quick turnaround!

We are cooking on an update to JBoss Tools 4.1.

https://community.jboss.org/servlet/JiveServlet/showImage/38-5273-21204/jbosstools-jbdevstudio-blog-header1.png

 

JBoss Tools 4.1.1 Alpha2

One small step...

[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.

 

Currently we are preparing for doing some bugfixes incl. refresh the until now experimental Apache Cordova support as part of our Aerogear Hybrid tooling.

 

Installation

 

From within Eclipse Kepler you need to add the JBoss Tools Eclipse Kepler development updatesite:

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

Note, if you already have this enabled you will get updates to your plugins via 'Help > Check for updates' but you will not get new plugins installed - thus if you don't have for example the Cordova tooling installed already you need to use the 'Help > Install' menu instead.

 

Improvements

 

Alpha2 and the previous Alpha1 build are mainly about bugfixing and being ready to include the Cordova tooling into JBoss Developer Studio.

There are though a few new features included to make your life easier.

 

Resource content assist and file creation

There are now content assist on resources for things like script, img, source, anchors etc.

 

Alexey made a nice video of how it works you can watch here.

 

Furthermore if you type in a resource that does not exist the html editing tools now offer to create the resource for you, making it much easier to quickly create a set of linked resources.

 

CreateFileHyperlink.png

Angular.js attribute content assist

 

To aid in developing of Angular applications we've added content assist for ng-* attributes.

 

ng-ca.png

 

We are working on providing better angular support (i.e. content assist for actual values) but that requires more than we can safely include into a bugfix release

 

Another often complaint is that the validation of angular.js marks ng-* with warnings as invalid html. This is actually correct since the proper syntax to be 100% compatible with the html5 spec is to use data-ng-* and if you disabled this rule you would loose warnings against you misspelling i.e. class as clas. This issue we can't fix in JBoss Tools alone thus we have submitted patches upstream to eclipse to allow you to choose to ignore ng-* and any other combination of attributes in your specific project. You can follow that here if you are interested.

 

Giving Feedback

There are more news and screenshots in What's New, and if you got an idea to an improvement or found a bug do not hestiate to open an issue in our issue tracker.

 

What's Next ?

Next planned item is beta release which will include improvements to Cordova tooling and introduce it as part of JBoss Developer Studio.

Gorkem Ercan already started blogging about some of this at his blog here.

 

...and do not forget that Integration Stack is Back, giving you support for SOA related tech too - we got beta builds for that announced last week.

 

Have fun!

For a while we have not had a release of the Integration Stack tools for Drools, jbpm, esb, SwitchYard, Teiid etc. that was verified to work with the latest release of JBoss Tools and Red Hat JBoss Developer Studio. Today that is being fixed - at least with a Beta.

 

 

 

JBoss Tools Integration Stack 4.1.3.Beta4 and Developer Studio Integration Stack 7.0.0.Beta4

The Stack Is Back!

 

The Integration Stack for JBoss Tools & Developer Studio (formerly JBoss Tools & Developer Studio SOA Tooling) is a set of plugins for Eclipse that provides tooling for the following frameworks:

 

  • BPEL (via Riftsaw)
  • BPMN2 (via jBPM6)
  • Drools
  • Drools Guvnor
  • JBoss ESB
  • Fuse
  • jBPM3
  • jBPM6
  • Modeshape
  • Savara (JBoss Tools only)
  • SwitchYard
  • Teiid

 

All of these components are now delivered from an update site that has been tested and verified to work with the same dependencies as JBoss Tools and Developer Studio. Making installing them together easy and smooth.

 

Installation

 

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 installed, you can install JBoss Developer Studio or JBoss Tools from the Eclipse Marketplace via Help > Eclipse Marketplace...

 

Then launch Eclipse or JBoss Developer Studio, and select Help > Install New Software > https://devstudio.jboss.com/updates/7.0-development/integration-stack/

 

This will give you the beta release of what is going to be part of the supported version of the tools.

 

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

 

http://download.jboss.org/jbosstools/updates/development/kepler/integration-stack

 

News

 

Besides the great news of now having updated support for the previously available SOA Tooling, this release also brings two new components to the stack: Tooling for SwitchYard and Fuse.

 

SwitchYard is the replacement for JBoss ESB and is a component-based development framework focused on building structured, maintainable services and applications using the concepts and best practices of SOA.  The tooling provides wizard for setting up maven based SwitchYard projects, Configuration of SwitchYard capabilities (i.e. runtime component dependencies; e.g. SOAP, BPM, Apache Camel, etc.), graphical editor for switchyard.xml and more.

 

You can read more about the SwitchYard tooling here.

 

Fuse comes with tooling that enables you to work with Fuse and Apache versions of ActiveMQ, Camel, CXF, Karaf, and ServiceMix.  You can connect and configure Enterprise Integration Patterns to build routes, browse endpoints and routes, drag and drop messages onto running routes, trace message flows, edit running routes, browse and visualize runtime processes via JMX, and deploy your project's code to Red Hat JBoss Fuse and Fuse Fabric containers, to Apache ServiceMix, and to Apache Karaf.

 

You can read more about the Fuse Tooling here.

 

Thanks to the various component leads to make this happen and especially Paul Leacu , Rob Cernich and Nick Boldt for making the aggregation happen!

 

Let us know what you think and want next!

 

Have fun!

Oracle introduced a regression bug in their latest _40 release of their Java 7 JDK/JRE which unfortunately prevented installations of plugins from JBoss Central, Maven Connectors, Mylyn Connectors and other Eclipse.org plugins having a installation by discovery feature.

 

To reduce the impact of that we've released an update to JBoss Tools 4.1 and Developer Studio 7.0 that fixes this issue for JBoss Central.

 

JBoss Developer Studio 7.0.1 also provides updates to Kepler SR1 making sure you have the latest bug fixes from eclipse.org too.

 

This fix is available as an update by simply using 'Help > Check for Updates'.

 

Mind you that not all issues caused by Oracle's Java 7 release can be fixed easily thus even with this update we still recommend you use a previous Java version until Oracle releases an update to their JDK that fixes this issue.

 

Thank you!

Filter Blog

By date:
By tag: