[Anthill] parsing the env.version property

[Erik Husby]

What about a different approach.

Maintain the document that will contain the version number in a 
"template" format. The version would be in the text like so

@VERSION@

Then you can use the COPY with filtering task

<copy file="templatefile" tofile="realfile">
    <filterset>
       <filter token="VERSION" value="${build.number}"/>
    </filterset>
</copy>

GLeavitt at unicacorp.com wrote:

>
> I need to do a replace on various fields in the source when the build 
> no changes.   The env.version value passed from anthill into
> my build script looks like:
>
>         [echoproperties] version=5.0.4.009Alpha
>
> so i need to set two properties in my build script oldbuild.no, and 
> newbuild.no so that i can do the following;(I know it's not elagant 
> but I can't get the development team to tokenize these values yet.):
>
>         <replace dir="${basedir}/Shannon/ImpactC"
>                         summary="true"
>                         includes="UACFlowChart.rc"
>                         token="5.1.0.${oldbuild.no}\0" 
> value="5.1.0.${newbuild.no}\0">
>                 </replace>
>
> Since Anthill already keeps track and updates the buildno field in the 
> version file is there a way i can call the same class(es) from within 
> the  build script to parse out the numeric value in the version env 
> var and increment it?
>
> Thanks - Glen
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Anthill mailing list
>Anthill at lists.urbancode.com
>http://lists.urbancode.com/mailman/listinfo/anthill
>  
>

-- 
Erik Husby
Team Lead for Software Quality Automation
Genome Center at MIT
Rm. 2192
320 Charles St
Cambridge, MA 02141-2023
mobile: 781.354.6669
office: 617.258.9227
mhusby at broad.mit.edu

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.urbancode.com/pipermail/anthill/attachments/20040310/aad5e78b/attachment-0004.htm