db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel John Debrunner <...@debrunners.com>
Subject [PATCH] Set Derby's build number to be the subversion revision number
Date Fri, 24 Sep 2004 18:32:20 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This patch sets Derby's buildnumber to be the ouput of svnversion when
the jar files are built. Tha main change is to allow the build number to
 be a string rather than just a number (previously Cloudscape used
Perforce's change number which was always a number).

Example partial output from sysinfo is

- --------- Derby Information --------
[/home/djd/derby/trunk/jars/insane/derby.jar] 10.0.2.0 - (47170M)
[/home/djd/derby/trunk/jars/insane/derbytools.jar] 10.0.2.0 - (47170M)
[/home/djd/derby/trunk/jars/insane/derbynet.jar] 10.0.2.0 - (47170M)


The M indicates that the svn client is being modified in some way. Any
pre-built jar or release on the Derby site would just have a simple
number like '47170'. Ie. from a clean un-modified code line.

This then allows easy tracking of the matching code for any Derby jar.

+1 vote from myself.

Dan.








-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFBVGg0Iv0S4qsbfuQRAuYNAKDl2nKsf9Vk0pocmJazQS9czGNLwwCfQfy3
3dMLosd9FN9QMEWDJ5Agubw=
=o1HQ
-----END PGP SIGNATURE-----

Mime
View raw message