Fixstyle Build Procedure

This is the procedure to be followed for building the Fixstyle BlueJ extension from source.

Setup

Check out a fresh version of the repository from the Twain subversion repository. You must be able to execute the javac, jar and ant utilities from the command line. Go to the folder for the branch you want to rebuild.

Windows Build

Run the batch script: build.bat in the root of the repository. This will recompile all of the source files and rebuild a new Fixstyle.jar from source, ready to install.

Unix/Linux/Mac Build

From the command line, run bash build.sh. This will recompile all of the source files and rebuild a new Fixstyle.jar from source, ready to install.

Manual rebuild

From the command line run ant cleanBuild. This will recompile all of the source files and rebuild a new Fixstyle.jar from source, ready to install. You will need to copy the output from ant directly into build_output.txt.

Status

The file build_output.txt contains the output from the java compile process. Analyze the output for compile errors and warnings.

Currently there is no build script for Unix/Linux.

Daily Build Reports

After the build process has finished, the daily build report log can be updated. Update to the latest version of the repository to check for changes since the repository checkout. If there are no updates to download, commit the new jar file and build_output.txt file to the repository and note the revision number. If there have been updates to the repository, check out a new version of the repository and restart the build process.

Go to the Daily Build page and edit the page. Copy a row from the existing log table and insert it under the heading row of the table.

  • Update the "When Build" column to reflect the current date and time.
  • In the status column, write "Complete", "Warnings" or "Broken" based on the compile messages in build_output.txt and the legend on the Daily Build page.
  • In the "SVN Log" Column, change the numbers in the link: "changeset:## log ##" to be the revision numbers you recorded after committing the new build to the repository.
  • In the "Build Output" Column, change the numbers in the link: "source:build_output.txt@##" to be the revision numbers you recorded after committing the new build to the repository.
  • In the "Download" Column, change the numbers in the link: "...Fixstyle.jar?rev=##&..." to be the revision numbers you recorded after committing the new build to the repository.