Ce post me servira de pense-bête, et peut-être à vous aussi

J’ai changé par mégarde la sonnerie de notre téléphone de bureau l’autre jour, sans savoir pourquoi ni comment celle-ci avait changé. Évidemment nous nous sommes retrouvés avec une sonnerie horrible : un bip qui ressemble à un reboot de PC

La solution est assez simple :

1. appeler sur le téléphone Alcatel (depuis un autre téléphone évidemment …)
2. appuyer sur 1, 2, 3 ou 4 pour choisir une sonnerie

Et voilà !

Subversion 1.5.0 est officiellement disponible !

Le principal apport de cette version est qu’il va enfin être possible de fusionner des branches de façon simple et intuitive. En effet la technique habituelle pour gérer des fusions répétées entre deux branches consistait jusque là à noter le numéro de révision de la dernière fusion pour le réutiliser dans la prochaine fusion.

The IzPack Glassfish installer has just been updated. It now provides a deeper integration on Windows systems.

Shortcuts to asadmin, the update center and the uninstaller are now created in the start menu hierarchy:

The Windows Add / Remove Software settings box will also display an icon for the Glassfish installation:

Lastly, the installer was generated from a snapshot of the IzPack Subversion trunk.

Oh and I forgot one more thing: the Glassfish installer has been downloaded at least 1326 times in May

I am a big fan of JIRA, a nice and powerful issues tracker that was created by the aussies at Atlassian. Part of the reason why IzPack joined Codehaus is that they provide a first-class infrastructure for their projects that includes a JIRA instance.

One thing that is highly important when you manage a JIRA project is to take some time to set-up a customized dashboard.

A customized dashboard is extremely helpful to have some stats on your project and don’t loose a bit of information on important issues. Leave an issue without at least an acknowledgment that someone took notice of it and your project will get a bad reputation quickly by making unhappy users.

Here is an overview of my dashboard for IzPack at Codehaus:

The first piece of information that I like to have is a roadmap and progress bars for the upcoming releases. Just below it a created vs resolved issues graph gives me an overview of where we are going with the project handling of issues. There will always be more issues created than resolved, but what is important is to measure how the gap between them evolves over time.

I then put some fancy graphs regarding the issues. They are nice to have and certainly useful.

On the right hand of my dashboard I keep a list of important issues. Those views play a highly critical role in my case.

• I track the issues that have been assigned to me. Memory is a versatile resource
• The unassigned and unresolved issues are quite important. Those ones need to be checked, assigned, scheduled or closed quickly if invalid. Enhancements and new feature requests can stay here for a while. This should however not the case for bug reports.
• The unscheduled issues are open and not yet scheduled, but at least someone has been assigned to them.

As I am still learning JIRA, feel-free to drop suggestions on how I could be even more efficient with it

Building Glassfish v3 from its Subversion trunk is relatively easy.

The first thing to do is to create an account on Java.net, else you won’t be able to perform any checkout. I believe that it is sufficient, but thing is you will be prompted for a user name and password by your Subversion client…

Next, you should point to the Glassfish-SVN project on Java.net, not to the regular Glassfish project as it uses CVS, and everyone knows how painful CVS can be (Subversion is not perfect either, especially on merges or tracking of upstream vendor branches…).

Checkout a fresh copy of the trunk:

svn checkout https://glassfish-svn.dev.java.net/svn/glassfish-svn/trunk/v3 \
      glassfish-v3-trunk --username YOUR_JAVANET_USERNAME

What you get is a bunch of Maven projects. The organization of the v3 repository is well done. For a comparison, go and have a look at the v2 one which embeds a lot of stuff that should not be under version control like Javadocs…

The next step is of course to grab and install Maven if you don’t have it on your local machine. You could go straight with Maven and build Glassfish, but there are a few caveats.

1. The build will fails if you don’t enlarge the JVM stack size, so you should

    export MAVEN_OPTS=-Xmx512m
   

   or something similar depending on your operating system and current shell.

2. Maven downloads a ton of bits from the net, so don’t forget to define a HTTP proxy if you need to.
3. Unit tests may fail (this is a trunk!) and Maven stops building when unit tests fail: you can disable them by passing the

   -Dmaven.test.skip=true

   parameter to Maven.

Building Glassfish is easy, from the root of your trunk checkout, just launch the Maven install and package goals, e.g.:

mvn install package -Dmaven.test.skip=true

The build may take a while, especially as Maven has to download a lot of plugins and dependencies. Once this is done, you can find a zipped image of Glassfish in

(your-trunk)/distributions/glassfish/target/glassfish-10.0-SNAPSHOT.zip

.

Hopefuly one day the Maven build will call the nice IzPack Maven plugin that our new developer Dan Tran contributed

You can then easily test Glassfish:

unzip glassfish-10.0-SNAPSHOT.zip
cd glassfish
java -jar modules/glassfish-10.0-SNAPSHOT.jar

Have fun hacking Glassfish!