At 12:21 3/2/01 -0800, Paul Hammant wrote: >What I am looking for is replacing the layer that links Ant commands to >the host OS provided command line with one that adapts to beanshell's >(or a new console tool's) command line. There are some other problems >too in that ANT should not hog the AWT thread if that's when command >invokation requests come though.
Well there is ant1.x but to get it working under Avalon is near impossible atm. Because Ant1.x makes use of statics and hardwires in a few assumptions it is difficult to do without side effects. You would also have to disable a heap of things in Avalon (like security manager) to get it working kosher. You will also need to pick up a version after yesterday when it was patched to work with better classpath arrangement. Alternatively you could help us work on Ant2.x which will almost certainly have a separate task-engine which is what you are asking for. It will hopefully be able to be gracefully embedded in any other app with 0 side effects (at least if I have a say in it ;-]). >.. for subsequent editing or execution, this would help to establish >ANT comand syntax as THE standard for both executable scripts and >invokable commands. If the same XMLized for could be "prompted" in a >suitable enhanced editor or command line a real GUI could pop up >temporarity to allow full blown selection of elements/attributes >including offering a FileChooser where appropriate. Well you could look at the myrmidon proposal for Ant2.0. As it uses avalon it should be basically familiar to you. It is the evolution of another version of ant I embedded in a cron tool (also based on ancient version of Avalon) so should do the trick. Currently myrmidon has a largely "complete" task-engine. With setting properties you can virtually swap any component and make it work anyway you want. The project building part however is based on Ant1.x and as it is not yet decided on what Ant2.0s format will be this will be considered completely alpha ;) There is also a few issues with respect to loading DataTypes from .tsk files that has yet to be discussed on ant-dev (ie What happens when tsk file A defines type Blah which .tsk file B wants to use). I suspect this will require a bit of manifest hackery in the future but who knows. Other than that all the names/packages are yet to be finalised and may change (a few people pointed out they dislike the name "tasklet" but no one on ant-dev has commented). Oh and there are no useful tasks written for it yet but it shouldn't take more than an hour or so to convert over the base tasks ;) I keep meaning to hack on it some more but every time I get some spare time the sun is shining outside ... and my area isn't usually known for good weather so ... ;) >Grand plans! > >What's thought of this? I say good, better, great - another vote for embeddable Ant2.0 ;) Cheers, Pete *-----------------------------------------------------* | "Faced with the choice between changing one's mind, | | and proving that there is no need to do so - almost | | everyone gets busy on the proof." | | - John Kenneth Galbraith | *-----------------------------------------------------*
