Beta3 of JBoss Tools and Developer Studio is now available with a good set of bugfixes but also a good set of new improvements and features in the area of OpenShift, Maven, BrowerSim, GWT, Annotation Processing and it even now come with easy installable source features for easy debugging and hacking. 

jbosstolsdevstudio.png

Beta3

Developer Studio: [Download] | Tools: [Download] [Update Site] | [What's New] [Forums] [JIRA] [Twitter]

 

JBoss Tools is a set of plugins for Eclipse that complements, enhances and goes beyond the support that exist for JBoss and related technologies in the default Eclipse distribution.

 

JBoss Developer Studio is a fully bundled Eclipse distribution which not only includes majority of JBoss Tools but also all its needed dependencies and 3rd party plugins allowing for an easy one-click and no-fuzz installation.

 

If you are into doing your own bleeding edge eclipse plugin assembly, JBoss tools is for you, if you are more into having something that "Just Works" then JBoss Developer Studio is the way to go.

 

Installation

 

JBoss Developer Studio comes with everything pre-bundled in its installer. Simply download it and run it like this:

 

java -jar jbdevstudio-<installername>.jar

 

Note, if you are on Mac OSX 64-bit we recommend you ensure to select the 32-bit option in the multi-platform installer to get Visual Page editor working and use much less memory.

 

Similar if you are on Windows 64-bit then use a 32-bit JDK to get 32-bit version running.

 

JBoss Tools requires a bit more:

 

This release requires at least Eclipse 3.7.1 but we recommend using the Eclipse 3.7.2 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 (Indigo)" or use our update site directly.

 

The update site URL to use from Help > Install New Software... is:

 

http://download.jboss.org/jbosstools/updates/development/indigo/

 

Note: SOA tooling such as Drools, jbpm, ESB, Teeid etc. are not included in the JBoss Tools core releases at this time - they will be available separately.

 

OpenShift

The OpenShift platform is moving and improving all the time and this also shows in the OpenShift tooling included in JBoss Tools.

 

The most prominent and waited for feature in this release is we now support starting port forwarding from the IDE instead of using the command line.

And we've done it so it is even better and more powerful than the command line in a couple of situations:

 

  • it works on all platforms out of the box
  • it allows you to choose between using 127.0.0.1 or the remote addresses (especially good for Mac and Windows which needs configuration using 127.0.0.x)
  • it will find free ports if necessary avoiding you to have to stop your local running servers to connect to OpenShift

 

http://docs.jboss.org/tools/whatsnew/openshift/images/port-forwarding.png

 

To start/stop this you use the context menu of your OpenShift application in OpenShift Explorer (previously named OpenShift Console).

 

OpenShift Tools further more now allows you to put any existing application onto OpenShift where it previously only allowed Eclipse WTP projects. These projects can now even be multi-module Maven projects if you want to. This feature should be used with care since it overwrites your OpenShift application and your project content might not be working out of the box on OpenShift - thus use with care and if it fails

remember that OpenShift uses Git for it storage so you can roll it back in case of a failure.

 

And finally OpenShift tools also allows you to create scalable applications in the UI now.

 

http://docs.jboss.org/tools/whatsnew/openshift/images/create-scalable-applications.png

 

Annotation Processing w/Maven

 

Java EE 6 really started pushing more and more annotation processors and Eclipse APT provides a nice incremental integreation with this in Eclipse that makes it fast and non-invasive.

 

Unfortunately in context of Maven this have not always been easy to get configured since there exists multiple ways to invoke the Annotation Processor and in some cases Eclipse APT single-folder-output gives problems

 

With this release of JBoss Tools we are also releasing a configurator for m2e which combines all the best plugins concerning Annotation Processing and made something better and more integrated.

 

Fred Bricon have written a full blog about the feature set and how it works - if you use Annotation processing and maven I recommend you read it.

 

Google Web Toolkit (GWT) w/Maven

 

In our previous releases we have struggled with getting GWT examples to load into Eclipse without users having to tweak and manually run certain actions in specific sequence. The reason for this all came down to that there did not exist a m2e Configurator which takes the maven compiler plugin settings and apply them to Google's Eclipse plugin properly. With JBoss Tools Beta 3 that now exists and it just works.

 

Without this loaded you would have to manually add the GWT module xml to Eclipse and then perform a build based on that which would generate to possibly different output directories than your Maven project is configured to. With JBoss Tools for Maven loaded this a problem of the past.

 

Mobile Browser Simulator Skins

 

BrowserSim now has support for View Source, roatation of the screen by clicking in the corners and two new skins:

 

http://docs.jboss.org/tools/whatsnew/vpe/images/3.3.0.Beta3/browsersim-iphone4.pnghttp://docs.jboss.org/tools/whatsnew/vpe/images/3.3.0.Beta3/browsersim-android.png

 

...and finally as a team enjoying the wonders of Open Source we've added two things that could not exist without the source(s) being open:

 

JBoss Source Lookup

We've included the JBoss Source Lookup container which Snjezana have been working on that will scan a directory of jar's and use their Maven metadata and if necessary their MD5 checksum to locate the source code for any Launch configuration not just your Maven projects and Maven classpath provider.

 

This is useful when you have a server like JBoss, Tomcat, Glassfish or any other server or framework which jar's are mostly available in Maven repositories together with their source artifacts.

 

This allow you to fully debug your runtimes without having to pollute your classpath or Eclipse project configuration with runtime details, machine specific locations and manual download of the sources.

 

http://docs.jboss.org/tools/whatsnew/images/sourcelookuppreferences.png

 

The feature must be explicitly enabled, thus be sure to read Snjezana's wiki article outlining how to use this.

 

Eclipse Source Features

If you are into Eclipse plugin development and want to tinker with the source of JBoss Tools our updatesite now include a matching source feature for majority of our plugins under the Source category on the updatesite. This allows debugging and editing of JBoss Tools plugin without having to checkout our full SVN source tree. Contributions very welcome

 

...and more

 

As usual screenshots and more explanation of what is new is available from the What's New site!

 

Let us know what you think - and do know that we are codefreezing for CR1/GA any day now, so do let us know if you find big issues or simply just love it - both things is what keeps us going

 

Have fun,

Max

Maven Integration for Eclipse JDT Annotation Processor Toolkit a.k.a m2e-apt is now available in its version 1.0. m2e-apt aims at providing automatic Annotation Processing configuration in Eclipse based on your project's pom.xml and its classpath dependencies  (Requires Java >= 1.6).

 

m2e-apt supports both annotation processing set on the maven-compiler-plugin or the maven-processor-plugin (the latter takes precedence over the former).

 

For example, to enable the JPA modelgen annotation processor, you can either set :

 

<plugin> 
    <artifactId>maven-compiler-plugin</artifactId> 
    <version>2.4</version> 
    <configuration> 
        <source>1.6</source> 
        <target>1.6</target> 
    </configuration> 
    <dependencies> 
        <dependency> 
            <groupId>org.hibernate</groupId> 
            <artifactId>hibernate-jpamodelgen</artifactId> 
            <version>1.2.0.Final</version> 
        </dependency> 
    </dependencies> 
</plugin> 

 

or

 

 

<plugin> 
    <artifactId>maven-compiler-plugin</artifactId> 
    <version>2.4</version> 
    <configuration> 
        <source>1.6</source> 
        <target>1.6</target> 
        <compilerArgument>-proc:none</compilerArgument> 
    </configuration> 
</plugin> 
<plugin> 
    <groupId>org.bsc.maven</groupId> 
    <artifactId>maven-processor-plugin</artifactId> 
    <version>2.0.5</version> 
    <executions> 
        <execution> 
            <id>process</id> 
            <goals> 
                <goal>process</goal> 
            </goals> 
            <phase>generate-sources</phase> 
        </execution> 
    </executions> 
    <dependencies> 
        <dependency> 
            <groupId>org.hibernate</groupId> 
            <artifactId>hibernate-jpamodelgen</artifactId> 
            <version>1.2.0.Final</version> 
        </dependency> 
    </dependencies> 
</plugin> 

 

The generated source folders (target/generated-sources/annotation for maven-compiler-plugin; target/generated-sources/apt for maven-processor-plugin) are automatically added to the project classpath.

 

m2e-apt.png

By default, Annotation Processing is managed by Eclipse JDT APT, so a change in your source classes triggers incremental processing automatically. The downside of using JDT APT is, there's no separation between main and test classes (the way maven-processor-plugin handles them).

To mitigate that limitation, you can change the workspace or project preferences to delegate annotation processing to maven, instead of JDT APT. This will result in slower incremental builds (all classes will be processed) but will provide identical results to maven command line builds. Note this only works when using maven-processor-plugin. When annotation processing is driven by maven-compiler-plugin, JDT APT is always used in eclipse.

 

Automatic annotation processing configuration from the maven pom.xml can also be disabled altogether. In this case, your manual settings for Eclipse JDT APT will remain untouched.

 

Go to Window > Preferences > Maven > Annotation processing or right-click on your project > Properties > Maven > Annotation processing to select the Annotation Processing strategy of your choice.

 

m2e-apt-prefs.png

m2e-apt is heavily based on the work from two community members :

  • a patch for m2e by Karl M. Davis, from Knowledge Computing Corp, implementing Eclipse JDT APT configuration based on the maven-compiler-plugin's configuration.
  • com.excilys.ebi.m2e.apt  by Stéphane Landelle, from eBusiness Information, Excilys Group, implementing direct maven-processor-plugin invocation from m2e.

 

m2e-apt is available :

 

Source code is available at github. If you find any bug, please raise a ticket on m2e-apt's issue tracker.

 

Happy hacking,

 

Fred

https://twitter.com/#!/fbricon

This morning I woke up to an email stating that Christos Vasilakis had created an iPhone app to manage JBoss AS 7 servers from your phone, he even posted a video about it.

 

I tried it out immediatly and wanted to see how to use it against servers started by JBoss Tools. Since JBoss AS 7 is secured by default you have to do a few steps to make this work:

 

  1. Add a user to your JBoss Server with $JBOSS_HOME/bin/add-user.sh
  2. Set "Host name" to your local ip instead of localhost
  3. Add -Djboss.bind.address.management=<local ip> to the server launch configuration.

 

Note: These steps are not unique for the iPhone app, it's the exact same you would need to do for any remote management of your JBoss Tools started server.

 

To show how it all works together I recorded a screencast which shows the setup in tools and how to use the iPhone app.

 

 

If the video is not showing up for you then you can watch it directly on JBoss Tools vimeo group.

 

Thanks to Christos for making the app and hope you all enjoy managing your JBoss Tools started AS 7 server from your couch

Filter Blog

By date:
By tag: