A JBoss Project
Red Hat

Posts tagged with 'jbosscentral'

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

The JavaEE part of the Tools now contains support for JSR-352 batch files. I’d like to show you the main features of the new visual editor available in JBoss Tools 4.3 and Developer Studio 9.

It extends the tree-form editor previously developed by the JBoss Tools team. There are now 3 ways to edit the batch XML files, represented by the 3 editor tabs:

  • Source (XML text editor)

  • Design (tree-form editor)

  • Diagram (visual editor)

Visual Editor for JEE Batch

Focus on Structure

The goal of the Diagram tab is to visualize the flowchart-like structure of batch jobs. Don’t bother editing the XML by hand and tracking down paths in your batch’s workflow. Instead, you can manipulate batch elements directly with your mouse.

Just select the proper objects from the palette, place them in the diagram and draw transitions among them. The editor visualizes all step, flow, split and decision elements, transitions using next attribute and next on elements and also terminating elements (fail, stop, end). If you need to edit elements nested inside a flow, just double-click its icon to switch the contents of the editor to the flow internals.

You also don’t need to reorder XML elements to set an element as a start. Just use Set as Start action.

Properties View

The diagram is useful for displaying structures but sometimes we would like to different things like to assign a Java bean to a batchlet. That’s when the Properties View comes in handy. Its content is changed according the current selection in the diagram and it serves for filling in various form data.

Properties View

Tip: Use Ctrl+Space to get content proposal.

Edit Anywhere

The diagram editor is integrated with the tree-form editor and the XML text editor in the way that all changes are propagated immediately between these three views. Use any of the editor tabs and you’ll see the changes reflected in the other tabs.

Content Assist

The editor is aware of the batch nature of your project and provides content proposal. It helps to fill in names batch artifacts such as jobs or flows, specific Java classes (your subclasses of ItemReader ItemWriter etc.) or exception classes. You may refer to your beans also by their name defined by the @Named annotation.

Get It Now

Just download the latest 9 release of JBoss Developer Studio or 4.3 version of JBoss Tools to get started. To quickly create a new file, try e.g. the wizard for creating batch files by selecting File ▸ New ▸ Other ▸ Batch ▸ Batch Job XML File.

Enjoy using the editor and give us some feedback!

Tomáš Milata
@tomas_milata

JBoss Fuse Tooling plus an updated Teiid Designer and Early Access versions of the Fuse SAP Tool Suite, Fuse Data Transformation tooling and SwitchYard (Luna/JBoss Developer Studio 8).

jbosstools jbdevstudio blog header
JBoss Tools Integration Stack 4.2.2.Final / JBoss Developer Studio Integration Stack 8.0.2.GA

What’s an Integration Stack?

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

JBoss Fuse Development

  • Fuse Tooling - Tools related to integrating and developing software components that work with Apache ServiceMix, ActiveMQ and Camel - support for Fuse.

The Fuse Development tooling category has both released and early access components. Consequently, you will see it in both the release installation dialog and the early access installation dialog.

JBoss Business Process and Rules Development

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

  • jBPM - A flexible Business Process Management (BPM) suite.

JBoss Data Virtualization Development

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

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

JBoss Integration and SOA Development

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

The SOA Development tooling category has both released and early access components. Consequently, you will see it in both the release install dialog and the early access install dialog.

SOA 5.x Development

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

All of these components have been verified to work with the same dependencies as JBoss Tools 4.2 and Developer Studio 8.

What’s Been Updated?

Updates have been made to the Business Process tooling, Fuse Tooling, Data Virtualization and SwitchYard. See the Integration Stack 8.0.2 Release Notes

Released Tooling Highlights

JBoss Fuse Development Highlights

  • New projects can now be given an arbitrary name. Previously, artifactId was used as the project name without the possibility to alter it.

  • JMX Navigator has been moved to JBoss Core and reworked. It now contains 3 categories: Local Processes, Server Connections, and User-Defined Connections.

  • Camel Debugger has been added. It allows to set, edit and remove breakpoints in the Design view. Camel 2.12 or higher is required for this functionality.

  • The Servers view now provides access to JMX when the server is running. Fuse-specific nodes are now also visible in the Servers view.

  • New and reworked server adapters have been added for Apache Karaf, Apache ServiceMix, and JBoss Fuse.

  • The previous deployment mechanism using hotfolder, JMX node and fabric8 nodes has been replaced by a publishing logic in the Servers view.

  • Project running on a server are now automatically redeployed when changed locally.

  • The Servers view now shows deployed projects and their bundle state.

  • The deploy, redeploy and undeploy operations are now all done in the Servers view.

  • Server credentials are now stored in the Eclipse secure storage.

  • A new editor palette drawer has been added for the most frequently used Camel components.

  • New custom component properties pages have been added.

  • Fabric8 tooling is now DEPRECATED and will be removed with the release of Fuse Tooling 8.0.0 (released in sync with JBoss Fuse 7.0.0).

BPMN2 Modeler Highlights

Teiid Designer Highlights

Early Access/ Technical Preview Tooling Highlights

Fuse Tooling Highlights

  • The new SAP Tool Suite enables integration of Camel routes with a remote SAP application server. The suite consists of ten components that support Remote Function Calls (RFC) and transmission of Intermediate Documents (IDocs).

  • The new Data Transformation tooling provides a GUI to assist users in implementing data translations as part of Camel routes.

Also see Lars Heinemann’s Blog for more Fuse Tooling insights.

SwitchYard Highlights

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 Integratin Stack components is to install JBoss Developer Studio Integration Stack from the Eclipse Marketplace via Help > Eclipse Marketplace…​

Eclipse Marketplace - JBoss Developer Studio Integration Stack

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

More to come…​

Paul Leacu.

The current Docker tooling for Eclipse does not support Docker 1.7.1. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=473743 for more information.

Last week at DevNation I had the chance to show some of the cool features that we provide in JBoss Developer Studio, including the Docker tooling that we’ve built for Eclipse Mars and that was released last week[1].

I also recorded a screencast that highlights some of those Docker tooling features. The video shows how to:

  • Connect to a local Docker engine (0:32)

  • Start a PostgreSQL container with a custom username and password (1:52)

  • Build a custom image for Wildfly to include the PostgreSQL JDBC driver and configure a datasource (3:20)

  • Start a WildFly container linked to PostgreSQL, with exposed ports and a volume mounted on the host machine (6:44)

  • Import a Quickstart project using JBoss Central (8:30)

  • Deploy the project on the WildFly container using a Server Adapter with custom settings (9:55)

  • Connect to the JVM using the Remote Debugging tools (13:25)

I commented all the tasks as I recorded this screencast to highlight the important steps. Beware that if you run 'boot2docker', you’ll need to use a specific IP address instead of 'localhost' when creating the Server adapter in Eclipse (trust me, I made this mistake before…​)..

The dockerfile and its associated resources (module.xml, standalone.xml and JDBC driver) used during the demo is available on GitHub, so feel free to clone the repo and play with it ;-)

Keep in mind that some wizards showed in this screencast may be refactored in the near future, as we target Eclipse Mars SR1 at the end of September for a more complete version of the Docker tooling.

Feel free to discuss features and report bugs with us on the Docker component of Linux Tools at Eclipse.org. As usual, feedback is welcome!

Enjoy!
Xavier Coulon
@xcoulon


1 Docker tooling is part of Developer Studio since version 9.0.0.Beta1 and JBoss Tools users can install it from Eclipse Marketplace or from our Update site

Eclipse Mars has arrived, and with it comes a brand new Docker tooling for it.

This blog is a cross-post from Eclipse Newsletter: Landed On MARS where you can read about more things included in recent released Eclipse Mars.

Goals

We wanted to have a way to easily start/stop and deploy Docker containers directly from Eclipse.

We wanted something that would run on all three major platforms: Windows, Linux and OS X.

We wanted something that would work together with existing Docker command line tools, but also utilized provide better overview and easier/faster access to common operations, from a visual perspective.

We wanted it to be released with Eclipse Mars.

…​and that is what we got now.

This article runs through how to get it installed, the main features and what the future plans are.

Where do I get it ?

With Eclipse Mars released, you can get it from the Eclipse Mars updatesite, the feature is named Docker Tooling.

If you want to try the latest greatest builds you can use Linux Tools project nightly builds update site at http://download.eclipse.org/linuxtools/updates-docker-nightly/

To use the plugins, it is assumed that Docker is already installed. You can see Docker’s Installation guide on how to do this on various platforms.

Views and Perspectives

Once you have installed the Docker tooling, you will get access to three new views:

Docker Explorer

a tree view listing all connected Docker instances, with image and containers.

Docker Containers

a table view listing containers for selected Docker connection

Docker Images

a table view listing images available in the selected Docker connection

The easiest way to get to see these are by opening the Docker Tooling perspective.

Docker Tooling Perspective

In the screen above, the Docker tooling are connected to a locally running Docker deamon named boot2docker.

Connect

To configure this you click the Add Connection…​ button in the Docker Explorer view.

This will start a wizard that will try to detect your default Docker connection setup, dependent on your operating system.

Add Connection Wizard

In Linux it will use standard unix sockets and if on Windows or OSX, it will look for the following environment variables: DOCKER_HOST, DOCKER_TLS_VERIFY and DOCKER_CERT_PATH.

If neither of these are detectable, you can click Use custom connection settings and provide the connection info.

When you have the connection working you can get started using Docker images.

Pull individual images

To pull an image, you use the Pull Image in the Docker Image view.

Pull Image

Here, I’m simply pulling the jboss/wildfly image, a image amongst many available at http://hub.docker.com.

Run

To run the image, the easiest way is to right-click on the image in the Docker Explorer.

Run Image from Docker Explorer

Here, I’ve initially filtered the list to just show images matching wildfly and then using right-click to choose the Run Image…​ action.

Docker Run

From within this dialog you can also search in Docker Hub for other images by clicking Search…​.

Docker search

In this example, I’m only going to focus on running using the defaults, but in the Run Image wizard you can also configure ports, links, volumes, environment variables etc.

By default, we enable interactive and tty mode to allow you to interact with the docker container in the console (i.e. if the image asks for input).

When you click Finish, the container will start and show output in a Console and the Docker Containers view will show which ports are used.

Console

In here, the port at 8080 (the web server) is mapped to 32768 on the docker daemon.

To show this I just need to goto http://dockerhost:32768 to access it. dockerhost is the IP of the docker daemon.

Browse

Build

If you have a Dockerfile you can build it via the hammer icon on the Image view. This will start the Build wizard.

docker build

Once built, the image will show up and be possible to use for running.

Properties

You can view properties for all the various parts: connection, image and container, including getting a tree view of what docker inspect would show.

docker properties

Future

For Eclipse Mars we added all of the above base features and you can use it in your day-to-day work with Docker.

For Eclipse Mars SR1, we will work on getting some of the rough edges fixed, like 'Run' and 'Build' should be available in the context menu and not only in the views menu.

Work also started in Eclipse CDT to support using Docker images to build binaries for an OS other than the one you are running on. The vision for this would allow running on Windows or Mac, but target native deployment on multiple various Linux architectures.

Furthermore in JBoss Tools we are working on better integrating Docker with Eclipse server adapters, to ease deployment of your web applications to a Docker container. You can see how server deployment works with the current Docker tooling by leveraging docker volumes and remote deployment support.

If you have suggestions or find bugs, please open these in the Linux Tools project under Docker.

Have fun!

Max Rydahl Andersen
@maxandersen

I’m happy to announce that from today JBoss Tools 4.3 Beta1 and Developer Studio 9 Beta1 is available for download.

jbosstools jbdevstudio blog header

Java 8 to run Eclipse; older runtimes OK for builds/deployment

To use this Beta, you must run Eclipse with Java 8.

You can still target development for old Java versions though. Yes, you can still target your Java 1.4 projects :)

We are doing this because certain components of Eclipse Mars now require Java 8 (especially Sapphire) and according to our usage stats, Java 8 will have gained majority this year.

But we have not made JBoss Tools dependent on Java 8 yet, since we want to get feedback from users on whether requiring Java 8 will be a problem.

Let us know on our forum, or contact Red Hat support if this will be a problem for you to use it.

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 JEE Bundle since then you get most of the dependencies preinstalled. In case that page it not available check main eclipse download for the Mars release.

Once you have installed Eclipse, you can either find us on the Eclipse Marketplace under "JBoss Tools (Mars)" or "JBoss Developer Studio (Mars)".

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 ?

The full details of what is new is available on this page. Some highlights below.

New Shiny Central

JBoss Central has now been updated to be faster to load, less overloaded and give access to any project example from developer.jboss.org.

html5 central

Docker tooling

There is now tooling to connect to (multiple) Docker daemons which allows you to pull, build, start, stop, etc. Images and Containers.

docker explorer view

The Docker tooling is technically part of Eclipse Mars, but we wanted to make it easily available to all JBoss Tools users, so we included it into our updatesite. In future releases, we will add some specific JBoss Tools integrations for our server adapters and OpenShift - but for now, what is included are the vanilla Eclipse Mars Docker tools.

Visual Java EE 7 Batch

We’ve added a visual diagram editor for Java EE 7 Batch tooling. Allowing you to visualize and edit your batch flow:

diagram

Big thanks to Tomáš Milata who worked on this for his thesis and contributed the foundation for this functionality!

Below is a video of the highlights of the feature set:

OpenShift 3

OpenShift 3 now works with OAuth logins as well as basic authentication and there is now support for creating applications from OpenShift/Kubernetes templates.

create from template

Port Monitoring

JBoss server adapters now support port monitoring, allowing you to trace and inspect requests made to a server.

20150521 monitoring view

Experimental LaunchBar

The Eclipse CDT project created a new feature called the LaunchBar, allowing to easily run launch configurations. We’ve added experimental support for WTP server adapters (like JBoss server adapters) making them as easy to run as a Java app. Details here.

20150604 launchbar

Next steps

Let us know what you like/hate about the release and if you find issues, please open a ticket at our issue tracker.

Going from Beta1 to Beta2, we are focusing on reported issues and going for improving Docker, OpenShift, JavaScript and JavaEE related features.

Hope you enjoy it and remember…​

Have fun!

Max Rydahl Andersen
@maxandersen

The Fuse team are looking for an Eclipse Developer to primarily work on JBoss Tools Fuse tooling.

769fcbdf1939cbdf43002be6e4330e9c.936x690x1

If you are interested read the job description and apply.

If you are interested in hearing more ping me on mail or find me at EclipseCon France next week!

I’m happy to report that a few days ago the final paperwork around Red Hat upgrading their membership to Strategic Developer at Eclipse was completed and now announced at Eclipse.org.

What does this mean ?

Strategic Members are organizations that view Eclipse as a strategic platform and are investing developer and other resources to further develop Eclipse Foundation technologies. Strategic Developers commit to assign at least eight developers full time to develop Eclipse technology, lead Eclipse projects and contribute annual dues up to 250.000 $.

At Red Hat we already have more than eight developers doing development Eclipse technology, both at and around the base Eclipse distribution.

  • m2e-wtp

  • JavaScript Development Tools (JSDT)

  • vert.x

  • Linux Tools

  • Thym

  • BPMN2

  • BPEL

  • SWTBot

..and contributing to many more.

This work is used in our JBoss Tools project and two products: JBoss Developer Studio (Middleware) and Red Hat Developer Toolset (Linux Platform).

