On Wed, 13 Feb 2002, Conor MacNeill wrote: > I have prototyped a new task in mutant which I'd like to get feedback > from anyone interested. It is called scriptdef and allows you to define > a task as a script. Here is an example > > <project name="scripttest" default="test">
> <libpath libraryid="antopt.script" > file="/home/conor/dev/antdev/jakarta-ant/lib/optional/bsf.jar"/> > <libpath libraryid="antopt.script" > file="/home/conor/dev/antdev/jakarta-ant/lib/optional/js.jar"/> > <import libraryid="antopt.script" name="scriptdef"/> > <scriptdef name="scripttest" language="javascript"> <![CDATA[ .... > ]]> </scriptdef> > > <target name = "test"> > <scripttest test="goodbye"/> > </target> > </project> > > The first two lines just provide additional classpath info for the > script Ant library. Normally these would be in a config file rather than > the build file but I wanted to test them out. > > This is built on BSF and works with javascript (Rhino) although I have > not tried any other scripting language. > > Thoughts? Is anything to prevent <scriptdef> from beeing implemented as a regular ant1.x task, similar with Taskdef ? If it is possible, I would love to see it as part of ant1.x, or as a separate 'contrib' scripttask.jar. Costin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
