Ant has a checksum task which can generate them for you - I've used it for
md5, but should work for sha as well.
Heres an example target to create md5 checksum....
<target name="internal-md5">
<checksum file="${md5path}/${md5filename}" property="md5"/>
<echo message="${md5} *${md5filename}"
file="${md5path}/${md5filename}.md5" />
</target>
Then, for example, to create a checksum for a particular file...
<antcall target="internal-md5">
<param name="md5path" value="${dist.home}" />
<param name="md5filename"
value="commons-validator-${component.version}.zip" />
</antcall>
Obviously this has the advantage of one less step to remember if its
automated, but also removes the platform dependency on the shell script.
Niall
> ----- Original Message -----
> From: "Apache Wiki" <[EMAIL PROTECTED]>
> Sent: Sunday, January 15, 2006 10:36 AM
> Subject: [Jakarta-velocity Wiki] Update of "ReleaseProcess" by
> HenningSchmiedehausen
> > === Building the release ===
> >
> > * change the version property in `build.properties` to reflect the
version
> > to be released.
> > * check this change in using `svn commit`
> > * build the release packages using `ant package`
> > * enter the `bin` directory
> > * run the following shell script to build MD5 and SHA1 checksums:
> > {{{
> > #! /bin/bash
> > for i in *.tar.gz *.zip *jar; do
> > md5sum < $i | cut -d' ' -f1 > $i.md5
> > sha1sum < $i | cut -d' ' -f1 > $i.sha1
> > done
> > }}}
> >
> > * Generate GPG signatures:
> > {{{
> > #! /bin/bash
> > for i in *.tar.gz *.zip *jar; do
> > gpg --default-key <your key id here> --armor --output
$i.asc --detach-sig
> > $i
> > done
> > }}}
> >
> > You should now have sixteen files in that directory: A .jar, a .jar with
> > dependencies, a .tar.gz and a .zip file. For each you must have a .md5,
a
> > .sha1 and a .asc
> > file. If you file count is not correct, please '''DO NOT CONTINUE'''.
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
