update the release date in the changelog
grab the latest pmd.jar file

Create the binary release, i.e., zip upthe PMDOpentools.jar file
move the zip file into c:\tmp

Create the src release:
cd lib
cvs add -kb PMDOpenTools-0.4.jar
cvs rm PMDOpenTools-0.3.jar
cvs ci -m "adding new jar, removing old one"
cd c:\data\pmd
rmdir /q /s pmd-jbuilder\build
cvs rtag -D tomorrow "pmd_jbuilder_release_0_4" pmd-jbuilder
rmdir /q /s c:\tmp\pmd-jbuilder
mkdir c:\tmp\pmd-jbuilder
cvs export -d c:\tmp\pmd-jbuilder -r pmd_jbuilder_release_0_4 pmd-jbuilder
zip it up, rename it to pmd-jbuilder-src-0.4.zip

unzip binary release into the JBuilder lib/ext directory
TESTS:
1) Can you run jbuilder ok?
2) Can you run it it on a file and find some unused code?

if you see a bug and fix it, you can delete the release using:
cvs rtag -d pmd_jbuilder_release_0_4 pmd
and then retag everything

FTP the zip file to SF
ftp upload.sourceforge.net
generic userid/password: anonymous/dcraine@infoether.com
cd incoming
bin
put pmd-jbuilder-src-0.4.zip
put pmd-jbuilder-bin-0.4.zip

Go to Admin, Edit/Release Files, click on Add new release
Paste stuff into the changelog/readme boxes
Add the pmd-jbuilder-src-0.3.zip file
Add the pmd-jbuilder-bin-0.3.zip file
Classify the file

Submit some news saying "hey, new release of the jbuilder plugin!"
====================================================================
Fixed in CVS, and you can download an updated PMDOpenTool.jar file here:

http://infoether.com/~tom/PMDOpenTool.jar

that fixes this bug.  To use the file, stop JBuilder, place PMDOpenTool.jar in your jbuilder/lib/ext directory, and restart JBuilder.

Please note that this new file depends on pmd-3.2.jar, so you'll need to download the pmd-3.2 release and unzip it and copy the lib/pmd-3.2.jar file into the same directory.  Or if you prefer, you can just wait until I do the next formal JBuilder plugin release.

Thanks for the report!

Yours,

Tom