By upgrading to Strategic Developer we are confirming our continued support and commitement of resources to Eclipse, but also increasing our funding to be $250.000 annually.

Red Hat have an interest in Eclipse Foundation continues to thrive, and that its flagship, the Eclipse IDE and other opensource development tools and runtimes continues to evolve and improve.

Stepping down and up from the board

This announcement also means I’ll have to step down from the board as solutions member representative, but I’ll be joining again as Red Hat’s representative for their newly aquired Strategic Developer position.

I’m happy to have served and I’m looking forward to see which other solutions member will come join in on the board and bring Eclipse Foundation forward.

What next ?

We’ve been contributing and continue to help making Eclipse Mars a great release, together with the rest of the community. We are especially working on fixing GTK/SWT on Linux, making Docker support and looking at improving the Java Script Development tools. The latter I did a presentation at EclipseCon which provide some of ideas what we are working on.

By becoming strategic developer we also plan to be involved more in how Eclipse IP and Development process works and evolves. Something that become more important to make more effective for fast moving projects to feel better at home at Eclipse.

On top of that Eclipse have a lot of other areas going on which Red Hat are keeping our eye on - especially in the area of web IDE’s and Internet-of-things.

If you are interested in hearing more about this or have a suggestion please feel free to contact me by mail or leave a comment below!

Let’s Have fun!,
Max Rydahl Andersen
@maxandersen

Alpha 2 build for Eclipse Mars M6 is now available at Alpha2 download.

Installation

This version of JBoss Tools targets Eclipse Mars 4.5 (M6).

We recommend using the Eclipse 4.5 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/mars/development/updates/core/

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

What is new ?

Easy Import/Open of projects

We have included our incubation project at Eclipse that makes importing and opening of projects much easier than default Eclipse. No longer do you need to know or guess at which of many import wizards are the right one. With this you just use menu:File[Import Project from Folder], point it to a folder and it will auto-detect the type of project, imports ann configure it as best as it can.

easyimport filemenu

Once started it will recursively scan the selected folder and report which directories it found.

easyimport wizard

We included this incubation feature to get early feedback - please do give it a try and let us know if it works great or if we detected some projects "badly".

OpenShft v3

Our OpenShift integration now allow you to connect to OpenShift 3 in addition to the existing OpenShift 2 support.

connection wizard server type

Once connected you can browse the OpenShift/Kubernetes data for your application/projects.

view explorer v3

Note: OpenShift v3 is not available from openshift.com to try at this point in time. If you want to try use it you can follow the instructions at OpenShift Origin sample app.

Java EE 7 Batch wizards, content assist, validation and refactoring

In Alpha 1 we introduced support for Java EE 7 batch specification and now extending this support with a wizard, content assist, linked navigation, searching and refactoring of Batch elements.

validation

WildFly 9

We’ve added native WildFly 9 runtime detection and server support. You no longer need to use the WildFly 8 adapter and detection will work correctly now.

Content assist for AngularJS Expressions

When editing AngularJS single-page html (not templates) the html editor now communicates with the preview to provide content assist for angularjs expressions.

angular

Custom HTML Tag validation

There is now a quickfix for marking custom HTML5 elements to be ignored in validation.

validation

Note: this is not specific to JBoss Tools, it is built into Eclipse M6

Next steps

With Alpha2 out we are heading towards a Beta1.

In Beta1 we are targeting including:

  1. OpenShift v3 support for templates

  2. Docker Tooling

  3. Better JavaScript content assist

  4. Making project imports in Eclipse even simpler

  5. And more…​

As always, ask/suggest away and we’ll keep you posted!

Have fun!

Max Rydahl Andersen
@maxandersen

JBoss Tools 4.12.0.AM1 for Eclipse 2019-06

by Jeff Maury on Jun 12, 2019.

Integration Tooling for Eclipse 2019-03

by Paul Leacu on May 30, 2019.

Quarkus

by Jeff Maury on May 13, 2019.

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