ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jose Alberto Fernandez <JFernan...@viquity.com>
Subject RE: [PATCH] New <case> task
Date Wed, 11 Oct 2000 19:01:50 GMT
> From: Nico Seessle [mailto:Nico.Seessle@epost.de]
> 
> 
> > To me scripting is using a cannon ball to kill a fly. Why 
> do I need to
> have
> > BSF installed and learn javascript, or netrexx or some 
> other language AND
> > download the interpreter for such language just to be able to make
> decision
> > based on a value.
> 
> If *you* will not need it someone else will for sure - there 
> will be always
> one functionality which is not / can not be handled by a 
> system like ant,
> for example if you would like to increment build-numbers 
> and/or other things
> which go in the direction of calculation/comparison.
> 

Nico, please do not misunderstand me. I am all for having the scripting
tasks. The only thing I was commenting about was on having to use scripting
just to be able to find the value of a property. That is where I disagree
scriptig must be the required tool.

I am also not sure, whether the current <script> gives the proper highlevel
access, or whether it is too low-level. I confess, I have not used <script>
at all, but what I saw on e-mails, it seem to require knowledge about ANTs
architecture, knowledge that regular users should not need to have, as
opposed to developers.

Could you show us how to write a generic script that does what the <case>
task is doing? The input is a property and a list of value property pairs.

Another thing, is there a way to define new tasks defined by scripts?

Jose Alberto


Mime
View raw message