Atlassian just released JIRA 6 with a bunch of new features besides a new and simplified style. You can get a quick overview by visiting the “what’s new” pages or have a deeper look at the full release notes. In summary, JIRA 6 is about:
- simpler and smarter style with automatic look and feel based on your logo
- support for mobile devices
- ease of use and efficiency (e.g. detail view of issues besides the filter result you came from)
- many improvements for the administration (sharing of workflows, renaming usernames, …)
You can see JIRA 6 in action by visiting Atlassian’s public JIRA instance.
For plugin developers, JIRA 6 is a big change, but the “Preparing for JIRA 6.0″ guide will help you to make the necessary changes.
Veröffentlicht unter Atlassian Tools
Verschlagwortet mit atlassian, jira, Plugin, release
SpringSource, the company behind the popular Spring Framework announced “Reactor” as:
We’re pleased to announce that, after a long period of internal incubation, we’re releasing a foundational framework for asynchronous applications on the JVM which we’re calling Reactor. It provides abstractions for Java, Groovy and other JVM languages to make building event and data-driven applications easier.
This means Reactor is supposed to be used with the whole variety of JVM languages. For Grails there will be built-in support in the future:
[...] so from version 2.3 on, Grails applications will have a built-in, extremely powerful yet easy to use, convention-based Events API that looks very similar to the current implementation in the platform-core plugin. This Events API will be built on a Reactor foundation.
… will be very exciting. Daniel Kurka, member of the GWT Steering Comittee, published his and Ray Cromwell‘s slides of their Google I/O session “GWT Roadmap for the Future”.
First of all, there is a new GWT project page created by the steering committee. The project site seems to be better structured than the current one, at least the documentation and the articles are first class citizens now…
For example: stumbling across the page I found a nice video from Andrew Bowers introducing the GWT SDK. I can’t say if the view was already there in the past. If so, it was so nicely hidden that I was not able to find it.
So, what about the GWT future? Well, from what we can take from the slides, there is really a lot to come. The upcoming releases will be focussing on the following goals:
In our comparative study about the runtime behavior of both JSF implementations we came to the conclusion that Apache MyFaces performs significantly better on large component trees than the reference implementation Oracle Mojarra. The duration Mojarra took to step through the JSF lifecycle was increased by factors compared to MyFaces, e.g. a view containing 1.000 components took more than 5 times longer to render with Mojarra. This led to the assumption that the overall performance of Mojarra-based JSF applications may improve notably by simply switching the implementation to MyFaces. Weiterlesen
Google announced Android Studio at the keynote of Google I/O 2013. Android Studio is an Android focused IDE based on the community edition of IntelliJ IDEA.
In the keynote you can see some really nice features as:
- Externalized Strings and used icons are displayed in the code editor
- Layouts are rendered beside the editor
- Rendering of Layouts for different screen sizes or languages
You can find more information and an “Early Access Preview” on the Android Developers Website.
Veröffentlicht unter Politics
Verschlagwortet mit Android, Google, IDE, IntelliJ
JavaFX does not run on iOS out of the box. One of the approaches to run JavaFX on iOS is based on an AOT compiler like RoboVM.
Niklas Therning managed to port a JavaFX (OpenJFX) application to iOS using RoboVM:
In a news bulletin Oracle recently announced that they will change the version numbering scheme for the next upcoming releases of the JDK. The new scheme will affect the way that update release numbers are assigned for all upcoming releases of JDK 5.0, JDK 6 and JDK 7.
According to Oracle, the following rules will be applied for assigning update release numbers:
- Limited Update releases will be numbered in multiples of 20.
- [Oracle intends] for Critical Patch Updates to continue to use odd numbers. The numbers will be calculated by adding multiples of five to the prior Limited Update and when needed adding one to keep the resulting number odd.
The main reason behind this decision is to assure that there will be several unused numbers between individual releases so as to allow for the insertion of unscheduled releases, such as security alerts or support releases without having to renumber existing releases. This will ensure backwards compatibility with software systems expecting the traditional version numbering scheme of the JDK and allows to create predictable release numbers for future Java releases.
You can read the full text of the news bulletin here.