JAG (Java Application Generator) is an Open Source project hosted at JAG consists of the JAG Application and JAG modules needed by the JAG generated applications. Both the JAG Application and the JAG modules are maintained at sourceforge.

This Manual describes the steps required for a JAG release manager to create a JAG release, update the JAG website documentation and developers documentation. Part of the manual is still in Dutch.

Using Sourceforge with putty and WinCVS

Configure Putty

This section will describe how to access sourceforge using the Putty ssh client.

First download and install Putty (The comple zip version with all tools like: plink, pageant, putty etc..).

First you should use Putty to create a private key and publish your public key on sourceforge site.

With putty a a profile should be defined for and pageant should be used to load your private key whenever you access JAG on SourceForge using SSH. Make sure you set the preferred SSH version to 1

With putty a private key can be created using: RSA (SSH1) key, 128 bits. (This is the default). Upload the public key to sourceforge (

Create a bat file: ssh_cvs.bat c:/apps/putty/plink -ssh -1 -i c:\apps\putty\identity.ppk %1 %2 %3 %4 %5

Make sure the -i optie points to your private key created with putty.

Using WinCVS over SSH

Oncy putty has been configured, SourceForge CVS over SSH can be used with WinCVS.


- WinCVS: -

In WinCVS preferences: Authentication: ssh

Path: /cvsroot/jag Host:

User: ekkelenkamp (Should be your sourceforge account name).

CVSRoot should be:

SSH settings: Select a SSH client; make it point to the bat file: c:/apps/putty/ssh_cvs.bat

Test using plink if you can login : plink . This should succeed without entering any password.

Now you can checkout jag. Make sure you don't checkout over an existing CVS tree that was checkoud as guest. That will give problems.

Releasing JAG


Using a script file for making a JAG release:

1) First make sure alle sources are checked in and up-to-date and create a tag called JAG_vX_X_X. For example: JAG_v1_3

2} Maven is used to create a distribution. Use maven dist to create both a source and binary distribution

3) On the SourceForge website, go to 'File Releases' in 'Admin' and make a new release 'jag_vX-Y-Z' from the 'stable' branch. Enter the release and change notes (You can use the notes from a previous release as the base).

6) Use ftp to upload the two zip files to: : login anonymous (Just use enter as the password) - 'put' de two zip files into de 'incoming' map (Don't forget to use binary mode: "bin" )

7) Back to the SourceForge website: refresh the page to be able to select the zip files - After selection of a zip file, select the following options: platform-independent, zip, (no-)sources.

8) Also make a news release (Also using the SourceForge website), and also the websites 'news' page.

Releasing JAG Modules

For most modules that can be built with Maven, the j2ee.jar should be available in the local repository. Put it in the download/jars/j2ee.jar . For some modules also the oracle driver is needed. This driver should also be stored in the local repository at download/jars/classes12.jar Build a new distribution with maven jar Build a website using: maven site

Every JAG module has a maven project file frrom which the module can be built. To build a module, use the first command and to deploy the jar to the JAG website, use the second command:

maven -Dmaven.username=ekkelenkamp jar

maven -Dmaven.username=ekkelenkamp jar:deploy

Updating the site documentation can be done using a simple command. The first command shows how to build a site for a JAG module, the second command shows how to deploy the site to JAG (it will actually be deployed to:

maven -Dmaven.username=ekkelenkamp site

maven -Dmaven.username=ekkelenkamp site:deploy

The only exception is the sequence-generator module that needs to be built with ANT (because it generates an EJB and depends on XDoclet).