Re: publish help

I believe what you laid out is a perfectly fine way of going about it. 
At this point, I believe the "publish" script, isn't so much deprecated 
as it is just a place to run a second script. The properties provided to 
the publish script should be just about the same as are provided to the 
build script (there's a silly property in the build script that we are 
leaving for backwards compatibility but not putting in publish) and the 
functionality should be pretty much the same too. It's just run a little 
later in the process.

Internally, we still use seperate publish scripts on several of our key 
projects, including Anthill and AnthillPro. On others we roll that in to 
the main build script. Either approach is fine.

-- Eric

Jim Hague wrote:

>On Thursday 11 May 2006 00:25, Scott Gardner wrote:
>  
>
>>Is there any examples of publish scripts out there? The examples do not set
>>this property and short of looking in the source, I cannot find any
>>information on it.
>>    
>>
>
>I believe (and I'm sure Eric will be along soon with the straight dope) that 
>publish scripts are deprecated. The 'correct' thing to do these days is to 
>publish from within your build.xml script. The publish directory is passed in 
>by Anthill on the command line.
>
>From one of my build scripts I find:
>
>  <property name="deployDir" location="deploy"/>
>  <property name="publish" location="${deployDir}"/>
>
>This sets property 'publish' to the name of the passed-in publish directory, 
>or to 'deploy' if none were passed. Later on I create a tar file with my 
>build results:
>
>    <!-- Create the publication directory -->
>    <mkdir dir="${publish}"/>
>
>    <!-- Create the gzipped tar in the publish directory -->
>    <tar destfile="${publish}/${server-targz}" compression="gzip">
>	...
>
>This Works For Me.
>  
>