Thursday Dec 01, 2011

Adopt a JSR, a JUG initiative for you. Yes, you!

Adopt-a-JSR is a recent initiative by multiple JUGs (I believe the ever-active LJC started this) to encourage community participation in the JCP and more specifically in making concrete progress in developing new JSRs.

Some of that is a consequence of the JSR 348/JCP.next increased transparency and early results are very encouraging with serious progress made on the JSR-310 TCK for instance. A recently-added grid should provide and idea of the community and JUG efforts on specific JSRs.

Let's get going Duke

As the program page on java.net says - "It looks great on the CV". In fact I think that resume-wise nothing beats serious contributions to industry-wide standards or open source projects and that's probably true around the world.

Tuesday Oct 18, 2011

JCP.next Final Approval Ballot - We have a go!

As previously explained, JSR 348 is there to change the JCP itself and add transparency to the process.

The results for the Final Approval Ballot are in with 25 YES votes, 2 ABSTAIN votes (Google and Vodafone), one NO vote and 4 non-votes (both Executive Committees were voting). And that's 5 months to complete a JSR from the day it was filed.

ALT_DESCR

Here are two (pseudo) random changes taken from the proposed final draft to give you sense of what will change :

"Attendance at meetings is mandatory. Missing two meetings in a row (whether teleconference or face-to-face meetings) results in loss of future, not yet started, JSR ballot and EC voting privileges."

"The Maintenance Lead must submit to the PMO at least quarterly a list of all implementations that have been certified as compatible and that have been released publicly or commercially. The PMO will publish this information on the JCP website."

For the latter part, Sun and now Oracle has been publishing the list of certified Java EE implementations.

Also, remember that this the first of two JSRs to change the JCP itself (the shorter one too). And in other JCP news, a new voting period has started, closing on October 30th (see list of SE/EE nominees, some really strong ones...).

Update: the JCP blog has more details on the EC ballot.

JCP.next Final Approval Ballot - We have a go!

As previously explained, JSR 348 is there to change the JCP itself and add transparency to the process.

The results for the Final Approval Ballot are in with 25 YES votes, 2 ABSTAIN votes (Google and Vodafone), one NO vote and 4 non-votes (both Executive Committees were voting). And that's 5 months to complete a JSR from the day it was filed.

ALT_DESCR

Here are two (pseudo) random changes taken from the proposed final draft to give you sense of what will change :

"Attendance at meetings is mandatory. Missing two meetings in a row (whether teleconference or face-to-face meetings) results in loss of future, not yet started, JSR ballot and EC voting privileges."

"The Maintenance Lead must submit to the PMO at least quarterly a list of all implementations that have been certified as compatible and that have been released publicly or commercially. The PMO will publish this information on the JCP website."

For the latter part, Sun and now Oracle has been publishing the list of certified Java EE implementations.

Also, remember that this the first of two JSRs to change the JCP itself (the shorter one too). And in other JCP news, a new voting period has started, closing on October 30th (see list of SE/EE nominees, some really strong ones...).

Update: the JCP blog has more details on the EC ballot.

Wednesday Oct 11, 2006

GlassFish Issue 539: Problems with Locked JARs

Diagram of a Normal GF Deployment

If you are using GlassFish on Windows and are deploying via archives (like EAR, a WAR, an EJB JAR, or an app client JAR) you may have encountered a variation of GlassFish Issue 539 where a problem during deployment leads to a locked JAR that requires a server restart. The good news is that Tim and Hong have checked in changes to address this problem: when possible the problem no longer occurs and, when it does, there is a nice error message that leads to a prompt resolution.

Expect the fix in the next promotion of GlassFish V2. Check Tim's Blog for a detailed description of the problem and the solution.