Very useful Alexander, Thanks :)
2005/10/27, Alexander Blum <[EMAIL PROTECTED]>:
> 2005/10/27, erixtekila <[EMAIL PROTECTED]>:
> > If you still get your Jvav example somewhere, I'll be happy to receive
> > it.
> > /me interested :)
>
> Well, it is inside a large build.xml file with dependency checks and
> configuration via a build.properties file, but I will post a small,
> modified (, untested) extract:
>
> <target name="compile">
> <buidlnumebr />
> <tstamp>
> <format property="build.time" pattern="yyyyMMddkkmmss" />
> </tstamp>
> <echo message="Build number ${build.number}" />
> <echo file="src/com/company/package/BuildInformation.as"
> append="false">class com.company.package.BuildInformatiion
> {
> public static var m_strVersionNumber : String = "${version}";
> public static var m_nBuildNumber : Number = "${build.number}";
> public static var m_nBuildTime : Number = "${build.time}";
> }
> </echo>
> <exec executable="${mtasc}" failonerror="true">
> <arg ....... />
> <arg ....... />
> <arg ....... />
> </exec>
> </target>
>
> assuming version and mtasc are set
>
> Since variables are expanded inside echo tasks, you can use them to
> configure package names and the location of your BuildInformation.as
> via a build.properties file. This way you can create one build.xml
> file for all your projects and all you have to adjust and change
> between projects are a few parameters in a flat build.properties file.
>
> --
> Alex
>
> _______________________________________________
> osflash mailing list
> [email protected]
> http://osflash.org/mailman/listinfo/osflash_osflash.org
>
--
::| Carlos Rovira
::| http://www.carlosrovira.com
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org
