On Mon, 5 Nov 2001 21:25, Jose Alberto Fernandez wrote: > Independently of what it is decided, I would like that any arquitecture we > come up with will manage this "keyworkds" are its functionality in a > pluggable fashion. That will allow for extensions or customizations in the > future on this regard. I am not saying they are tasks, mayby they are > ModelBuilders :)
It has only been close to a year I have been advocating ProjectBuilders for just this purpose. > > Everything that is not specifically recognized will probably be > > collected into a model component that supports arbitrarily nested XML > > elements. This will of course be used for tasks/types but may also be > > used for other constructions which need to be processed in the execution > > phase. So, there should be sufficient extensibility in the model for > > other elements without making the parsing phase some sort of stripped > > down DOM builder or taking on the "everything is a task" view. > > One thing that I would like to be able to do is for ANT to have a more > reasonable implementation of <antcall>. Today every <antcall> reads and > parses the project file over and over. Which looks like a waist and makes > the file system the only way for GUIs to communicate with ANT. What we > really need here is to be able to reause the internal representation of the > Project at the point where properties have not been applied to attributes. > That would allow for its evaluation as parameters. Any ideas on how to do > this efficiently? easily done. However that has been -1'ed as a use case so ... ;) -- Cheers, Pete --------------------------------------------------- For every complex problem there is a solution that is simple, neat and wrong --------------------------------------------------- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
