JUNG Build Process

This file clarifies the method for running a build & releasing the current software version, using Eclipse.
  1. Select the 1.4.2 JRE, and make sure that this JRE is used for the build process; also make sure that the compiler compliance level is set to 1.4.
  2. Run all unit tests and confirm that they all pass.
  3. Delete, if they are present, the /doc, /build2, /release, and /coverage directories.
  4. Go to build.xml (in project directory).
  5. In build.xml: make sure that links to other packages' documentation are up to date.
  6. Edit build.xml, go to the definition of the "version" property (near the top), and modify the value to reflect the current version.
  7. Check any changes into the CVS repository.
  8. Tag the release with the new version number: Team->Tag As Version.
  9. Make sure that there are no old JUNG-related jars in the "jardir" directory (see below). Otherwise Javadoc will (for some obscure reason) try to get the package information from them (rather than from the source files) and fail.
  10. Right-click on build.xml, select "Run->Ant Build..." .
  11. Make sure that the following configuration elements are set up (this should only need to be done once for a given installation of Eclipse):
  12. Select "main (default target)" task, run; this builds the docs and the jcoverage
  13. Do this again: this time, select "jar-src" and "release", then run.
  14. Go to the workspace/jung directory.
  15. Create an archive of the doc directory, and name it jung-X-doc.zip (where X is the current version number, as above). Copy this file to the release directory. The release directory should now contain the following files:
  16. Go to http://sourceforge.net/projects/jung/
  17. Go to Admin
  18. File Releases->Add Release
  19. Release name: jung-X
  20. Paste in release notes (excerpt from ReleaseNotes.html)
  21. click "submit" for this section (step 1)
  22. Follow directions for adding files listed under step 2:
  23. Click "add files and/or Refresh View"
  24. Step 3: fill out form appropriately (specify Platform-Independent, etc.)
  25. Select "send notice" when complete.
  26. ssh to shell.sourceforge.net, go to jung's htdocs directory (/home/groups/j/ju/jung/htdocs)
  27. Replace jars in applet directory as necessary
  28. Test links to make sure that everything on site works and links to correct version
  29. Copy edited website files into CVS repository, if necessary.