Hi everybody,
Hope you don't mind a late join to the discussion.
There is some precedent for this kind of thing in Ant -- extension-points.
In fact, extension-points plus appendable paths / filesets is a potent
combination. You know:
* base script declares a few standard, empty data structures
Point taken. But that sounds like an argument against the augment
feature itself. If you are going to make exceptions, then things aren't
really immutable at all. When properties were made immutable there had
to be ugly little hacks like the prefix on tstamp to get around the fact
there were ti
On 2010-03-13, Clark Archer wrote:
> On Tue, Mar 9, 2010 at 11:19 PM, Stefan Bodewig wrote:
>> Hi Clark
>> On 2010-03-09, Clark Archer wrote:
>>> coded up a HistoryRecorder which builds a simple text file
>>> containing a history of up to the last 100 executions for each test
>>> class/suite
On 2010-03-15, Petar Tahchiev wrote:
> If you want to test it you can checkout the source of the book from here:
> https://junitbook.svn.sourceforge.net/svnroot/junitbook/trunk/junitbook2/
> and go to chapter 6 and execute ant test.
Did that with Java6 on Windows, Ant 1.8.1, empty CLASSPATH, e
I agree with your argumentation about final in java. But I'm not sure you
can translate that to ant.
First, I have access to the overwrite method in 1 key in my java IDE. In
ant, it might be a little bit more complex.
Secondly, I continue to see ant as a declarative language (although inside
th
