jcmdline Developer Info

Introduction
Running a Single UT
Releasing a New Version of jcmdline

Introduction

This document contains information for developers working on the jcmdline package. It is not too complete a document, but will be added to as necessary. This project is hosted on SourceForge. Any work on this project should be done from a CVS copy of the source files.

[toc]

Running a Single UT

To run a single unit test, the "ant utone" target can be used.

Alternately, it is sometimes simpler to just run from the command line and see the output. An environment file, jcmdline.env, can be sourced into the user's environment (might want to modify this to suit your environment). A unit test may then be run from the command line:

java jcmdline/StringParam_UT

or even a single test within the UT:

java jcmdline/StringParam_UT testMaxLength

A list of tests within a UT file can be obtained with the -help option:

java jcmdline/StringParam_UT -help

[toc]

Releasing a New Version of jcmdline

These are the current notes for releasing a new version of the jcmdline package. At some point it would be nice to have ant do more of this automatically, but since the process is still being experimented with, I am leaving much of it manual. To release a new version of the package:

Up the release number in the build.xml file.
Document changes in the CHANGES file (this is easiest to do as you go along).
Run "ant dist", which will clean, build, run all UTs to verify all is well, and create distribution files.
Commit all code changes in CVS.
Tag the release: "cvs tag rel-1-0 ." from the jcmdline directory.

FTP distribution files to sourceforge:

cd dist
[me]: ftp upload.sourceforge.net
Connected to osdn.dl.sourceforge.net.
220 ProFTPD 1.2.0pre10 Server (ftp1.sourceforge.net) [66.35.250.221]
500 AUTH not understood.
500 AUTH not understood.
KERBEROS_V4 rejected as an authentication type
Name (upload.sourceforge.net:lgl): anonymous
331 Anonymous login ok, send your complete e-mail address as password.
Password: my_email
ftp> bin
200 Type set to I.
ftp> cd /incoming
250 CWD command successful.
ftp> prompt off
Interactive mode off.
ftp> mput *

Use the admin forms on SourceForge (project Admin page, select Edit/Release Files). For the release name, use the release number (i.e. 1.0.3...). Upload the ./CHANGES file where requested; click the "Keep my formatting" button.

Update the SourceForge homepage by doing the following:

Run "ant webpkg" to generate a gzipped tarfile of the homepage and docs.

scp it to userspace on SourceForge:

cd build/tmp
scp homepage.tar.gz myUserName@shell.sourceforge.net:homepage.tar.gz

Log onto sourceforge shell server and unpack the file in the webspace:

[local]: ssh -l myUserName shell.sourceforge.net
[onSF]$ gunzip homepage.tar.gz
[onSF]$ cd /home/groups/j/jc/jcmdline/htdocs
[onSF]$ tar xf ~/homepage.tar
[onSF]$ cd
[onSF]$ rm homepage.tar

From email by Alexander Ivanyukovich (java foundry guide):
If you want further announces to appear in either Announces or News, submit them through "Suggest news" or "Submit news" link on the foundry page. It will be really good, if you can use the following structure(also, your announce will be approved faster):
```
  <URL where I can find your product logo, up to 100 x 100 px - optional>
  <short product description - 2-3 sentences>
  <product homepage link>
  Changes:
  <list of changes>
```