JBoss Tools - Posts tagged with 'jbosscentral'

This article has been posted also on Red Hat Developers Program blog.

We are happy to announce the release of Red Hat JBoss Fuse Tooling for Eclipse Mars. It is available now in the JBoss Tools Integration Stack 4.3.2 / Developer Studio Integration Stack 9.0.2.

What’s in there?

Let me highlight the most important changes only. You can see a full list of changes in the What’s New section for the release.

New Fuse Integration Project wizard

One of our main objectives for this release was improving the usability and making the tooling easy to use. The project wizard was one of the things we wanted to improve. In the new version of the wizard you are now able to specify a runtime you want to develop for OR an Apache Camel version to be used from the list of supported versions.

Another improvement is the replacing of the archetype selection with a more user friendly list of project templates which are now more use case oriented. At the moment we have just a few templates available but we will add new templates in future. (see above screenshot)

Updated Visual Camel Editor

We are happy to show you the new Camel Editor :D

We’ve got a new diagram layout and new icons together with a search field inside the palette which allows easy lookup of palette items without the need to browse any drawers. The new layout improves the readability of your route. Another change has been made to allow showing all routes of a Camel Context file inside one editor. For those of you who liked the "only one route" approach more we added a "Go Into" button on the route’s button pad.

You maybe also recognized a new tab in the editor from the above screenshot. We added the "Configurations" tab which can be used to handle elements which are not part of the route itself, like beans, global endpoint definitions and data formats. At the moment we have support for handling global endpoints and data formats. If you installed the SAP Tool Suite you can also add SAP Server definitions. More types will be added in future releases.

For more information on this tab please have a look here.

Other

There have been some improvements in the validation of Camel files. Please have a look here for more information.

We hope you enjoy the improvements and are looking forward to your feedback. Have fun!

Lars Heinemann

Happy to announce 4.4.2.AM1 (Developer Milestone 1) build for Eclipse Neon.

Downloads available at JBoss Tools 4.4.2 AM1.

What is New?

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

OpenShift 3

Although our main focus is bug fixes, we continue to work on providing better experience for container based development in JBoss Tools and Developer Studio. Let’s go through a few interesting updates here and you can find more details on the What’s New page.

Cluster common namespace

When looking for Openshift resources (builder images, templates), a common namespace is browsed. Earlier hardcoded openshift namespace is now configurable with default value openshift.

Please note that templates are still loaded from the òpenshift namespace and not the from configured common namespace, this will be fixed for the next release.

It can be accessed and modified through the connection extended properties:

CDK server using native terminal for better user interactions

The CDK server adapter now uses a native terminal that allows better interaction with the user. In the case credentials are not passed in the Vagrant environment, the user will be asked just as with the standard Vagrant CLI and in case of registration failures, retries will be performed.

First, make sure your CDK server adapter is configured not to pass credentials:

Then, start the CDK server adapter and a new terminal window will open, asking for registration:

If you answered y to the previous questions, then the terminal window will ask for username:

Then the terminal window will ask for password:

If the registration fails, then the terminal window will perform retries and ask again for username and password:

Enjoy!

Jeff Maury

JBoss Tools 4.4.1 and Red Hat JBoss Developer Studio 10.1 for Eclipse Neon are here waiting for you. Check it out!

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.6 (Neon) but we recommend using the latest Eclipse 4.6 Neon 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 "Red Hat JBoss Developer Studio".

For JBoss Tools, you can also use our update site directly.

http://download.jboss.org/jbosstools/neon/stable/updates/

What is new?

Our main focus for this release was improvements for container based development and bug fixing.

Improved OpenShift 3 and Docker Tools

We continue to work on providing better experience for container based development in JBoss Tools and Developer Studio. Let’s go through a few interesting updates here.

Support for Container Labels

Users can now specify labels when running a container. The labels are saved in the launch configuration and can also be edited before relaunching the container.

Automatically detect known Docker daemon connections

When the Docker Explorer view is opened, the list of existing connections (saved from a previous session) is reloaded. In addition to this behaviour, the view will also attempt to find new connections using default settings such the 'unix:///var/run/docker.sock' Unix socket or the 'DOCKER_HOST', 'DOCKER_CERT_PATH' and 'DOCKER_TLS_VERIFY' environment variables. This means that by default, in a new workspace, if a Docker daemon is reachable using one of those methods, the user does not have to use the "New Connection" wizard to get a connection.

