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!

You can now nominate IzPack in the SourceForge 2008 Community Choice Awards in the category “Best Tool or Utility for Developers”:

We need your votes

BTW: IzPack is not a SourceForge project, but the awards are open to non-SourceForge projects.

… coming soon !

… c’est que je suis bien en train de rédiger ma thèse.

Last login: Sun Apr 20 02:03:13 on ttyp1
Welcome to Darwin!
stardust:~ julien$ history|awk '{a[$2]++} END{for(i in a){printf “%5d\t%s \n”,a[i],i}}’|sort -rn|head
  110   svn
  101   ./build.rb
   56   cd
   40   ls
   34   find
   16   mate
   14   ./izpack2app.py
   12   rm
   11   exit
    9   patch
stardust:~ julien$

Si vous ne l’avez pas encore fait, essayez la commande précédente dans un shell, c’est top-g33k-moumoute

Chez moi :

• Subversion et le script en Ruby qui me sert à compiler ma thèse (d’ailleurs depuis je l’ai modifié)
• TextMate, le Emacs moderne qui ne fait pas mal aux doigts (et en plus il est RMS-free)
• izpack2app.py et patch : pour faire un break j’ai appliqué pas mal de patches en attente pour IzPack (ça m’a pris à peine 1/2h et c’est bon pour les stats dans JIRA).

Bonne nuit à tous

The Mercurial project has just released its version 1.0!

Congratulations to the team behind this project for bringing what I personally consider as the very best distributed source configuration management tool to date (yes, I have already played with Bazaar and Git)

Mercurial is (much like Bazaar) written in Python. It is cross-platform, extremely efficient, extensible with plugins and last but not least, Mercurial is such a stupid tool to use! The interface and general workflow are no-brainers if you have already played with SCM before. You’ll get started in just a few minutes with it. I know that lots of geeks prefer playing with Git… but how can anyone understand the Git interface?

If you are currently considering a distributed SCM model, then I strongly suggest that you look at it, just like Mozilla and Sun did. Oh and if you happen to work with Windows boxes, there is still TortoiseHG for a seamless integration with the Windows explorer!