rls preps

git-svn-id: https://pmd.svn.sourceforge.net/svnroot/pmd/trunk@3869 51baf565-9d33-0410-a72c-fc3788e3496d

pmd-jbuilder/etc/doing_the_next_pmd_jbuilder_release.txt

@@ -1,46 +1,54 @@
-update the release date in the changelog
+Update the release date in the changelog
-grab the latest pmd.jar file
+Update the version number in build.xml and README.txt
 
-Create the binary release, i.e., zip upthe PMDOpentools.jar file
+ant dist
-move the zip file into c:\tmp
+rm -rf ~/tmp/pmd-jbuilder-1.3/
+mkdir -p ~/tmp/pmd-jbuilder-1.3/
+cp ../lib/pmd-3.3.jar ../lib/PMDOpenTool.jar ../lib/jaxen-1.1-beta-7.jar ~/tmp/pmd-jbuilder-1.3/
+cp ../LICENSE.txt ~/tmp/pmd-jbuilder-1.3/
+cp ../lib/ReadMe.txt ~/tmp/pmd-jbuilder-1.3/
+cd ~/tmp/pmd-jbuilder-1.3
+zip -q -r ../pmd-jbuilder-bin-1.3.zip *
+cd -
+
+CVSROOT=:ext:tomcopeland@cvs.sourceforge.net:/cvsroot/pmd && export CVSROOT
+cd ../../
+cvs -q tag -D tomorrow "pmd_jbuilder_release_1_3" pmd-jbuilder
 
 Create the src release:
-cd lib
+rm -rf ~/tmp/pmd-jbuilder-1.3
-cvs add -kb PMDOpenTools-0.4.jar
+rm -rf ~/tmp/pmd-jbuilder-1.3.zip
-cvs rm PMDOpenTools-0.3.jar
+cd pmd-jbuilder/etc/
-cvs ci -m "adding new jar, removing old one"
+ant jarsrc
-cd c:\data\pmd
+cd ../../
-rmdir /q /s pmd-jbuilder\build
+rm -rf tmp/
-cvs rtag -D tomorrow "pmd_jbuilder_release_0_4" pmd-jbuilder
+mkdir tmp
-rmdir /q /s c:\tmp\pmd-jbuilder
+cd tmp
-mkdir c:\tmp\pmd-jbuilder
+cvs -q export -r pmd_jbuilder_release_1_3 pmdjbuilder
-cvs export -d c:\tmp\pmd-jbuilder -r pmd_jbuilder_release_0_4 pmd-jbuilder
+mv pmdjbuilder/ pmd-jbuilder-1.3/
-zip it up, rename it to pmd-jbuilder-src-0.4.zip
+cd ..
+cp pmd/lib/pmd-jbuilder-src-1.3.jar tmp/pmd-jbuilder-1.3/lib/
+mv tmp/pmd-jbuilder-1.3/ ~/tmp/
+cp pmd-jbuilder/lib/PMDOpenTool.jar ~/tmp/pmd-jbuilder-1.3/lib
+cd ~/tmp/
+zip -q -r pmd-jbuilder-src-1.3.zip pmd-jbuilder-1.3/
 
-unzip binary release into the JBuilder lib/ext directory
+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
+cvs rtag -d pmd_jbuilder_release_1_3 pmd-jbuilder
 and then retag everything
 
-FTP the zip file to SF
+ncftpput upload.sourceforge.net incoming/ pmd-jbuilder-src-1.3.zip pmd-jbuilder-bin-1.3.zip
-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 files and then classify them
-Add the pmd-jbuilder-bin-0.3.zip file
-Classify the file
 
-Submit some news saying "hey, new release of the jbuilder plugin!"
+Submit some news saying "hey, new release of the JBuilder plugin!"
 ====================================================================
 Fixed in CVS, and you can download an updated PMDOpenTool.jar file here:
 
@@ -48,8 +56,6 @@ 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,

pmd-jbuilder/lib/ReadMe.txt

@@ -5,3 +5,5 @@ pmd-3.3.jar
 jaxen-1.1-beta-7.jar
 
 Once you restart JBuilder the toolbars and menus should reflect that PMD is now available.
+
+PLEASE NOTE: If you have been using previous verisons of this opentool, and the version of the pmd.jar file has changed, you need to remove the old pmd.jar file (pmd-3.2.jar for example)

pmd-jbuilder/src/README.txt

@@ -1,14 +0,0 @@
-To install this plugin, simply place the PMDOpenTool.jar and the
-pmd-3.3.jar (again, whatever version) into the JBuilder/lib/ext directory.  PLEASE NOTE:  if you
-have been using previous verisons of this opentool, and the version of the pmd.jar file has changed,
-you need to remove the old pmd.jar file (pmd-3.2.jar for example)
-
-The PMD_Jbuilder OpenTool requres the pmd-x.x.jar file to run (where x.x is the major/minor version id).
-Although the openTool has no other special requirements, the PMD utility does.  PMD also requires that Xerces
-and Ant be available in the JBuilder classpath as well.  This is not an issue for JBuilder 6/7 Enterprise users
-since those libraries come preinstalled.  However, users of the Professional/Personal versions may have to
-put those libraries into their JBuilder lib directory manually.  I have not tested on anything other than
-JBuilder 7 Enterprise, but the tool should run fine on most of them given the aforementioned changes.
-
-JBuilder 4 Users - The PMD Check Project and CPD Check Project operations will only work if you have packages 
-defined in your project view.  This is because of some of the differences in JBuilder 7 (at least) and JBuilder 4 in handling packages within the project view.  I'm working on a way to remedy this.