We won in the Best Mobile Development Solution category.
Really happy to see that happening!
One of the materials submitted was this video outlining the mobile features in particular:
Max Rydahl Andersen
This site is currently under development, and may contain inaccurate and misleading information.
Report an issue
| Status: Red. Known issues: | None
We won in the Best Mobile Development Solution category.
Really happy to see that happening!
One of the materials submitted was this video outlining the mobile features in particular:
A few weeks back Eclipse launched their Java 8 Support for Eclipse Kepler.
Its a great page with links to various resources about Java 8 and how to install the various components into Eclipse.
The four components you want to install if you are doing web/java development for Eclipse are the ones covering:
Java core (JDT)
Java Web Tools (WTP)
For now those need to be installed individually.
We wanted to make that even simpler.
Thus today we deployed our Java 8 packaged install and update site which does not require you to do four different installs.
There are two ways to use this. Using JBoss Central or the composite update site.
Open JBoss Central
Choose Java 8
You will then be shown a screen where you can choose to install all or select a subset.
If you have JBoss Tools installed the recommended way is that you install them all since then you get the best Java 8 coverage possible in Eclipse.
If you do not want to use JBoss Central you can also use this update site directly:
Please note that this site includes plugins for 'm2e' with "Optional" in their name which are only relevant if you are an Eclipse plugin developer. You can skip those - just there for completeness.
We know that Java 8 support is not fully working for WildFly 8 server adapter in our Kepler based JBoss Tools version - if you want to use that try out our recent builds of JBoss Tools for Luna where this is being supported.
But otherwise you can now build and run Java 8 projects with JBoss Tools for Eclipse Kepler today.
The last few days an error have started popping up during validation of all our existing JBoss archetypes and examples.
The error you will see in Eclipse problems view will be:
Referenced file contains errors (http://docs.jboss.org/ironjacamar/schema/datasources_1_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..."
on various *-ds.xml files.
The cause of this error is that the IronJacamar project moved their xsd’s and rest of their content to http://ironjacamar.org back in June 2013.
I’m sorry for that inconvenience, but do not despair - the solution is here.
For now we have requested that the content will be restored to make this true but annoying error to go away without you having to do anything.
But until that is fixed you can also fix it locally by using the updated ironjacamar url/namespace in your .xml files:
<datasources xmlns="http://www.jboss.org/ironjacamar/schema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.jboss.org/ironjacamar/schema http://docs.jboss.org/ironjacamar/schema/datasources_1_0.xsd">
<datasources xmlns="http://www.ironjacamar.org/doc/schema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.ironjacamar.org/doc/schema http://www.ironjacamar.org/doc/schema/datasources_1_0.xsd">
Why this validation errors have not shown up before we are still looking into and I’ll let you know when we have that answer.
For now just live with the validation error for a few days or update your xsd files to use the new namespace.
Again, sorry for the inconvenience.
Despite this - do Have fun!
In this article I’m happy to introduce you a brand new HTML Preview without XULRunner.
Basically, HTML Preview could be treated as a possible XULRunner substitution for plain HTML pages (JSF/xhtml still requires XULRunner). The point is that when XULRunner is unavailable, HTML Preview will be used in "Visual/Source" and "Preview" tabs of the VPE. It will be also available as a separate view and won’t be coupled with a paticular editor.
HTML Preview has several cool features like:
automatic refresh (enabled by default)
refresh on save
navigation from source to view and vice versa
Here is a short demo video, which covers basic use case :
HTML Preview is not in production yet. It will be a part of JBoss Tools and Developer Studio Beta2 release for Eclipse Luna. However, you can today access to the "nightly" build of JBoss Tools VPE update site at:
On this update site you find "HTML Preview" when unselecting "Show categorized". Once installed and you have restarted Eclipse you should have a "HTML Preview" view available.
We are trying our best to make HTML Preview as good as possible. Users feedback is what we are seeking for now. We are looking forward to hearing your comments / remarks!
We are ready with JBoss Tools 4.2 Beta1 and Red Hat JBoss Developer Studio 8 Beta1.
This announcement is a bit special since it is on our new website, with a cleaner and more consistent structure.
There is the specific version download available from JBoss Tools 4.2.0.Beta1.
Then there is the Luna download page which shows the latest Stable, Development and nightly download for Eclipse Luna - that is available from Luna releases.
JBoss Developer Studio comes with everything pre-bundled in its installer. Simply download it from our JBoss Products pagerun it like this:
java -jar jbdevstudio-<installername>.jar
JBoss Tools or Bring-Your-Own-Eclipse (BYOE) JBoss Developer Studio requires a bit more:
This release requires at least Eclipse 4.4 (Luna) M6 but we recommend using the Eclipse 4.4 JEE Bundle since then you get most of the dependencies preinstalled.
Once you have installed Eclipse, you either find us on Eclipse Marketplace under "JBoss Tools (Luna)" or "JBoss Developer Studio (Luna)".
For JBoss Tools you can also use our update site directly if you are up for it.
Note: Integration Stack tooling will become available from JBoss Central at an later date.
As always there is more than can be covered in a single blog but here are some of my favorites. You can see everything in the What’s New section for this release.
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.
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!
While we wait for feedback on Beta1, we are already working on what will become Beta2. Some of things that are moving here are:
Looking at doing radical changes to how the visual page editor works since XULRunner is not maintained anymore and we need HTML5 support
Improve JavaEE 6 and JavaEE 7 support
Full Java8 support
Hope you enjoy it and remember…
Fuse Tooling goes Final in the Stack!
The Integration Stack for JBoss Tools Developer Studio is a set of plugins for Eclipse that provides tooling for the following frameworks:
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.
JBoss ESB - An enterprise service bus for connecting enterprise applications and services.
Fuse Apache Camel Tooling - A graphical tool for integrating software components that works with Apache ServiceMix, Apache ActiveMQ, Apache Camel and the FuseSource distributions.
jBPM3 - A flexible Business Process Management (BPM) Suite - JBoss Enterprise SOA Platform 5.3.x compatible version.
Modeshape - A distributed, hierarchical, transactional and consistent data store with support for queries, full-text search, events, versioning, references, and flexible and dynamic schemas. It is very fast, highly available, extremely scalable, and it is 100% open source.
Savara (JBoss Tools only) - A tool for ensuring artifacts defined at different stages of the software development lifecycle are valid against each other, and remain valid through the evolution of the system.
SwitchYard - A lightweight service delivery framework providing full lifecycle support for developing, deploying, and managing service-oriented applications.
All of these components have been verified to work with the same dependencies as JBoss Tools 4.1 and Developer Studio 7, so installation is easy.
To install the Integration Stack tools, first install JBoss Developer Studio from the all-in-one installer, bundled and configured out of the box with everything you need to get started. Alternatively, if you already have eclipse-jee-kepler installed, you can install JBoss Developer Studio or JBoss Tools from the Eclipse Marketplace via Help > Eclipse Marketplace…
Once Developer Studio is installed, restart Eclipse and select the Software/Update tab in the JBoss Central view and look for the JBoss Developer Studio Integration Stack installation section. Select the items you’d like to install:
If you want to try out Savara you will need to use the JBoss Tools Integration Stack URL instead:
Note: If you installed into your own Eclipse you should bump up the launch resource parameters:
--launcher.XXMaxPermSize 256m --launcher.appendVmargs -vmargs -Dosgi.requiredJavaVersion=1.6 -XX:MaxPermSize=256m -Xms512m -Xmx1024m
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
This morning I wanted to go try out the latest Eclipse Luna nightly.
It is actually very easy to do.
You simply goto Eclipse Downloads.
Scroll to the bottom where you should fine the last two weeks worth of nightly downloads. Take the newest one where the tests completed indicate the build should be mostly working.
Why was I trying out the latest nightly anyway ? Well, I heard a rumor from Lars Vogel that one of my least favorite "improvemnts" in Kepler have now been properly fixed.
It turns out it is true, the Quick access feature no longer requires the toolbar!
You could do this is in Eclipse Kepler too but when using the Quick Access feature via Cmd+3 (or Ctrl+3 on Linux/Windows) the toolbar would pop up again disturbing your toolbar free Zen state.
With this fix we can finally get back to utilizing the full screen with what matters - the content I want to see, not what a toolbar want me to push.
While testing this I did find a few bugs, but that is all good. This helps the Eclipse Platform team to know about the issues and makes it more likely the issues will be fixed. Maybe someone even comes up with a patch.
I can only encourage you to try out the nightlies of both Eclipse and JBoss Tools to give early feedback.
It is how we all get a better IDE and hey, you might find that your biggest annoyance have been fixed!
We have been working for a while on doing a refresh of our website, and today we are happy to announce tools.jboss.org.
We had a few goals for the website:
Make it simple and clear how to download the plugins
Explain what features are in the tools
Include New and noteworthy
Make it easier to update/fix the content
and I think we reached all of them.
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:
Alexey Kazakov - for contributing to Features
Andre Dietisheim - for contributing to Features
Aslak Knutsen - for inspiration and help with Awestruct
Barry LaFond - for contributing to Features
Bob Brodt - for contributing to Features
Bob McWhirter - for reacting at weird hours on #awestruct and for not caring how his name is spelled
Brian Fitzpatrick - for contributing to Features
Cheyenne Weaver - for design help
Dan Allen - for help with asciidoc and especially for including the video support we made
Daniel Florian - for contributing to Features
Fred Bricon - for contributing to Features
Gorkem Ercan - for contributing to Features
Ilya Buziuk - for contributing to Features
James Cobb - for design help and bugfixing
Jason Porter - for awestruct fixes and especially finding that nasty performance bug we had made
Koen Aers - for contributing to Features
Kris Verlaenen - for contributing to Features
Lars Heinemann - for contributing to Features
Mark Newton - for enabling the infrastructure
Michelle Murray - for bugfixes!
Nick Boldt - for helping setup downloads and bugfixing!
Paul Leacu - for contributing to Features
Pete Muir - for review!
Rob Cernich - for contributing to Features
Rob Stryker - for contributing to Features
Rysiek Kozmik - for help with jboss.org theme
Snjezana Peco - for contributing to Features
Vineet Reynolds - for contributing to Features
Vladimir Vasilev - for setting up redirects to ensure we didn’t break the internet!
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 :)