[Anthill] Are there additional ant properties available to build scripts....

[Michael Forsberg]

So if I understand you correctly,
You just use these conventions for your builds.

Currently I am doing using other conventions, but was
hoping that values set in an anthill's project's properties
are passed into the build script.  Much like the ant task....
    <ant antfile="build.xml" target="ATarget" inheritAll="true" />
Where the antfile is my build, and all the current build file
properties are passed my build file.

I'd just like the properties in the anthill project affect
the build scripts a little more.  Thus if I change a publish dir in
anthill, I don't need to change my "copying the binaries" target.
Ant would know the final destination from an inherited property.

Michael Forsberg

Mark Derricutt wrote:
> Michael Forsberg wrote:
> 
>> Are there extra properties available to the ant script during the build?
>> Specifically, those like the anthill.publish.dir property.
> 
> 
> I tend to use the following:
> 
>     <property name="deployDir" location="dist" />
>     <property name="dist" location="${deployDir}" />
>     <property name="version" value="dev"/>
>     <property name="dependency.artifact.dir" value="dependency"/>
> 
> deployDir is the publish directory and I default it to a local "dist" 
> dir for when building on a dev box.
> 
> version is well duh. the version :P  I default that to "dev" for a local 
> dev/non-anthill build.
> 
> dependency.artifact.dir is the share directory for dependency targets.
> 
> There may be others but these are the ones I tend to use.
> 
> _______________________________________________
> Anthill mailing list
> Anthill at lists.urbancode.com
> http://lists.urbancode.com/mailman/listinfo/anthill
>