You may have noticed a new item in the "Get Involved" section at the upper left of the java.net home page: Java.net Enhancements. This is a new feature that's been added as a way to enable the broader java.net community to identify potential enhancements to java.net that are most important.
The Java.net Future Enhancements provides many different ways of looking at enhancements that are being considered for the site. The default view briefly describes several of the proposed enhancements, and lets you vote your view of the importance of each item or add a comment. Clicking on an item's title brings you to a detail page for that proposed enhancement, where you can see the already-posted comments, or post your own comment.
The rating system for the importance of each proposed enhancement is as follows:
5 stars: Must have!
4 stars: Very useful
3 stars: Useful
2 stars: Could be useful
1 star: Don't care
These additional enhancement views are also available:
List view - view a summary table of proposed enhancements, with statistics on number of views, comments, and the target schedule for implementation (if a date has been set)
If you don't see an enhancement you consider important on the Java.net Future Enhancements page, you can visit the Wish List Forum or the java-net project issue list. If still don't see the enhancement you're interested in, you can enter it as a new enhancement request, and it will be given consideration by the java.net development team.
Here are a few tips and tricks to get faster OpenJDK builds. * RAM: RAM is cheap, if you don't have at least 2Gb RAM, go buy yourself some RAM for Xmas. ;^) * LOCAL DISK: Use local disk if at all possible, the difference in build time is significant. This mostly applies to the repository or forest you are building (and where the build output is also landing). Also, to a lesser degree, frequently accessed items like the boot jdk (ALT_BOOTDIR). Local disk is your best choice, and if possible /tmp on some systems is even better. * PARALLEL_COMPILE_JOBS=N ...
It's been a
hard year,
but the GlassFish community has kept pushing v3 onward and all the indicators are
that the result is very much worth the effort. The target date for GlassFish v3 is mid-December so the last few weeks have been very busy
- check out these MarkMail charts: ...
They will, of course, not remove anything to make room, so Java just gets bigger and bulkier. They will also give us a half-hearted implementation that removes some interesting pieces that would make it backwards incompatible, so we're getting really aren't closures after all. Did Sun learn nothing from the generics debacle? Most tellingly, despite all the talk of openness, this seems to very much be Sun's decision. There's no proposal in the JCP, and all discussion of this seems to have purely been internal to Sun. If you aren't eating lunch in the Sun cafeteria, you don't get to chime in. Sun simply presented the decision as a fait accompli to the community. First they decided they wouldn't do closures in Java 7; then they decided they would; and now they'll decide how and when. Scala's looking more attractive by the hour.
Test-Driven Development, or TDD, is often quoted as an essential Agile best practice, and so it is. It works wonders on green-fields projects and new code bases where you can start afresh and ensure that all your code is both easily testable and well tested. But what about legacy code? (By legacy code, I mean any code that does not have a comprehensive set of automated tests, so you might be writing legacy code as we speak). For most of us, most of the code we will ever work on will not have originally been our own work. And, unfortunately for the software industry, only a small fraction of code can really boast comprehensive unit and integration tests. How can techniques like Test-Driven Development make our work as developers more productive and less frustrating? ...
When we start working on a new project as an architect we are dealing basically with a set of requirement which our architecture should be able to act as a foundation for the design and implementation of those requirements in form of a software system. to let the customer fulfill its requirements in a better and more efficient way. Preparing the architecture for a software system means not only the architect to be familiar with the domain but also he should well aware of new technologies, frameworks, COTS, and standards available not only for the domain he is working on but also for the development platform which will realize the architecture into a working piece of software...
My latest example of an API that would benefit from support by a RDF
store was the "Observation
API" and focused on modeling a set of observations made by
some subjects and related to some places (I'm keeping birds and
birdwatchers in mind, but it's only a special case): ...
In the Forums, bradmiley is seeing jerky animations: "My animations are consistently not smooth. A create an animation of duration one second. Below is an example of the of the fraction of the percent of the animation elapsed. Note the huge jump from 0.381 to 0.629 that causes the jerky behavior. I..."
nareshdoni has a problem with Image scroll: "I was trying to make the image scrollale . but I could not able to do that. any help is highly appreciated. I have given my source code below. Suggest mw where I have to make changes. public FloorPlanDisplayable(YasmoLive _ParentMIDlet,..."
hiraldesai needs to Display commands as buttons on Dialog: "HI, I am trying to display the commands of a dialog as buttons on the dialog.This can be achieved by using the static methods on Dialog : 1.Dialog.setCommandsAsButtons(true) 2.Dialog.show("title",Component,cmds[]) ..."
In our current Spotlight, Terrence Barr invites us to Check out Java Card 3.0 Connected Edition: Real Java, just really flat ;-): "Java Card 3.0 was released a couple of months ago – and the second update (version 3.0.2) is scheduled for December. If you haven’t paid much attention to Java on smart cards because you thought it’s not “real” Java – well, look again. It’s true that Java Card 2 was very limited in many ways – a testament to the kind of technology you had available on smart cards 10 years ago. There are billions of these out there today..."
Registered users can submit event listings for the java.net Events Page using our events submission form. All submissions go through an editorial review before being posted to the site.
Archives and Subscriptions: This blog is delivered weekdays as the Java Today RSS feed. Also, once this page is no longer featured as the front page of java.net it will be archived along with other past issues in the java.net Archive.
Previous Topic