Extension point for Docker daemon connection settings

An extension point has been added to the Docker core plugin to allow for custom connection settings provisionning.

Support for Docker Compose

Support for Docker Compose has finally landed !

Users can select a docker-compose.yml file and start Docker Compose from the context menu, using the Run > Docker Compose launcher shortcut.

The Docker Compose process displays it logs (with support for text coloring based on ANSI escape codes) and provides a stop button to stop the underlying process.

Also, as with the support for building and running containers, a launch configuration is created after the first call to Docker Compose on the selected docker-compose.yml file.

Docker Image Hierarchy View Improvements

The new Docker Image Hierarchy view not only shows the relationships between images (which is particularly interesting when an image is built using a Dockerfile), but it also includes containers based on the images in the tree view while providing with all relevant commands (in the context menu) for containers and images.

Server templates can now be displayed / edited

Server templates are now displayed in the property view under the Templates tab:

You can access/edit the content of the template with the Edit command.

Events can now be displayed

Events generated as part of the application livecycle are now displayed in the property view under the Events tab (available at the project level):

You can refresh the content of the event with the Refresh command or open the event in the OpenShift web console with the Show In → Web Console command.

Volume claims can now be displayed

Volume claims are now displayed in the property view under the Storage tab (available at the project level):

You can create a new volume claim using a resource file like the following:

{
    "apiVersion": "v1",
    "kind": "PersistentVolumeClaim",
    "metadata": {
        "name": "claim1"
    },
    "spec": {
        "accessModes": [ "ReadWriteOnce" ],
        "resources": {
            "requests": {
                "storage": "1Gi"
            }
        }
    }
}

If you deploy such a resource file with the New → Resource command at the project level, the Storage tab will be updated:

You can access/edit the content of the volume claim with the Edit command or open the volume claim in the OpenShift web console with the Show In → Web Console command.

Server Tools

QuickFixes now available in runtime detection

Runtime detection has been a feature of JBossTools for a long while, however, it would sometimes create runtime and server adapters with configuration errors without alerting the user. Now, the user will have an opportunity to execute quickfixes before completing the creation of their runtimes and servers.

To see this in action, we can first open up the runtime-detection preference page. We can see that our runtime-detection will automatically search three paths for valid runtimes of any type.

Once we click search, the runtime-detection’s search dialog appears, with results it has found. In this case, it has located an EAP 6.4 and an EAP 7.0 installation. However, we can see that both have errors. If we click on the error column for the discovered EAP 7.0, the error is expanded, and we see that we’re missing a valid / compatible JRE. To fix the issue, we should click on this item.

When we click on the problem for EAP 7, the new JRE dialog appears, allowing us to add a compatible JRE. The dialog helpfully informs us of what the restrictions are for this specific runtime. In this case, we’re asked to define a JRE with a minimum version of Java-8.

If we continue along with the process by locating and adding a Java 8 JRE, as shown above, and finish the dialog, we’ll see that all the errors will disappear for both runtimes. In this example, the EAP 6.4 required a JRE of Java 7 or higher. The addition of the Java 8 JRE fixed this issue as well.

Hopefully, this will help users preemptively discover and fix errors before being hit with surprising errors when trying to use the created server adapters.

Support for WildFly 10.1

The WildFly 10.0 Server adapter has been renamed to WildFly 10.x. It has been tested and verified to work for WildFly 10.1 installations.

Hibernate Tools

Hibernate Runtime Provider Updates

A number of additions and updates have been performed on the available Hibernate runtime providers.

New Hibernate 5.2 Runtime Provider

With final releases available in the Hibernate 5.2 stream, the time was right to make available a corresponding Hibernate 5.2 runtime provider. This runtime provider incorporates Hibernate Core version 5.2.2.Final and Hibernate Tools version 5.2.0.Beta1.

Figure 1. Hibernate 5.2 is available

Other Runtime Provider Updates

