prepping for 0.4 release

git-svn-id: https://pmd.svn.sourceforge.net/svnroot/pmd/trunk@201 51baf565-9d33-0410-a72c-fc3788e3496d
This commit is contained in:
Tom Copeland
2002-07-03 15:11:08 +00:00
parent 32ea6cf151
commit 6d96b6a2e9
2 changed files with 12 additions and 12 deletions

View File

@ -1,3 +1,5 @@
???? 2002 - 0.4:
July 03 2002 - 0.3:
Added new rules: UseSingletonRule, ShortVariableRule, LongVariableRule, ShortMethodNameRule
Moved rules into RuleSets which are defined in XML files in the ruleset directory

View File

@ -1,23 +1,21 @@
update the xdocs:
-modified Ant task (see changelog for details)
-run.bat/sh third param is a rule set file
update run.bat to point to pmd-0.3.jar
update run.bat to point to pmd-0.4.jar
update the changelog
ant dist
ant test
Do all the tests run? OK, then:
ant dist
cvs add -kb pmd-0.3.jar
cvs rm pmd-0.2.jar
cvs add -kb pmd-0.4.jar
cvs rm pmd-0.3.jar
cvs ci -m "adding new jar, removing old one"
cd c:\data\pmd
cvs rtag -D tomorrow "pmd_release_0_3" pmd
cvs rtag -D tomorrow "pmd_release_0_4" pmd
rmdir /q /s c:\tmp\pmd
mkdir c:\tmp\pmd
cvs export -d c:\tmp\pmd -r pmd_release_0_3 pmd
zip it up, rename it to pmd-0.3.zip
unzip it into c:\tmp\pmd-0.3
cvs export -d c:\tmp\pmd -r pmd_release_0_4 pmd
zip it up, rename it to pmd-0.4.zip
unzip it into c:\tmp\pmd-0.4
clear classpath
TESTS: Can you
1) run 1 file and get a report
@ -27,7 +25,7 @@ run c:\data\pmd\pmd\test-data\Unused1.java html rulesets/unusedcode.xml
ant pmd
if you see a bug and fix it, you can delete the release using:
cvs rtag -d pmd_release_0_3 pmd
cvs rtag -d pmd_release_0_4 pmd
and then retag everything
FTP the zip file to SF
@ -35,11 +33,11 @@ ftp upload.sourceforge.net
generic userid/password: anonymous/tomcopeland@users.sourceforge.net
cd incoming
bin
put pmd-0.3.zip
put pmd-0.4.zip
Go to Admin, Edit/Release Files, click on Add new release
Paste stuff into the changelog/readme boxes
Add the pmd-0.3.zip file
Add the pmd-0.4.zip file
Classify the file
SSH in to shell.sourceforge.net