[Anthill] Customizing Tag Name

[Ben Rady]

To everyone who responded...thanks for taking the time to help. More 
questions below!

At 04:14 AM 2/16/2005, you wrote:
>On Tuesday 15 Feb 2005 23:40, Ben Rady wrote:
> > I have my version number all sorted out. The problem is that anthill
> > currently appends a 'v' onto the front of the version number to create the
> > tag name. I don't want the 'v' (we have an in-house policy on CVS tag
> > names).
>
>The CVS repository adapter will prepend a 'v' if the first character of the
>version string isn't a letter. I haven't used CVS for a while, but I think
>this may be a CVS requirement, so it can tell tag names from revision
>numbers. None of the other repository adapters do this, and I know for sure
>that my Subversion tree is full of purely numeric tags.
>
>source/main/java/com/urbancode/anthill/adapter/CVSRepositoryAdapter.java, 
>line
>525.

Ah, ok. So if I can solve my other problem, the prepended 'v' will go away. 
Excellent.


> > Secondly, the version file has additional constraints when building
> > off of a branch. Namely, the branch name must be included in the version
> > string.
>
>Sorry, I don't follow. Is this your policy, or something Anthill does?

This is something that Anthill does. From the FAQ:

Q: What format does the Anthill version file use when building on a branch?
A: If you are on a branch, then the <prefix> must contain the name of your 
branch as specified in the RepositoryAdapter properties page. This is 
mostly because we could not figure out how to assign version numbers to 
multiple branches while making sure that each version number was unique 
across all branches Including the branch name in the version number solves 
this problem. We're definitely open to other ideas here.

At my company, we solve this problem by numbering all of our branches, and 
then using that branch number in the tag name. So you'll have something like:

BRANCH_V31_5

contains

TAG_310501
TAG_310502
TAG_310503
...

where each increment on the tag is a new release candidate. Other parts of 
our build and release system depend on the tags being in this exact format. 
What I'd like to do is have Anthill automatically create those tags on each 
successful build. The problem, of course, is that Anthill complains unless 
you have the branch name in the version string. Like I said...I think I 
could do this by making my own Versioning Adapter, but is there an easier way?

Thanks again,
Ben

/*************************************
Ben Rady
Project Leader
Interactive Network Technologies
713-975-7434
*************************************/