Justin,
Where should I go or what should I read to figure out how our build works?
I'm not sure how our top-level build is invoked. Ideally it could be
invoked with
ant -Dbuild.number={svn-rev-that-triggered-build} release (or whatever
target you are using)
This would cause flex-sdk-description.xml to have the correct build number
and build.number would get propagated down to all the tools like mxmlc,
etc so their version information would be correct as well.
The tools all have this in their build files:
<echo file="${module.classes}/flex2/tools/version.properties"
append="false">build=${build.number}</echo>
And then this is used for strings like this:
~/dev/asf_trunk/frameworks/javascript$ ../../bin/mxmlc
Loading configuration file
/Users/cframpto/dev/asf_trunk/frameworks/flex-config.xml
Apache Flex Compiler (mxmlc)
Version 4.8.0 build 272727 <------
Copyright 2012 The Apache Software Foundation.
Carol
On 5/21/12 5 :17AM, "Justin Mclean" <jus...@classsoftware.com> wrote:
>Hi,
>
>The windows CI server has just run out of disk space, while Flex SDK
>build was not the direct cause I'm sure it helped a little (take up about
>2GB).
>
>Anyway I've logged an issue with INFRA and also noted that we'll need
>more disk space in the near future for running the Mustella scripts/tests.
>
>Thanks,
>Justin
