We've pushed our first Beta of JBoss Developer Studio 4 to our early access site.
You can download the full Eclipse based IDE from the early access site for free, and if you want to have the no-fuzz-single-click-install experience with JBoss Enterprise Application platform bundled you just need to go and sign up for the early access program here.
This release incorporates the changes and improvements done in JBoss Tools 3.2 Beta1.
What does that mean for users ?
It means you can now from your own Eclipse Help menu choose "Eclipse Marketplace"
...and if you type in "jboss" into the search field you will find JBoss Tools there and click "Install" for the version that is relevant for you.
i.e. 3.1 is for Galileo and 3.2 is for Helios (if in doubt, see the description text in the Marketplace).
The screenshot also shows how easy it is to Update or Uninstall the installation you already have (in this case I got JBoss Tools 3.2 already installed).
We hope this makes it even easier to install and use JBoss Tools and if you like what you see please go and favorite us (click the Star) or comment on our Eclipse Marketplace page.
It's Beta time for JBoss Tools, the Eclipse plugin suite for JBoss and related technologies.
It's beta time, meaning we've locked down new feature additions to most of JBoss Tools and we get to give you the first beta release of JBoss Tools 3.2 - the version of JBoss Tools you should use if you are using Eclipse 3.6 (Helios).
Since it is beta time the focus have been and will be on bugfixing, optimization and stabilization but we do got a few nice new features I would like to highlight - as all ways there is more to see on the What's New page(s).
We've fixed reported issues concerning performance problems with validation of XHTML in larger projects. Our own test project (100.000's of Expression languages and thousands of pages) which before took 15 minutes to validate are now done in much less time when doing a full validation. Making the validation much faster as what is seen in the M2 release. If you continue to have performance problems with Beta1 please let us know, since we are still doing improvmements for this area to beta2!
CDI and Seam have all received some more additional validation (i.e. we now valdiate classnames referenced in CDI descriptors) and a good set of quickfixes allowing you to quickly fix common problems.
MyFaces 2 does not ship TLD's within their project. This make them "invisible" to our default handler for JSF compoenents since we moved to use classpath based lookups to have more correct code completion and validation per project. MyFaces does though ship their own -metadata.xml file that describes their components and we've added support to parse and recognize these now. This should make any new components or changes to existing ones in MyFaces show up in the editor without having to get JBoss Tools updated.
JBoss Tools AS Server adapter is now telling the remote server to not scan for changes when remote deployment are done via file copying; preventing "accidental" deployments, making things much more robust.
The remote deployment now also includes optiorns for controlling the start and startup commands used over SSH - allowing you use your own external launch scripts to control how JBoss AS is started/stopped.
HQL (Hibernate Query Language) does not support comments natively, but we have had many requests for allowing it in the Query Editor since it is very useful for quick experiments to be able to comment out parts of your query. Therefore you can now use "--" the beginning of a line to comment it out in the editor. Not a big feature in itself but worth mentioning it since many have asked for it over the years.
We are experiementing with using the new Annotation Properties View which are available via Eclipse WTP JAX-WS support in Helios.
This release therefore are including support for JBoss ESB and JAX-RS (RestEasy) annotations, giving you a more graphical approach to read and write annotations on your service classes.
In M2 we enabled our Usage Tracking and it was a raving success and continues to give us more and more information about where and how JBoss Tools are being used without having users to do anything beyound using our plugins.
We still very much appreciate to hear directly from our users thus don't forget to leave a comment on this blog, post on the forum or report or leave patches to issues on our jira - we love it all.
I'm looking forward to attend for my first time Eclipse Summit 2010 where as I until now only been at EclipseCon's.
I (luckily?) won't be speaking at the conference, but Chris Aniszczyk and Nick Boldt will:
Tuesday at 14:00, Nick is having a 4-hour symposium together with Henrik Lindberg (Cloudsmith) on the topic of "What's in a Build? Best Practices and Requirements". The intent of this is to work out best practices for how to mange the process of developer, nightly, milestone and release builds for Eclipse projects. Something that we have spent alot of time on in the JBoss Tools project but still know can be improved - looking forward to see if what others have done in projects of our scale/size.
Wednesday at 10:30, Chris is doing his "Using Git in Eclipse" together with Matthias Sohn (SAP) showing of the wonders of Git and the EGit tooling for it.
Thursday at 10:30, Nick Boldt is participating together with Henrik Lindberg (Cloudsmith), Jason Van Zyl (Sonatype), Oisin Hurley and Thomas Hallgren (Cloudsmith) in "Build Systems Exposed: Strengths & Weaknesses of Build Technologies at Eclipse" . This talk will compare the various build systems in use at Eclipse - will we finally reach some concensus ?
I'm looking forward to meet old and new Eclipse friends - if you want to find me, look for someone with a JBoss Tools jacket!
See you there!