[Jprojecttimer-commits] CVS: jprojecttimer/docs/devel-docs generating_file_releases.txt,NONE,1.1

[Christian G. [M. Mitch] <mas...@us...>]

Update of /cvsroot/jprojecttimer/jprojecttimer/docs/devel-docs
In directory sc8-pr-cvs1:/tmp/cvs-serv2736

Added Files:
	generating_file_releases.txt 
Log Message:
Initial source version.


--- NEW FILE: generating_file_releases.txt ---
JProjectTimer documentation
http://sourceforge.net/projects/jprojecttimer/


        How to generate "official" file releases
        (.zip, .tar.gz and -src.tar.gz)


Generating the file releases should be done on a Un*x systen because
of file names (uppercase might get lost using Windows zip utilities).


Step 1: Get the source code.

It's easiest to do a CVS checkout (see the CVS section on the
Sourceforge homepage on how to do this).  You propably already have a
current CVS checkout on your machine to work with.  This will do fine.

If you don't hava a Un*x system, but are a registered member of a
Sourceforge project, you can request access to the Sourceforge compile
farm.


Step 2: Tag the files.

Use the CVS tag command to tag all files with a version tag.  Be sure
not to use a tag that is already in use.  The cvs tag must be in the
form "vX_Y_Z" where X.Y.Z is the version number (e.g. for release
0.2.4 the tag would be "v0_2_4" -- without the quotes).

You will tag the file versions that are currently visible in your
local CVS tree -- if there are already some newer versions that should
not be included in the release, take a look at the options to the tag
command and tag only the desired file versions.


Step 3: Run buildPackages.sh

Run the script "buildPackages.sh" (it's in the main directory of the
CVS tree).  Pass the version number to build as an argument.  For
example, if you'd want to build the release 0.2.4 you'd have to type
this:

  ./buildPackages.sh 0.2.4

The script will then check out an extra snapshot of version 0.2.4 and
build the following files:

  - JProjectTimer-0.2.4.tar.gz
  - JProjectTimer-0.2.4.zip
  - JProjectTimer-0.2.4-src.tar.gz

Note that you can build any version that exists as a proper version
tag in the CVS.  Re-creating packages for older versions os no
problem.

Note that you can't build releases prior to 0.0.6 because the location
of the .jar libraries was different then.