Ah - I see. Nice work :-)

We are using SVN exclusively here so as you say the SvnRevisionLabeller fits
our needs


2009/3/19 Daniel Nauck <[email protected]>

>
> Hello,
>
> it has no dependency on subversion. It can be used with every SCM that
> support the "Last Change Number", like the lastChangeLabeller
> or by setting all 4 version party by hand.
> And it is dedicated to create a valid System.Version label without
> setting prefix, suffix or any other properties.
>
> If you want more configuration possibilities and you're only using svn
> then SvnRevisionLabeller is the proper labeller for you.
>
> Hope that helps.
>
> Daniel
>
> Dave Carson schrieb:
> > How does it differ from SVNRevisionLabeller -
> http://code.google.com/p/svnrevisionlabeller/
> >
> > On Mar 19, 12:44 pm, Daniel Nauck <[email protected]> wrote:
> >
> >> Hello,
> >>
> >> i've created a new labeller that always generated a valid assembly
> version.
> >> It uses the "Last Change Number" from supported SCM's like subversion to
> >> determine the revision and
> >> it automaticly increments the build number.
> >>
> >> Internally it uses the System.Version class to ensure a correct version
> >> label.
> >>
> >> The patch is available here:
> http://jira.public.thoughtworks.org/browse/CCNET-1424
> >>
> >> Example:
> >>
> >> <labeller type="assemblyVersionLabeller">
> >>     <major>$(majorVersion)</major>
> >>     <minor>$(minorVersion)</minor>
> >>     <incrementOnFailure>false</incrementOnFailure>
> >> </labeller>
> >>
> >> Its also possible to set every part of a version by hand:
> >>
> >> <labeller type="assemblyVersionLabeller">
> >>     <major>$(majorVersion)</major>
> >>     <minor>$(minorVersion)</minor>
> >>     <build>$(buildVersion)</build>
> >>     <revision>$(revisionVersion)</revision>
> >> </labeller>
> >>
> >> Any feedback is appreciated.
> >>
> >> Daniel
> >>
>
> >
>

Reply via email to