The objective for the Jabox version 0.1.0 is to have a kickoff a maven project in 4 clicks (counting the downloading of Jabox itself), with the only requirement to have a Java JRE installed already:

• Download Jabox
• Login
• Create Project
• Submit

With this you will get the following:

• The creation of an embedded Subversion repository hosted locally to your computer at ${user.dir}/.jabox/svnRepo/
• The creation of a directory for your project in Subversion.
• The creation of the subdirectories trunk/tags/branches as the best-practices recommend.
• The generation of your project skeleton by a selected maven archetype.
• Injection inside your pom.xml configuration about the whereabouts of your development services:
  • scm
  • issuemanagement
  • cimanagement
  • distributionmanagement
• The commit of your project skeleton to the Subversion trunk/ directory.
• Configuration of the project’s target/ directory to be ignored by the Subversion.
• The creation of a new job for an embedded instance of Hudson configured to check-out the code from the Subversion repository and monitor the Subversion for changes.
• Configuration of Hudson to download and install automatically the latest Java and Maven versions.
• An automatic trigger to the new Hudson job.
• Automatic upload of the generated binaries to an embedded instance of a Repository Manager.

This way you get your first automatic build before even writing one line for your project. You can now launch your favorite IDE (e.g. Eclipse, Netbeans etc.) to start your development.

You can find the exact subversion URL on the Servers page in order to check-out your new project. Then if you do a new commit on the code, in a matter of seconds you will find a new binary of your project waiting for your in the Repository Manager.

Of course, in order to have optimal performance, you could move the Jabox instance to a dedicated server so that you don’t have the automatic builds eat the CPU of your developer PC. Just move the ${user.dir}/.jabox/ directory to your new server and you can continue from where you left.

Of course, If you already have some or all of those services running, you can configure Jabox to use those instead for the generation of the new projects.