More on Kawa snapshots (and build and CVS issues)

[Jim White <jim at pagesmiths dot com>]

Hello again.

I've tweaked the Kawa CVS Snapshot script.  I've added the upload of the 
Kawa executable jar, normalized the file names so that they group by 
date code, and added a readme file.

http://www.pagesmiths.com/kawa/
http://www.pagesmiths.com/kawa/0README.html
http://www.pagesmiths.com/kawa/build.xml

For those wondering why use an Ant script to do something that is less 
verbose in a shell script, the reason is that the next step up would be 
to use an automated build and report system like CruiseControl (which 
I've used) or AntHill (which I haven't).  They are both dandy Java/Ant 
automation tools.

http://cruisecontrol.sourceforge.net/
http://www.urbancode.com/projects/anthill/default.jsp

Of course with only one committer, automating the build beyond a 
manually invoked script isn't really much help, although those tools do 
generate nicely formatted reports.

And speaking of Ant and those having firewall/CVS issues, there is 
CVSGrab which is a (limited) CVS client that uses http to the CVSWeb 
server.  I haven't tried it with Kawa's CVSWeb to see if it works or not.

http://cvsgrab.sourceforge.net/

Jim

Jim White wrote:
> Hi Gang.
>
> I've put together an Ant script to automate posting Kawa snapshots from 
> CVS as source-only and binary build gzipped tars.
>
> I've not made sure that the binary version gets built with all the 
> optional jars.  I'll look into that later, or maybe Per will use the 
> script to run builds for Kawa's site.  Another refinement would be to 
> also upload just the Kawa jar as I'm sure some folks would prefer to 
> just download that.
>
> I've run it to include the most recent checkin by Per fixing Are's 
> defmacro issue.
>
> Latest snapshot (date code in file name, "-src" is source-only) is here:
>
> http://www.pagesmiths.com/kawa/
>
> Jim