Both Oracle JDK and OpenJDK 1.7 update 40 have a known issue when creating temporary files (see http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=8025128 and https://bugs.openjdk.java.net/browse/JDK-8025128), preventing JBoss Central from fetching informations and remote project examples.
We fixed JBoss Central to work around this issue but you may still encounter difficulties with other IDE tools (m2e, p2, subclipse…). If this is the case, use an alternative version of Java developer kit 1.7 before or after update 40 (fixed in 1.8 and set to be included in 1.7 update 45).
Related JIRA: JBIDE-15494
JST / JSF / HTML Editor
Content assist (Ctrl+Space) is now available for AngularJS ng-* and data-ng-* attributes in HTML:
Related JIRA: JBIDE-15378
This release of JBoss Tools LiveReload brings support for Asciidoc files (.adoc and .asciidoc). Using a basic Text Editor in combination with the LiveReload tooling and the Asciidoctor.js Chrome extension and FireFox add-on, users will now have instant reload of their documentation in their browser !
Related JIRA: JBIDE-15506
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.
Related JIRA: JBIDE-15389
Web Services Tools
A few bugs were fixed in the JAX-RS Tooling for this version of the Web Services component. In particular:
If a Web application contained 2 JAX-RS Application definition (in Java classes and/or as a declaration in the deployment descriptor), a warning on both elements would be set. But if the user removed one of those elements to fix the problem, the warning on the other element would remain. This is now fixed, the warning on the remaining is also removed.
Related JIRA: JBIDE-12860
When refactoring an annotation (such as a custom CDI qualifier), the JAX-RS Tooling would complain if the @Target was incorrect, even though the annotation was not related to JAX-RS. This is now fixed, the JAX-RS tooling checks that an @HttpMethod meta-annotation is set on the user’s annotation to validate it.
Related JIRA: JBIDE-15508
If a Web application contained 2 JAX-RS Application definition (in Java classes and/or as a declaration in the deployment descriptor), there would be 2 warnings on each of those elements. This is now fixed, and only 1 warning will appear on each element.
Related JIRA: JBIDE-15504