The Hibernate 4.3 runtime provider now incorporates Hibernate Core version 4.3.11.Final and Hibernate Tools version 4.3.5.Final.

The Hibernate 5.0 runtime provider now incorporates Hibernate Core version 5.0.10.Final and Hibernate Tools version 5.0.2.Final.

The Hibernate 5.1 runtime provider now incorporates Hibernate Core version 5.1.1.Final and Hibernate Tools version 5.1.0.CR1.

Forge Tools

Added Install addon from the catalog command

From Forge 3.3.0.Final onwards it is now possible to query and install addons listed in the Forge addons page.

Forge Runtime updated to 3.3.1.Final

The included Forge runtime is now 3.3.1.Final. Read the official announcement here.

Freemarker

Freemarker 2.3.25

Freemarker library included in the Freemarker IDE was updated to latest available version 2.3.25.

flth / fltx file extensions added

The new flth and fltx extensions have been added and associated with Freemarker IDE. flth stands for HTML content whereas fltx stands for XML content.

Overhaul of the plugin template parser

The parser that FreeMarker IDE uses to extract IDE-centric information (needed for syntax highlighting, related tag highlighting, auto-completion, outline view, etc.) was overhauled. Several bugs were fixed, and support for the newer template language features were added. Also, the syntax highlighting is now more detailed inside expressions.

Fixed the issue when the (by default) yellow highlighting of the related FTL tags shift away from under the tag as you type.

Showing whitespace, block selection mode

The standard "Show whitespace characters" and "Toggle block selection mode" icons are now available when editing a template.

Improved automatic finishing of FreeMarker constructs

When you type <#, <@, ${, #{ and <#-- the freemarker editor now automatically closes them.

Error positions links on the console

When a FreeMarker exception is printed to the console, the error position in it is a link that navigates to the error. This has worked long ago, but was broken for quite a while.

Fixed auto-indentation

When hitting enter, sometimes the new line haven’t inherited the indentation of the last line.

Updated the "database" used for auto completion

Auto completion now knows all directives and "built-ins" up to FreeMarker 2.3.25.

What is next?

Having JBoss Tools 4.4.1 and Developer Studio 10.1 out we are already working on the next maintenance release for Eclipse Neon.1.

Enjoy!

Jeff Maury

Happy to announce AM3 (Developer Milestone 3) build for Eclipse Neon.

Downloads available at JBoss Tools 4.4.1 AM3.

A late bug has been discovered in the Docker Tools on the Windows platform. It prevents the Docker Explorer to be displayed and affects also Openshift users. This will be fixed in the next release of JBoss Tools. A workaround exists: after you install JBoss Tools, restart your Eclipse and run Help > Install new software > Work with: http://download.eclipse.org/linuxtools/updates-docker-nightly/ > select Docker Tooling > install. Restart when prompted.

What is New?

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

OpenShift 3

Although our main focus is bug fixes, we continue to work on providing better experience for container based development in JBoss Tools and Developer Studio. Let’s go through a few interesting updates here and you can find more details on the What’s New page.

Events

Events generated as part of the application livecycle are now displayed in the property view under the Events tab (available at the project level):

Volume claims

Volume claims are now displayed in the property view under the Storage tab (available at the project level):

Here is a short video which demonstrates these new features:

Docker Tools

Support for Container Labels

Users can now specify labels when running a container. The labels are saved in the launch configuration and can also be edited before relaunching the container.

Docker Hierarchy View

The new Docker Image Hierarchy view lets the user view the layers for a selected image in the Docker Explorer View. This is especially interesting when an image was built locally, as it helps understanding on which layers the top-level image depends.

Automatically detect known Docker daemon connections

When the Docker Explorer view is opened, the list of existing connections (saved from a previous session) is reloaded. In addition to this behaviour, the view will also attempt to find new connections using default settings such the 'unix:///var/run/docker.sock' Unix socket or the 'DOCKER_HOST', 'DOCKER_CERT_PATH' and 'DOCKER_TLS_VERIFY' environment variables. This means that by default, in a new workspace, if a Docker daemon is reachable using one of those methods, the user does not have to use the "New Connection" wizard to get a connection.

Extension point for Docker daemon connection settings

An extension point has been added to the Docker core plugin to allow for custom connection settings provisionning.

Server Tools

QuickFixes now available in runtime detection

Runtime detection has been a feature of JBossTools for a long while, however, it would sometimes create runtime and server adapters with configuration errors without alerting the user. Now, the user will have an opportunity to execute quickfixes before completing the creation of their runtimes and servers.

To see this in action, we can first open up the runtime-detection preference page. We can see that our runtime-detection will automatically search three paths for valid runtimes of any type.

Once we click search, the runtime-detection’s search dialog appears, with results it has found. In this case, it has located an EAP 6.4 and an EAP 7.0 installation. However, we can see that both have errors. If we click on the error column for the discovered EAP 7.0, the error is expanded, and we see that we’re missing a valid / compatible JRE. To fix the issue, we should click on this item.

When we click on the problem for EAP 7, the new JRE dialog appears, allowing us to add a compatible JRE. The dialog helpfully informs us of what the restrictions are for this specific runtime. In this case, we’re asked to define a JRE with a minimum version of Java-8.

If we continue along with the process by locating and adding a Java 8 JRE, as shown above, and finish the dialog, we’ll see that all the errors will disappear for both runtimes. In this example, the EAP 6.4 required a JRE of Java 7 or higher. The addition of the Java 8 JRE fixed this issue as well.

Hopefully, this will help users preemptively discover and fix errors before being hit with surprising errors when trying to use the created server adapters.

Forge

Forge Runtime updated to 3.3.0.Final

The included Forge runtime is now 3.3.0.Final. Read the official announcement here.

Added Install addon from the catalog command

From Forge 3.3.0.Final onwards it is now possible to query and install addons listed in the Forge addons page.

Freemarker

Improved automatic finishing of FreeMarker constructs

When you type <#, <@, ${, #{ and <#-- the freemarker editor now automatically close them.

Enjoy!

Jeff Maury

Try our complete Eclipse-Mars capable, JBDS 9.1.0 compatible integration tooling.

JBoss Tools Integration Stack

Since JBoss Tools 4.3.0 we require Java 8 for the installation and use of all JBoss Tools, including the Integration Stack tooling. We still support developing and running applications using older Java runtimes. See more in Beta1 blog.

JBoss Tools Integration Stack 4.3.1.Final / JBoss Developer Studio Integration Stack 9.0.1.GA

What’s an Integration Stack?

The Integration Stack for JBoss Developer Studio is a set of features and plugins for Eclipse that further enhances the IDE development functionality provided by JBoss Developer Studio in support of the following frameworks:

All of the Integratioon Stack components have been verified to work with the same dependencies as JBoss Tools 4.3 and Developer Studio 9.

JBoss Fuse Development

Fuse Tooling - JBoss Fuse Development provides tooling for Red Hat JBoss Fuse. It features the latest versions of the Fuse Data Transformation tooling, SwitchYard and access to the Fuse SAP Tool Suite.
SwitchYard - A lightweight service delivery framework providing full lifecycle support for developing, deploying, and managing service-oriented applications.

JBoss Business Process and Rules Development

JBoss Business Process and Rules Development plug-ins provide design, debug and testing tooling for developing business processes for Red Hat JBoss BRMS and Red Hat JBoss BPM Suite.

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 including KIE.
jBPM6 - A flexible Business Process Management (BPM) suite.

JBoss Data Virtualization Development

JBoss Data Virtualization Development plug-ins provide a graphical interface to manage various aspects of Red Hat JBoss Data Virtualization instances, including the ability to design virtual databases and interact with associated governance repositories.

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

ModeShape is deprecated.

JBoss Integration and SOA Development

JBoss Integration and SOA Development plug-ins provide tooling for developing, configuring and deploying BRMS, SwitchYard and Fuse applications to Red Hat JBoss Fuse Service Works, Red Hat JBoss Fuse and Fuse Fabric containers, Apache ServiceMix, and Apache Karaf instances.

All of the Business Process and Rules Development plugins, plus…
Fuse Apache Camel Tooling - A graphical tool for integrating software components that works with Apache ServiceMix, Apache ActiveMQ, Apache Camel and the FuseSource distributions.
SwitchYard - A lightweight service delivery framework providing full lifecycle support for developing, deploying, and managing service-oriented applications.

SOA 5.x Development

Please note that the plugins in this category have been deprecated.

JBoss ESB - An enterprise service bus for connecting enterprise applications and services.
jBPM3 - A flexible Business Process Management (BPM) Suite - JBoss Enterprise SOA Platform 5.3.x compatible version.

What’s Been Updated for this release?

The highlight of this release is tooling support for JBoss Data Virtualization 6.3.0 on Eclipse Mars with Teiid Designer. In addition a new spin of an Early Access version of Fuse Tooling is available.

Released Tooling Highlights

Data Virtualization Highlights

Teiid Designer Highlights

See the Teiid Designer 10.0.1.Final Release Notes

SOA 5.x Development

JBoss ESB, jBPM3 and guvnor. These tools have been deprecated.

Early Access Tooling Highlights

JBoss Fuse Development Highlights

Fuse Tooling Highlights

See the Fuse Tooling 8.0.0.Beta4 Release Notes

The JBoss Tools website features tab

Don’t miss the Features tab for up to date information on your favorite Integration Stack components.

Installation

The easiest way to install the Integration Stack components is to first install JBoss Tools 4.3.1 or JBoss Developer Studio 9.1.0 and then select the Software/Update tab in the JBoss Central view. Select the 'Enable Early Access' checkbox.

For a complete set of Integration Stack installation instructions, see Integration Stack Installation Instructions

Try it out!

Paul Leacu.

Happy to announce AM2 (Developer Milestone 2) build for Eclipse Neon.

Downloads available at JBoss Tools 4.4.1 AM2.

What is New?

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

OpenShift 3

Although our main focus is bug fixes, we continue to work on providing better experience for container based development in JBoss Tools and Developer Studio. Let’s go through a few interesting updates here and you can find more details on the What’s New page.

Server templates

Server templates are now displayed in the property view under the Templates tab:

Forge

Forge Runtime updated to 3.2.3.Final

The included Forge runtime is now 3.2.3.Final. Read the official announcement here.

Freemarker

Freemarker 2.3.25

Freemarker library included in the Freemarker IDE was updated to latest available version 2.3.25.

Related JIRA: JBIDE-22700

flth / fltx file extensions added

The new flth and fltx extensions have been added and associated with Freemarker IDE. flth stands for HTML content whereas fltx stands for XML content.

Related JIRA: JBIDE-22636

Enjoy!

Jeff Maury

JBoss Tools 4.4 and Red Hat JBoss Developer Studio 10.0 for Eclipse Neon are here waiting for you. Check it out!

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.6 (Neon) but we recommend using the latest Eclipse 4.6 Neon 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 "Red Hat JBoss Developer Studio".

For JBoss Tools, you can also use our update site directly.

http://download.jboss.org/jbosstools/neon/stable/updates/

What is new?

Our main focus for this release was on adoption of Eclipse Neon, improvements for container based development and bug fixing. Eclipse Neon itself has a lot of new cool stuff but let me highlight just a few updates in both Eclipse Neon and JBoss Tools plugins that I think are worth mentioning.

JavaScript Development Tools 2.0

Red Hat team along with other contributers have been working hard for the last months on restarting JavaScript Development Tools (JSDT) project for Eclipse Neon. The updated tooling includes EcmaScript 2015 support, JSON editor, Node.js, grunt, gulp, bower and npm tools.

Here is a short video which demonstrates new features and enhancements of JavaScript Tools:

Improved OpenShift 3 and Docker Tools

We continue to work on providing better experience for container based development in JBoss Tools and Developer Studio. Let’s go through a few interesting updates here and you can find more details on the What’s New page.

Dockerfile Editor

The new Dockerfile editor provides users with content assist on the commands (ADD, COPY, RUN, etc.) as well as a customizable syntax highlighting.

Deploy docker images to the CDK OpenShift registry

The New OpenShift Connection wizard supports setting a Docker registry URL in the advanced properties section. This allows you to push docker images to the given Docker registry via the Deploy Docker Image wizard, right before actually creating the OpenShift resources. The URL is automatically added if the connection has been created by the CDK server adapter.

New support for builder images

The New OpenShift Application wizard now supports builder images, on top of the existing template support.

Compared to regular templates, with the builder image-based workflow, users will be able to define:

git source url
build triggers
environment variables
data volumes
replicas
exposed service ports and routes

Create new resources

The OpenShift Explorer provides a New > Resource menu, that lets you create new OpenShift resources from an existing file, similar to the oc create -f some_resource.json command. Resource files can be local (from File System or Workspace), or remote, by providing a URL.

Scaling pods

It is possible to scale pods up and down, from the Service context menu in the OpenShift Explorer, or the Deployments and Deployment Configuration context menus in the Properties view.

New EAP 7 quickstarts

Red Hat Central now lists quickstarts targeting the newly released Red Hat JBoss Enterprise Application 7.0 server.

And more…

You can find more noteworthy updates in on this page.

What is next?

Having JBoss Tools 4.4 and Developer Studio 10.0 out we are already working on the next maintenance release for Eclipse Neon.

Enjoy!

Alexey Kazakov

To celebrate the release of Eclipse Neon, the Eclipse Foundation produced a webinar series with a list of 7 of the Top New & Noteworthy Features that are integral to the Eclipse Neon Release.

Amongst those webinars, Ilya and Gorkem presented the Eclipse JavaScript Development Tools (JSDT) and I presented the Docker tooling.

JSDT Tooling

Description:

The Eclipse JavaScript Development Tools have reached a new level of features and usability with Eclipse Neon. Many things were implemented as part of the JSDT 2.0 release that is now available with Eclipse Neon. This webinar demonstrates the following new features:

Package managers (npm / bower)
Build systems (grunt / gulp)
Node.js Tools
ECMAScript 2015 (ES6) parser

The talk also features plans for the future of JavaScript development in Eclipse IDE.

The slides for the presentation are available here.

Docker Tooling

Description:

Docker is awesome, but how to use it well when doing development? In this talk you will get a quick introduction on how to use Docker effectively, especially for development from within Eclipse. We will show how the release of Eclipse Neon supports Docker to make it even more integrated into your day-to-day work from within your IDE. In particular, you’ll see how you can pull and run an image for a database, build a custom image for an application server, run it and deploy an application using data volume, exposed ports and container links. We will also take a look at some of the newest features, such as support for Docker Machine, TM Terminal integration, run configurations for containers, and a variety of other UI improvements.

The slides for the presentation are available here.

Other Webinars

Other webinars have also been recorded and are available on the Eclipse Neon Webinar Series on Youtube.

Enjoy !
Xavier Coulon
@xcoulon

Note: This article has been posted also on Red Hat Developers Program blog

As I mentioned in this earlier post, the 8.0.0.Beta2 version of JBoss Fuse Tooling is available. In this article I will cover another new and updated feature: validations. I will explain what was already available and what’s new which improves productivity.

Existing

In Fuse Camel Editor, the classic XML editor is used in the source tab. Consequently, we can rely on the Eclipse built-in validation of xml files against xsd. You just have to right-click on the source code, then Validate.

validation XSD

There was a limitation about blueprint, I let you check this issue report in case the validation doesn’t work for you in previous versions: FUSETOOLS-1653.

Improved and New

Fuse validation everywhere

Going further than the xsd validation, the Fuse validation validates some characteristics of the component URI. This validation reports Problem markers against the Camel Component. This kind of validation was already available through Properties view but there was no global vision of these issues.

You can now see markers in:

Project explorer
Camel Route Diagram
Tree nodes for Global configuration element
Source tab editor
Problems view

validationEverywhere validationOnXmlFile

Jump from Problems view

When double-clicking on Fuse Validation error in Problems view, you are redirected to the correct Editor tab depending on which specific Camel element the error comes from.

For the xsd validation, you are redirected to the source editor.

Happy to announce Alpha2 build for Eclipse Neon M7.

Downloads available at JBoss Tools 4.4.0.Alpha2.

Installation

This version of JBoss Tools targets Eclipse Neon 4.6 (M7).

We recommend using the Eclipse 4.6 JEE Bundle since then you get most of the dependencies preinstalled.

Once you have installed Eclipse, you use our update site directly:

http://download.jboss.org/jbosstools/neon/development/updates/core/

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

What is new ?

As always there is more than can be covered in a single blog but here are some highlights. You can see everything in the What’s New section for this release.

Dockerfile Editor

A new Dockerfile editor provides users with content assist on the commands (ADD, COPY, RUN, etc.) as well as a customizable syntax highlighting.

Improved OpenShift 3 support

New support for builder images

The New OpenShift Application wizard now supports builder images, on top of the existing template support:

Create new resources

The OpenShift Explorer now provides a New > Resource menu, that lets you create new OpenShift resources from an existing file, similar to the oc create -f some_resource.json command. Resource files can be local (from File System or Workspace), or remote, by providing a URL.

Scaling pods

It is now possible to scale pods up and down, from the Service context menu in the OpenShift Explorer, or the Deployments and Deployment Configuration context menus in the Properties view. Scale > Up will spin up one more pod, Scale > Down will remove one pod. Scale > To… will open a pop-up dialog to let you set the amount of pods you want your OpenShift to spin up.

Updated JavaScript Tools

Our team worked hard for last month on rebooting the JavaScript Development Tools (JSDT) project which is part of Eclipse Web Tools. You can install updated JavaScript tooling directly from eclipse.org or using JBoss Tools Target Platform.

JavaScript Tools now support EcmaScript 2015. No false positive validation errors any more. Performance has been improved dramatically.

Node.js support now allows you to run and debug Node.js applications. Note: Node.js debugger is currently not available in JBoss Tools Target Platform and has to be installed directly from eclipse.org. It will be available in the next JBoss Tools version and will work OOTB in Developer Studio.

Here is a short video which demonstrates new features and enhancements of JSDT 2.0 release:

Next steps

While we wait for feedback on Alpha2, we are already working on the next JBoss Tools release for Eclipse Neon.

Enjoy!

Alexey Kazakov

Posts tagged with 'jbosscentral'

What’s in there?

New Fuse Integration Project wizard

Updated Visual Camel Editor

Other

What is New?

OpenShift 3

Cluster common namespace

CDK server using native terminal for better user interactions

Installation

What is new?

Improved OpenShift 3 and Docker Tools

Support for Container Labels

Automatically detect known Docker daemon connections

Extension point for Docker daemon connection settings

Support for Docker Compose

Docker Image Hierarchy View Improvements

Server templates can now be displayed / edited

Events can now be displayed

Volume claims can now be displayed

Server Tools

QuickFixes now available in runtime detection

Support for WildFly 10.1

Hibernate Tools

Hibernate Runtime Provider Updates

New Hibernate 5.2 Runtime Provider

Other Runtime Provider Updates

Forge Tools

Added Install addon from the catalog command

Forge Runtime updated to 3.3.1.Final

Freemarker

Freemarker 2.3.25

flth / fltx file extensions added

Overhaul of the plugin template parser

Related tag background highlighting fixed

Showing whitespace, block selection mode

Improved automatic finishing of FreeMarker constructs

Error positions links on the console

Fixed auto-indentation

Updated the "database" used for auto completion

What is next?

What is New?

OpenShift 3

Events

Volume claims

Docker Tools

Support for Container Labels

Docker Hierarchy View

Automatically detect known Docker daemon connections

Extension point for Docker daemon connection settings

Server Tools

QuickFixes now available in runtime detection

Forge

Forge Runtime updated to 3.3.0.Final

Added Install addon from the catalog command

Freemarker

Improved automatic finishing of FreeMarker constructs

What’s an Integration Stack?

JBoss Fuse Development

JBoss Business Process and Rules Development

JBoss Data Virtualization Development

JBoss Integration and SOA Development

SOA 5.x Development

What’s Been Updated for this release?

Released Tooling Highlights

Data Virtualization Highlights

Teiid Designer Highlights

SOA 5.x Development

Early Access Tooling Highlights

JBoss Fuse Development Highlights

Fuse Tooling Highlights

The JBoss Tools website features tab

Installation

What is New?

OpenShift 3

Server templates

Forge

Forge Runtime updated to 3.2.3.Final

Freemarker

Freemarker 2.3.25

And more…