Exports Hybrid Mobile projects as XCode or Android projects.

Sister wizard to the Export Native Platform Project Wizard. Export Mobile Application Wizard creates compiled binary for running on the targeted platform(s).

Discover and install Cordova Plug-ins from a registry to your Hybrid Mobile projects. Wizard also enables installation of plug-ins via a Git repository or from a directory.

Extends the Project Explorer so that installed Cordova Plug-ins are visible, enables easy installation and removal of Cordova Plugins. Also enables the properties view for installed Cordova Plug-ins.

Content assist (Ctrl+Space) is now available for AngularJS ng-* and data-ng-* attributes in HTML:

image::images/4.1.1.Alpha2/ng-ca.png

Content assist (Ctrl+Space) now works for file names in the following HTML tags:

Properties view for HTML now supports multiple categories of properties. For example HTML image now has two categories: Often used and Advanced HTML. jQuery Mobile elements have three categories: Often used, Advanced jQuery and Advanced HTML:

OpenShift now allows you to have several domains. You may own multiple domains if you are on Silver Plan. But it’s also possible to get access to other peoples domains. JBoss Tools now supports these setups and lets you choose the domain you’re creating an application for.

The OpenShift Explorer now shows a domain-node.

And we offer you a wizard to create, rename and delete your domains.

Environment varibales in OpenShift allow you to easily customize your application at runtime. JBoss Tools allows you to provide environment variables when creating an application.

Existing applications may also have their environment variables modified.

In Beta1 we now allow you to inspect the log files on all gears of a scalable application. When executing "Tail Files…​" we’ll show you the number of gears that an application is running on.

We’ll then open a separate console for each of them and allow you to inspect all logs.

In Beta1 we start to warn you when you try to embed an incompatible cartridge. We’ll prmpt you with a warning that the non-scalable phpmyadmin cartridge cannot get added to a scalable application.

There is now a preference available to set the timeout used when waiting for OpenShift requests to complete. We’re using a default of 120 seconds (2 minutes) if no preference value (0) is provided. You can try raise this value if you are getting time out errors when using OpenShift.

When looking at the log files in your OpenShift application the tooling allows you to provide your very own settings. In Alpha2 we now store these personalized options on a per-application basis. This frees you from re-providing them.

You can create a new application with your very own source code since JBoss Tools 4.0.

use your own source code

There are openshift quickstarts that require long timeouts because the size of the source code being checked out is very large. Another frequent requirement is that embedded (add-on) cartridges have to be present when the application is created. Adding the cartridges in a 2nd step wont help; the initial application build fails. It was not possible, for example, to create the OpenShift wordpress quickstart at https://github.com/openshift/wordpress-example within JBoss Tools. The update to 4.1.1.Alpha1 fixed this.

The openshift-java-client now allows you to provide embeddable cartridges when you create an application. Previously these could only get added once the application was ready. This might be required when you use your own application template source.

The openshift-java-client now allows you to use a specific timeout in your operation. This is useful if you know that it takes much longer to create your application with your custom source than it takes for the default. Previously you had to increase the global timeout.