ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Donald <>
Subject Re: [PATCH] Script enhancement to standardize the "project" object exposed
Date Sun, 30 Sep 2001 12:22:11 GMT
On Sun, 30 Sep 2001 20:35, Sam Ruby wrote:
> > Hmmm - I thought you could access java objects directly in BSF. Something
> > like prefixing it with "java." or similar.
> Netscape's implementation of JavaScript allows access to Java objects by
> prefixing with "package.".

thats what I was thinking about ;)

> > Tasks are different. The majority of tasks used by the majority of users
> > are controlled by ant-dev. Thus the users of ant rarely have to be aware
> > of changes in underlying system. The contract is at the XML
> > representation level rather than at the code level.
> Be careful not to confuse cause and effect.  Project specific tasks are too
> dang hard to write (IMHO), so people don't.  This is something that should
> be corrected (IMHO) in future versions of Ant, not propagated.

Agreed. Part of it is that the current Ant evolved rather than was designed. 
With a clear separation between between API (like servlet API), framework 
(think turbine for tasks) and container it should be a lot easier to write by 
assemblying bits together.

However it is still a java + component based solution that suffers from the 
same issues as servlets. Integrating a <script/> task with a decent framework 
should create a RAD task environment (think JSP for tasks) or perhaps we 
could go with XSLT to create a task out of an assembly of tasks or similar. 
Not sure. However thats still something a way off unless someone steps up to 
base and implements it ;)



 We shall not cease from exploration, and the 
  end of all our exploring will be to arrive 
 where we started and know the place for the 
        first time -- T.S. Eliot

View raw message