| Directory | Changes | Lines of Code | Lines per Change |
|---|---|---|---|
| Totals | 122 (100.0%) | 6966 (100.0%) | 57.0 |
| src/main/org/apache/tools/ant/taskdefs/ | 28 (23.0%) | 3422 (49.1%) | 122.2 |
| src/main/org/apache/tools/ant/ | 14 (11.5%) | 1648 (23.7%) | 117.7 |
| proposal/anteater/source/main/org/apache/ant/ | 22 (18.0%) | 768 (11.0%) | 34.9 |
| proposal/anteater/bootstrap/ | 12 (9.8%) | 413 (5.9%) | 34.4 |
| proposal/anteater/source/main/org/apache/ant/cli/ | 7 (5.7%) | 384 (5.5%) | 54.8 |
| / | 9 (7.4%) | 222 (3.2%) | 24.6 |
| src/etc/ | 4 (3.3%) | 37 (0.5%) | 9.2 |
| src/bin/ | 4 (3.3%) | 28 (0.4%) | 7.0 |
| proposal/anteater/source/coretasks/echo/org/apache/ant/echo/ | 2 (1.6%) | 22 (0.3%) | 11.0 |
| proposal/anteater/source/ | 3 (2.5%) | 20 (0.3%) | 6.6 |
| proposal/anteater/source/coretasks/echo/ | 2 (1.6%) | 2 (0.0%) | 1.0 |
| whiteboard/utah/ | 4 (3.3%) | 0 (0.0%) | 0.0 |
| src/main/com/ice/tar/ | 6 (4.9%) | 0 (0.0%) | 0.0 |
| spec/ | 1 (0.8%) | 0 (0.0%) | 0.0 |
| proposal/anteater/source/coretasks/buildtarget/org/apache/ant/buildtarget/ | 1 (0.8%) | 0 (0.0%) | 0.0 |
| proposal/anteater/source/coretasks/buildtarget/ | 1 (0.8%) | 0 (0.0%) | 0.0 |
| proposal/anteater/ | 1 (0.8%) | 0 (0.0%) | 0.0 |
| docs/ | 1 (0.8%) | 0 (0.0%) | 0.0 |
Oops.. Forgot little update in Bootstrap to build out the buildtarget
task. :)
1 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.
21 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.
160 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
core.
540 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
this information.
273 lines of code changed in:
Changed task loading to use a centralized TaskManager that keeps tabs on
all classes.
61 lines of code changed in:
Changed bootstrap to use Conor's idea of having a BootBoot that grabs
tools.jar and puts it on the classpath when needed. I did change things
around so that it's now Bootstrap --> Bootstrap2
68 lines of code changed in:
Updated instructions now that the .jars are history.
3 lines of code changed in:
Remove .jar dependancies.. Now AntEater builds off xml-crimson as its parser
and handles things on its own. Only takes an extra 10 seconds on the bootstrap
and will tend to keep the crimson guys honest. :)
16 lines of code changed in:
Initial checkin
466 lines of code changed in:
Removed ancient utah whiteboard area. The material in /spec is much
more up to date (even if it does need to be updated... :)
0 lines of code changed in:
Put in proper unix /bin/sh declaration
2 lines of code changed in:
Hack to make clear that Modern compiler isn't yet implemented. Of course,
a real solution is needed, but I didn't want to see any more unneeded
confusion over this.
3 lines of code changed in:
Initial checkin of core spec. There's still pieces that need to be filled
in that I know about. The big on is the task reflection stuff.
0 lines of code changed in:
Initial checkin of Utah Design Guide.
0 lines of code changed in:
initial checkin
5298 lines of code changed in:
Really just a test of notifications
0 lines of code changed in:
Flesh out readme and testing putback notifications
53 lines of code changed in:
Initial revision
1 lines of code changed in:
