From: Ed Taekema <etaekema@ea...> - 2004-04-23 03:32:55
Thanks for the feedback. I mentioned in the article that I was doing things backwards from the approach you presented ... although the goals are the same ... and actually could be used together ... hmmm that would be an interesting approach ... automate Ant builds from a jython script by calling Ant tasks ... some of which are actually written in Jython!
From: Jonathan Simon <jonathan_s_simon@...>
Sent: Apr 22, 2004 9:18 PM
To: Ed Taekema <etaekema@...>, jython-users@...
Subject: Re: [Jython-users] Use Jython to Write Ant Tasks
This looks cool. I just wanted to make one point. With the article I wrote for
Java.net, I was getting at the idea of driving ANT *from* Jython- not the other
way around. That said, I think what youre doing is still on the right track.
But I just wanted to make sure you understand what I was getting at.
I was thinking of a way to leave the ANT tasks in Java (or Jython as you
present) and getting rid of the build.XML file entirely. Then the file that you
run would itself be a Jython script. This way you could do loops, method calls,
conditionals, etc- all in a logical way.
Keep the fight alive!
--- Ed Taekema <etaekema@...> wrote:
> I've written a guide to writing Ant tasks using Jython: how to add scripted
> behaviour to ant builds. It details the steps to write a custom Ant task in
> jython, compile it and install it into ant so it can be used as any other
> task in an ant build. The article also takes a quick look at an alternate
> implementation using Groovy.
> Ed Taekema
> Toronto, Canada
> This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
> For a limited time only, get FREE Ground shipping on all orders of $35
> or more. Hurry up and shop folks, this offer expires April 30th!
> Jython-users mailing list
Home - 732.777.0377
Work - 201.671.1175
Cell - 732.718.8844
Music - http://www.mp3.com/jonathan_simon
From: Casey Dunn <caseyd1@st...> - 2004-04-27 04:08:36
This "backwards" approach is great for my purposes - in my situation the
build.xml is used
to express a number of dependancies for runtime as well as compile time.
It serves as a
manifest for the app.
the human readability of the build.xml isn't to be discounted when
dealing with a diverse team
As it is now I'm generating various shell scripts from ant to be
by extending w/some simple tasks in Jython I can include a number of
in the deployment issues and get rid of this verbose bit.