news <news@sea.gmane.org> wrote on 08/06/2005 01:57:32 AM:
> Here's an example of the properties that would be set in a sample
working
> copy (with modifications):
>
> svn.repos.url -> https://server/repos/branches/1.2.x
> svn.repos.path -> /repos/branches/1.2.x
> svn.revision.max -> 676
> svn.revision.max-with-flags -> 676M
> svn.revision.range -> 676M
> svn.modified -> true
>
> if it was a mixed and modified working copy the results would be like
this:
>
> svn.repos.url -> https://server/repos/branches/1.2.x
> svn.repos.path -> /repos/branches/1.2.x
> svn.revision.max -> 676
> svn.revision.max-with-flags -> 676MX
> svn.revision.range -> 673:676M
> svn.modified -> true
> svn.mixed -> true
>
> I then use the and copy filters to include these properties in my build,
> and name the output jars/installers with the numbers.
>
> It's made including version/branch info in the build simple ... and
allows
> you to see at a glance if you made a build from modified sources ...
which
> is important for quality control ... and so you know exactly what you
build
> was made up of.
>
> I've only really implemented this a few weeks ago ... but if people
think
> this type of thing is useful, I'm happy to take feedback, polish it up
and
> publish it for use somewhere..... or even to include in svnAnt (not
that
> I've even looked at that code).
This sounds like it could be a good feature. Would you consider trying to
add it into svnAnt and write it against svnClientAdapter instead of
directly against JavaSVN? svnClientAdapter now has support for JavaSVN
included, although I do not think this has been brought into svnAnt yet.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Fri Aug 12 00:34:32 2005