Zap the bootstrap stuff
0 lines of code changed in:
Make AntEater compile.
2 lines of code changed in:
A small task example that illustrates something... A long time ago I
argued against "if" logic as part of the defined part of Ant stating
that all logic really should go into tasks. Now that the object model
is clean enough, it becomes silly obvious how to do this without requiring
the addition of any if/unless attributes in the target definitions themselves.
The build target task takes a target name and, optionally a if property. If
the property is used and is "true", then the target is executed by calling
the appropriate functionality on the Project object.
8 lines of code changed in:
Removed last legacy of Ant.java and have settled a bit on how front
ends use core... In order for a front end to run a build, it first
creates a ProjectBuilder, loads a Project from it, then can run a
build on that Project. What still needs a bit of looking after is
creating a project from scratch (such as a GUI might do) and then
executing it. Later.
23 lines of code changed in:
Removal.. Most of the functionality has been moved to other places now
that its becoming a bit more clear how FrontEnds should interace with the
178 lines of code changed in:
Several things all at once...
* Bootstrap now passes args all the way through
* FrontEnding implemented which allows Ant to talk back out
to whatever front end might be driving it. Events propogated
are project start/end, target start/end, task start/end.
This should allow any front end (like a GUI) to move a
progress indicator through a display of the object tree.
Also included is a generic writeMessage(String, int) method.
* cli/Main now plays ClassLoader games so that it can auto
matically place needed resources (like tools.jar) into
the classpath space of the executing Ant. Note -- this
is the first of a few steps to make complicated shell
launch scripts unnecessary. All that should be done
is a single executable per platform that essentially
calls "java -jar anteater.jar [args]". Main is also
primed for a future CJAN so that it can download whatever
jars are needed from CJAN and place them into the classpath
space of the executing Ant. Of course, it's not implemented
yet since CJAN isn't around yet -- but its ready. :)
* AntException now has fields for embedding the location
of an Error. Next up will be implementing the code
around where Tasks are run so that exceptions will contain
111 lines of code changed in:
64 lines of code changed in: