A JBoss Project
Red Hat

Posts tagged with 'devstudio'

A couple weeks ago, I started prototyping how we could enable building PRs submitted against the JBoss Tools projects, in order to more easily create installable update sites (Eclipse p2 repositories) from pull requests. This is part of our new thrust to provide more continuous integration and deployment, to better be able to release software faster.

Purpose

Verify a commit before pushing it to master. Continuous feedback. Easier installation testing. Ability to share a proposed change, including the whole built update site so peer reviews can be done against binaries as well as sources.

Job Config

Here’s how to configure a job to use the Github Pull Request Builder Plugin:

  1. add a sha1 parameter

    <hudson.model.StringParameterDefinition>
      <name>${sha1}</name>
      <description/>
      <defaultValue>master</defaultValue>
    </hudson.model.StringParameterDefinition>
  2. pull from git using this remote config:

    <name>origin</name>
    <refspec>+refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin/pr/*</refspec>
  3. pull from git using this branch:

    ${sha1}
  4. enable Github Pull Request Trigger

    <org.jenkinsci.plugins.ghprb.GhprbTrigger plugin="ghprb@1.20.1">
      <spec>H/5 * * * *</spec>
      <adminlist>nickboldt</adminlist>
      <allowMembersOfWhitelistedOrgsAsAdmin>false</allowMembersOfWhitelistedOrgsAsAdmin>
      <orgslist>jbosstools</orgslist>
      <cron>H/5 * * * *</cron>
      <triggerPhrase/>
      <onlyTriggerPhrase>false</onlyTriggerPhrase>
      <useGitHubHooks>false</useGitHubHooks>
      <permitAll>false</permitAll>
      <commentFilePath/>
      <whitelist>nickboldt</whitelist>
      <autoCloseFailedPullRequests>false</autoCloseFailedPullRequests>
      <displayBuildErrorsOnDownstreamBuilds>false</displayBuildErrorsOnDownstreamBuilds>
      <whiteListTargetBranches>
        <org.jenkinsci.plugins.ghprb.GhprbBranch>
          <branch/>
        </org.jenkinsci.plugins.ghprb.GhprbBranch>
      </whiteListTargetBranches>
      <msgSuccess/>
      <msgFailure/>
      <commitStatusContext/>
      <project>jbosstools-build-sites.aggregate.child-sites__pull-request_master</project>
    </org.jenkinsci.plugins.ghprb.GhprbTrigger>

Job Steps & Deployment

One way to react to a successful build of a PR is to simply deploy to a different URL than normal builds.

For example, a job could be set up such that if ${ghprbPullId} is defined, a deploy-pr profile is used; if not, the usual deploy-to-jboss.org profile could instead be used.

mvn deploy -Pdeploy-pr

However, we might also want a different sequence of build steps in a job. Normally, we orchestrate jobs to build, deploy, & test. But for a PR build, we might instead want to sequence the steps as build+test, and only deploy if successful.

So perhaps instead of parameterizing the job to publish to snapshots/pulls/ or snapshots/builds/, we might instead parameterize the maven lifecycle steps:

if [[ ! ${ghprbPullId} ]]; then
    mvnStep1="clean install -DskipTests" # build without tests
    mvnStep2="deploy -Pdeploy-to-jboss.org" # deploy if p2diff or SHA check shows difference into /builds/ folder
    mvnStep3="verify" # run tests & fail job if problems found
else
    mvnStep1="clean deploy -Pdeploy-pr" # build and test, then deploy to /pulls/ folder if successful or fail if tests fail
    mvnStep2="NONE"
    mvnStep3="NONE"
fi

Current experiment is here (sorry, VPN required):

Questions / TODOs

  • Can whitelists be set up programmatically? (git committerIDs which can trigger a build automatically)

  • Can admins be set up programmatically? (git committerIDs which can approve a PR to be built, rather than ANY submitted PR, to prevent malicious attacks)

  • How do we roll up a low-level project’s pull request build into a larger stack of projects or products? Do we rebuild everything that’s downstream? Or just the aggregates/product?

  • How aggressively should we purge pull request builds?

  • When running matrix jobs, what happens when one part of the job is running, another is waiting, and a force-push updated to a PR arrives? (Answer: the waiting configurations will fail because the expected SHA no longer exists, having been force-replaced.)

The second Beta of JBoss Tools 4.3.1 and JBoss Developer Studio 9.1.0 for our maintenance Mars release is available.

jbosstools jbdevstudio blog header
Remember that since JBoss Tools 4.3.0 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.

What is New?

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

Eclipse Mars.2

JBoss Tools and JBoss Developer Studio are now targeting the latest Eclipse Mars.2 as a running platform with many issues fixed comparing to the previous Mars.1 release.

OpenShift 3

More than 60 issues targeting OpenShift 3 support have been fixed in this release. The OpenShift 3 integration was introduced as a technology preview feature in JBDS 9.0.0.GA but will graduate to a supported feature in the upcoming JBDS 9.1.0.GA release.

Incremental publishing

The OpenShift 3 server adapter now respects the auto-publish settings as declared in the server editor, giving the user the option to automatically publish on workspace changes, build events, or only when the user requests it. The server adapter is also able to incrementally deploy the server’s associated project with a quick call to rsync, ensuring minimal over-the-wire transfers and a fast turnaround for testing your project.

Support for Java EE projects

Experimental support for Java EE projects (Web and EAR) is now available. When the workspace project associated with the OpenShift 3 server is a Dynamic or Enterprise Application project, the server adapter builds an exploded version of the archive to a temporary local directory and replaces the version deployed on the remote OpenShift pod. That Pod Deployment Path, is now inferred automatically from the image stream tags on the remote Pod. A .dodeploy marker file is created for the remote server to redeploy the module if necessary (for EAP/WildFly servers supporting it).

Support for LiveReload

The new tooling includes LiveReload support for OpenShift 3 server adapters. This is accessible from the Show In > Web Browser via LiveReload Server menu. When a file is published to the server adapter, the Browser connected to the LiveReload server instance will automatically refresh.

openshift3-livereload-menu

This is particularly effective in conjunction with the Auto Publish mode for the OpenShift 3 server adapters, as all it takes to reload a web resource is saving the file under edition (Ctrl+S, or Cmd+S on Mac).

Simplified OpenShift Explorer view

Previously, the OpenShift 3 resources representation exposed a large amount of unnecessary information about OpenShift. The explorer view is now simplified and specific (and made much more robust) and focuses on an application-centric view.

simplified-openshift3-view

Everything that is no longer displayed directly under the OpenShift Explorer is accessible in the Properties view.

Red Hat Container Development Kit server adapter

The Red Hat Container Development Kit (CDK) server adapter now provides menus to quickly access the Docker Explorer and the OpenShift Explorer. Right-click on a running CDK server adapter and select an option in the Show In menu:

cdk-server-show-in-menus

Forge Tools

Forge Runtime updated to 3.0.0.Beta3

The included Forge runtime is now 3.0.0.Beta3. Read the official announcement here.

Stack support

Forge now supports choosing a technology stack when creating a project:

stack-new-project

In addition to setting up your project, choosing a stack automatically hides some input fields in the existing wizards, such as the JPA Version in the JPA: Setup wizard:

What is Next

We are approaching the final release for our first maintenance update for Eclipse Mars.2. It’s time to polish things up and prepare a release candidate.

Enjoy!

Alexey Kazakov

Just in time for Christmas, JBoss Tools 4.3.1.Beta1 and JBoss Developer Studio 9.1.0.Beta1 are ready for download. This is the first beta for our maintenance Mars release.

jbosstools jbdevstudio blog header
Remember that since JBoss Tools 4.3.0 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.

What is New?

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

Docker Tools

Run Image Launch Configuration

When running an image, a launch configuration is created, based on the selected image. This is useful when users want to try tweaking a previous run for various reasons (e.g. binding in new volumes or changing command parameters, etc.)

Running a container from an image can now be also done via a launch configuration.

Run Image Launch Configuration

Docker Machine Support

Docker Machine is now supported for the creation of a new connection. Simply click the "Search…​" button and you will be prompted to select an active Docker Machine connection, if one exists.

Docker Machine Support

TM Terminal Support for Interactive Shells

Containers created with a pseudo TTY allocated (-t) will open within a TM Terminal. This is much more fully featured interaction when compared with the previous standard console. In particular, the Terminal view recognizes the color code on logs and displays messages in appropriate colors.

terminal_tm_support

Improvements on the Importer wizard

The Import wizard that you can access via File > Import Projects from Folder…​, File > Import…​ > General > Projects from Folder or File > Import…​ > Git > Projects from Git (auto-import) allows more user control. You can now see a proposal for the import (what will be imported and how) and select which sub-projects to import or not.

Performances have also been highly improved, and importing a Maven project will now suggest installation of m2e connectors when necessary.

Credential Framework

A new feature has been added to safely store your credentials for various domains in a central location. As our tools grow, it has become more likely that at least some credentials will be re-used by several different features. Having a central place to store, for example, your Red Hat Access credentials or JBoss.org credentials, for re-use by our server adapters or download-runtime features helps to prevent you from having to constantly type the same usernames and passwords in multiple locations. It also helps to ensure that if you change your password on some remote server, you only need to update one location in eclipse.

Credentials Preference Page

OpenShift 3

More than 80 issues have been fixed in this release of the OpenShift tooling, mostly targetting OpenShift 3 support. OpenShift 3 was introduced as a techpreview feature in JBDS 9.0.0.GA but will graduate to a supported feature in the upcoming JBDS 9.1.0.GA release. More details for all improvements you can find here.

Deploy Workspace Projects

You can now deploy existing workspace projects to OpenShift 3 instances. You can either create a new OpenShift application, using an OpenShift 3 connection and then select the workspace project to deploy, or you can start by right-clicking on a project and use the Configure…​ > Deploy to OpenShift…​ menu.

deploy-workspace-project

New OpenShift 3 Server Adapter

A prototype for a new OpenShift 3 server adapter is now available. It’s goal is to allow incremental deployment of workspace resources directly into the deployed node on OpenShift, bypassing the whole build step. Its capabilities are currently limited and require a number of manual steps to set it up, but we should streamline its usage in the next Beta. Currently only Node and PHP based applications are supported.

openshift3-new-server

OpenShift Explorer Improvements

The explorer is now listening to server side events, so it can automatically refresh itself. A new Edit…​ menu is available in the OpenShift Explorer, allowing you to edit any resource (except Builds) as JSON in a text editor.

edit-resources

Search for Docker Images

When deploying a Docker image, searching for a docker image has never been easier, simply click on the Search…​ button and find your favorite image from the the selected Docker registry:

search_docker_images

Expose Additional Ports from the Docker Image

It is now possible to expose ports to a deployment, other than just those explicitly exposed on the docker image (they still need to be exposed by the image though).

expose-service-ports

What is Next

We are working on the next Beta build which we are planning to release in January.

Merry Christmas!

Alexey Kazakov

JBoss Fuse Tooling is now featuring production versions of the Fuse SAP Tool Suite, Fuse Data Transformation tooling and SwitchYard plus updated Data Virtualization (Teiid Designer/ ModeShape) and BRMS Tooling (BPEL, BPMN2, Drools/jBPM6) for Luna/JBoss Developer Studio 8.

jbosstools jbdevstudio blog header
JBoss Tools Integration Stack

JBoss Tools Integration Stack 4.2.4.Final / JBoss Developer Studio Integration Stack 8.0.4.GA

What’s an Integration Stack?

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

JBoss Fuse Development

  • Fuse Tooling - JBoss Fuse Development plug-ins providing tooling for Red Hat JBoss Fuse, specifically for integrating and developing software components that work with Apache ServiceMix, ActiveMQ and Camel.

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.

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

  • 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

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

  • 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 Since 8.0.3.GA?

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

Released Tooling Highlights

JBoss Fuse Development Highlights

Fuse Tooling Highlights
  • Data Transformation, SAP and SwitchYard are now released!

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

SwitchYard Highlights

JBoss Business Process and Rules Development

Drools/jBPM6 Highlights
  • As part of this release, the Kie Navigator is added to the Drools component.

Data Virtualization Highlights

Teiid Designer Highlights
  • Added support for dynamic VDBs.

  • Performance improvements in the admin factory.

  • Lots of bug fixes.

Early Access/ Technical Preview Tooling Highlights

None! We’re happy to say that all JBDS 8/ Eclipse Luna compatible features are now released as production plugins.

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…​

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

Give it a try!

Paul Leacu.

An update to Red Hat JBoss Developer Studio 9 for Eclipse Mars are now generally available!

jbds9

What’s new?

This release is simply a rebuild of the JBoss Developer Studio 9.0.0.GA installer that bundles JBoss EAP 6.4.0, due to CVE-2015-7501. The rebuild includes a patched version of EAP 6.4.0.GA.

The standalone installer is unaffected and therefore required no change. Similarly, JBoss Tools users are also unaffected unless you manually downloaded and installed EAP 6.4.0. A patched version of the EAP 6.4.0.GA is available.

Previous announcements

For what’s new in this release of JBoss Tools 4.3.0.Final or JBoss Developer Studio 9.0.0.GA, see our previous GA blog announcement.

What’s next?

We are already working on the next maintenance release for Eclipse Mars - JBoss Tools 4.3.1.Beta1 and Red Hat JBoss Developer Studio 9.1.0.Beta1 will be available shortly.

We are also working on our first Eclipse Neon based builds. Try them out here:

Enjoy!

Nick Boldt

JBoss Tools 4.3 and Red Hat JBoss Developer Studio 9 for Eclipse Mars are now generally available!

jbds9
Java 8 is required for installing and using 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 latest Eclipse 4.5.1 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 "Red Hat JBoss Developer Studio".

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

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

What is new ?

There are many new features and improvements. The full list of what is new you can find on this page. Hundreds of bugs have been fixed on JBoss Tools side but we also continue to work on making Eclipse better and contribute to many Eclipse projects: Web Tools, Docker, Maven Integration, JavaScript, Hybrid Mobile Tools and many others.

Let me highlight just a few major features in JBoss Tools 4.3 and JBoss Developer Studio 9.

OpenShift 3

There is a new tooling available to help you with OpenShift 3 application development.

new connection wizard

OpenShift 3 tooling is provided as a TechPreview feature, available from the JBoss Central Software/Updates page. We are working on improving OpenShift 3 tooling and it will be included in JBoss Developer Studio by default as a Supported feature in the upcoming months.

Docker

Tooling for Docker is available in Eclipse Mars under the Linux tools umbrella. Despite this name, this works on all major developer platforms. It is mirrored on JBoss Tools update site and is also included in Developer Studio 9.

docker explorer view

Batch

Java EE 7 Batch Tools include an advanced Job XML editor, wizards, validation, navigation, and other features.

diagram

Where is integration stack tooling?

The integration stack covers the tooling for Fuse, Drools, jBPM, SwitchYard, JBoss ESB etc.

They are available as "Early access" in JBoss Tools under JBoss Central Software/Update page.

In the near future it is planned to also show up in JBoss Developer Studio and eventually be available as fully supported.

What is Next

Having JBoss Tools 4.3 and JBoss Developer Studio 9 out we are already working on the next maintenance release for Eclipse Mars. We are also working on Eclipse Neon adoption.

Enjoy!

Alexey Kazakov

We are happy to announce JBoss Tools 4.3 CR1 and Red Hat JBoss Developer Studio 9 CR1 for Eclipse Mars are now available.

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

jbosstools jbdevstudio blog header
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.

What is new ?

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

WildFly 10 and EAP 7 Server Adapters

New server adapters for JBoss EAP 7 and WildFly 10 have been added to the toolset, allowing you to enjoy all the past benefits, but with all the newest runtimes.

wildfly10

Quick Access to Launch LiveReload

Users can now launch LiveReload from the 'Quick Access' menu, or using the Ctrl+3 (or Cmd+3) keyboard shortcut.

This will first display the dialog to create and start a LiveReload server. Then, this will open the current element (a selected file in the Project Explorer, a selected module in the Servers view or the content of the active editor) in the browser, without even having to use the 'Open With>Web Browser via LiveReload Server' contextual menu.

livereload quick access

OpenShift 3

We have made great progress in the OpenShift 3 Eclipse Tooling, but a few features are still missing, like deploying an existing workspace project, or editing existing build configurations. We have some ideas to provide an even better OpenShift Explorer user experience.

OpenShift 3 tooling is provided as a TechPreview feature, available from the JBoss Central Software/Updates page. Once we are fully satisfied with the quality of its feature set, OpenShift 3 tooling will mature to a Supported feature in the upcoming months, and will then be installed by default in JBDS.

But despite the fact that OpenShift 3 is still in TechPreview status in this release there are many improvements. Such as enhancements in the Application wizard or a link to the online documentation from the connection wizard for OpenShift 3. Hopefully that should help you get started with OpenShift 3 in Eclipse:

openshift3-getting-started

Improvements in OpenShift Explorer:

openshift-menus

Easy setup for 'oc' binary and log streaming:

stream-logs

Integration with Docker tooling:

deploy_image_menu

And other features + almost a hundred fixed bugs.

Java EE Batch Tooling

Quick Fixes for validation problems in Batch Job XML source editor.

qf

The Quick Fixes open a pre-set New Batch Artifact wizard to create the missing artifact.

New Maven Red Hat GA repository

In the Maven Repository Configuration wizard, accessible from Preferences > JBoss Tools > JBoss Maven Integration > Configure Maven Repositories…​, the predefined Red Hat TechPreview All Maven repository has been replaced with the new, official Red Hat GA (GA: General Availability) repository, for released Red Hat JBoss Middleware artifacts.

It is recommended you replace the old TechPreview All repository with the new GA one, in your Maven settings.xml.

Offline Support for Project Examples in JBoss Central

In the updated JBoss Central page, you now have access to more than 200 project examples. All these examples and their dependencies can now be cached locally via the Groovy Offline script, available from Preferences > JBoss Tools > Project Examples > Offline Support.

Eclipse Mars.1 with better Docker tooling

This version of JBoss Tools targets Eclipse Mars.1 which besides many bug fixes has some noteworthy improvements such as a better Docker tooling. We worked on the Docker tooling to make it rock in JBoss Tools with OpenShift support - so we wanted to highlight these improvements.

Running/paused/stopped Docker containers

New icon decorators in Docker Explorer View show the state of the docker containers. This makes it clearer if a container is running, paused or stopped.

docker_explorer_view

New Dialog to Search and Pull Images

There is an updated Pull Image wizard which can be launched from the Docker Images view or from the Docker Explorer view (a new context menu entry is available on the connection node and on the Images node):

docker_pull_image_wizard

The wizard detects the tag in the image name and if none is specified, the image tagged latest will be pulled. If the user needs to search a specific image name, he or she can click on the Search…​ button which will open the Search wizard:

docker_search_image_wizard1

followed by a second page that displays all the tags for the selected image.

New Launcher to Build a Docker Image

We have also added a new launcher to build images from a Dockerfile.

docker_image_build_launcher

You can find more details about this and other new stuff in Docker tooling here.

What is Next

With CR1 out we are heading towards a final release.

Have fun!

Alexey Kazakov

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

In this article I’m happy to introduce brand new JBoss Bower Tools:

Bower JBoss Tools

Bower is a front-end package manager which works by fetching and installing frameworks, libraries, assets. It offers a generic, unopinionated solution to the problem of front-end package management, while exposing the package dependency model via an API that can be consumed by a more opinionated build stack. Bower provides declarative dependency management (dependencies are declared and tracked in a manifest file, bower.json).

Pre-Requirements

JBoss Bower Tools fall back on native Node.js and Bower calls. Hence, the following software must be pre-installed:

  • Node.js

  • npm

  • Bower

Installation instructions for Node.js and npm can be found here. Bower is a command line utility which is installed via npm command npm install -g bower

Quick Start Guide

For now only init and update commands of Bower API are supported. In order to initialize Bower one need to select File → New…​ → Other…​ and choose "Bower Init" wizard:

Bower Init wizard

This wizard helps to create bower.json file depending on set of preferences:

Bower Init wizard page

After pressing "Finish" button bower.json will be created under specified directory:

Default bower.json

In order to add new dependencies one need to specify them in bower.json:

Bower dependencies

For updating dependencies user should right-click on the bower.jsonRun As…​Bower Update

In most cases Bower and Node.js will be detected in the system automatically. However, if the detection failed warn dialog will be shown for specifying location in preferences:
Bower preferences

"Bower Update" launch shortcut makes a native call which will install required packages or update them to the newest version according to bower.json:

Bower Update launch

Specified packages will be created under bower_components folder after "Bower Update" execution:

Bower components

Basically, that is all - one can now use those packages for future front-end development.

Demo

Here is a short demo video which describes a basic use case of JBoss Bower Tools:

How to give it a go ?

Bower support will be available in 4.3.0.Beta2 release and above. You can also use our nightly update site in order to try Bower Tools (JBoss Tools JavaScript Tools category) before the official release:

Bower dependencies

Conclusion

We are trying our best to make our tools as good as possible. User feedback is what we are seeking for now. We look forward to hearing your comments, remarks and proposals.
Have fun!

Ilya Buziuk
@ilyabuziuk

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