Posts tagged with 'jbosscentral'

To allow users of JBoss Developer Studio to try out plugins which have not yet reached supported level more easily we’ve added the notion of Early Access to JBoss Central.

For now we’ve moved Eclipse VJET into this area and made Arquillian Tools and AngularJS available for Developer Studio users.

The "Early Access" features are from an isolated update site that only gets added if you press "Show Early Access" and when you unselect "Early Access" we will remove/disable those update sites thus you will not receive anymore updates of those features.

Try it out!

VPE has been refactored to use the new HTML Preview feature.

This means we will use your system native browser to preview HTML5 based pages (XHTML/JSF will still use the old XULRunner based browser if possible).

This new preview has much better Javascript support and just looks better.

If you do not like the split editor view you can also open it as a separate view which will show the HTML representation of editors that uses the WTP based XML DOM model (i.e. our html editor and wtp xml editors).

The preview supports navigating between source and the visual elements allowing you to easily find the right place in the code.

To improve Eclipse JSDT default JavaScript we’ve done many fixes to it that are available in stock Eclipse, but for JBoss Tools we’ve started to try use Tern behind the scenes via Angello Zerr’s angularjs-eclipse and tern-java projects.

In JBoss Tools Tern is now automatically enabled on Javascript based projects intended to give you much stronger and better content assist in addition to what Eclipse JSDT provides.

We are trying to make it that there is no user setup needed for most common javascript functionallity to work.

For example if you create a Hybrid Mobile Tooling project we will enable the support for Apache Cordova Javascript out of the box.

As an experiemnt, we’ve made AngularJS available from JBoss Central under "Early Access" to give a try if you are an Angular user.

We are really interested in hearing if these improvements to JavaScript and Angular support work for you!

The OpenShift wizard now supports OpenShift’s notion of quickstarts or instant apps.

This means it is now possible to just use OpenShift Wizard in Eclipse to use one of the many custom defined quickstarts without having to use the browser.

Examples of interesting JBoss server related quickstarts are WildFly 8.1, AeroGear Push server and CapeDwarf.

On request OpenShift now supports saving and restoring your OpenShift instances via Snapshots.

The view before called 'MBeans Explorer' is now called 'JMX Navigator' and it now can do much more than before.

First off, it will automatically list locally detected Java Virtual Machines which you can connect to and browse their internal state via JMX MBeans.

Once you have this view open you can browse the MBeans, but with a little bit of magic you can also get various performance metrics displayed.

You can even get profiling info such as hotspots, memory usage etc.:

Basically, JBoss Tools now comes with a built-in Java profiler out of the box.

This functionallity originally comes from Fuse IDE which adopted jvmmonitor which we have now moved into JBoss Tools core to unify our access to JMX and Java processes.

Until now JBoss Tools core have used basic file patterns to find appropriate jars for your classpath and for introspecting the JBoss servers. With JBoss Modules where there can be multiple versions and several layers of patching this kind of simple file pattern searching is not sufficient.

Thus now our WildFly/JBoss EAP based servers understand the notion of JBoss Modules and will locate the proper module.

It even will detect if your manifest.mf has Dependencies and add them to the list of jboss modules to the classpath Eclipse will use for compiling.

The server adapters for JBoss AS, EAP and WildFly have been refactored to support…​

These improvements required significant changes in the server adapter core API and UI. The meat of the code is still the same - just split out to be more reusable and composable.

We would really like to hear from you if the UI is good, bad, better, worse; and in any case how we can make it even better. We’re obviously interesting in knowing whether these features do work for you.

You can see more in the Servers What’s New.

OpenShift has been offering support for custom defined cartridges - now OpenShift tools supports this natively too.

This means you can create or use an existing cartridge by choosing the "Code Anything" option for either Applications or Cartridges.

This allows you to, for example use a Cartridge like WildFly 8 or the recent OpenShift on JRebel experiment without leaving the IDE.

The Cordova runtime support is now extended to also support using locally downloaded runtimes. Making it possible to use custom builds or simply distributions that are not directly available from Cordova repositories.

There are also various other fixes which can be viewed at Aerogear What’s New.

p.s. we are contributing these tools to eclipse.org under Project Thym.

The Cordova Simulator also now understands the notion of multiple Cordova runtimes allowing you to test against multiple versions.

The Arquillian tooling (for now only available in JBoss Tools) added a Sapphire based editor for the arquillian.xml file format.

For now it is a simple structured editor but we plan on using it for experimenting with Sapphire to provide better XML oriented editors.

This Arquillian editor was based on ideas and initial contribution from Masao Kunii working for Nippon Telegraph and Telephone Corporation (NTT) - thank you!

Recent version of Forge 1 and 2 are now distributed with tools and especially the later one brings an interesting feature.

Forge 2 Connection Profiles now will consider Eclipse Database Tooling Platform (DTP) connections meaning you no longer have to configure your database settings in multiple places.

This feature is called connection profiles in Forge 2.

We have learned a lot from our last 3+ years usage tracking and continue to be amazed with how many nationalities, countries and operating system distributions the tools are used in - it has been and continue to be very informative and helpful in guiding our tooling support.

In Beta1 we have gone a step further into learning not only about how many starts JBoss Tools, but also now which features are being used.

In Beta1 we now collect info about which server types are used and which JBoss Central installs are being done to be able to see how much and how often these features are used.

We will use that in the future to decide new development and maintanence work - thus if you love a feature in JBoss Tools then please say yes to usage tracking and use the feature and we’ll notice.

Note: We are only collecting aggregated summaries of i.e. server types and installs - meaning we cannot use any of this info to identify you. It is truly anonymous usage statistics - we are not the NSA!

The previous release of the JBoss Developer Studio Integration Stack had a candidate release of Fuse Apache Camel Tooling. The support is now complete and ready to run with the Fuse Active MQ 6.1 release.

Fix release versions of BPMN2 Modeler, SwitchYard and Teiid Designer are also available in this release.

Don’t miss the new Features tab for up to date information on your favorite Integration Stack component: /features

Our old download page had grown organically over the last 7 years and, despite all good intentions, we had ended up with a download page with way too many options presented by default. With the new site, we went for simplicity first, and so the Downloads page now simply presents you with two options: Download either latest stable JBoss Tools or Developer Studio.

If you want other versions, combinations, add-ons etc. you can follow the Overview link which will give all the dirty details.

For this we created the Features page. This page gives an overview over all of the various projects and technologies we support and if you click on the images you get more information about each feature.

Try it out - you might be surprised how much we actually do.

For every release/milestone, we get the JBoss Tools team to write up what is New and noteworthy for their components. We use that when doing blogs and sharing with the whole community what changes are coming up. In the past, that was a very tedious process of getting multiple people to submit changes to a bunch of html files that then needed to be manually cleaned up and published. It was a chore, and it took longer and longer as we added or updated more and more features.

That is now a story of the past - in the new site, component developers just add a single document for their release and the magic of publishing the site does all the right wiring. Removing all the chore and reducing the actual lines of code needed substantially. Asciidoc for the win.

You can go look at what is new and improved over at What is new - it currently gives you a sneak preview of upcoming JBoss Tools 4.2.0 Beta1.

The old website was "hidden" behind a magnolia CMS system. It has served us well and it does what it is supposed to do. In the age of github and pull-requests though it was more a burden than a help. The new system uses a simple github repo which uses Awestruct to render the page automatically via Travis when we push to certain branches.

The content is primarily Asciidoc making it so the content is very compact - no additional boiler plate markup to worry about and best of all, you do not need to even run awestruct locally to get an idea of the rendering. Github’s rendering of asciidoc is close enough to make it trivial for anyone with a github account to help do fixes to this site.

If you find some errors (we left some in for you to find) just open a PR on https://github.com/jbosstools/jbosstools-website :)

The design and launch of this website have been long under way - we started 1+ year ago but we are finally here :)

The primary person to thank for this is Xavier Coulon who helped on the initial design of the site and then fought, battled and sometimes cried over having to implement and play with Ruby and Haml. But he persevered and today we are here with his great help!

But he and I were not alone in this; we got help from a bunch of other people to write and update content, give feedback, find bugs and help setup the infrastructure. Here they are in random importance, but ordered alphabetically:

In case I missed someone - let me know or submit a PR on https://github.com/jbosstools/jbosstools-website

I hope you like it and please leave a comment below to test the new commenting system too :)

Have fun!

Max Rydahl Andersen
@maxandersen