Hello:
Some of you may remember me as a sometime ant contributor.
Well, the project I am working on has need of another Ant expert.
If interested, please drop me a line at cstrong at arielpartners dot com
thanks, and sorry for the interruption.
--Craeg
Steve Loughran wrote:
Actually, I quite like the listener approach. We just need an extended
listener; there is no reason the -listener command can't handle both
types.
The nice thing about a listener is that it lets an IDE do fancy things
like list all properties.
if we are going to do
Dominique Devienne wrote:
So obviously I'm +1 on adding such a facility, but implementing it the
way you propose is indeed disruptive.
Alternate impls (disclaimer: I'm just thinking aloud here...) might be:
1) Add categories to log messages. You could then change the log
statements in
Dominique Devienne wrote:
Changing an interface is a no-no of course.
So far I think I like #1 best, i.e. adding a few overrides to the log
methods in ProjectComponent to support an additional category. I'm not
sure we'd need hierarchical categories a la Log4J or
java.util.logging. Makes it
of the issue-- I am discouraged by how many files would
have to be changed to implement this capability.
Does that make it too expensive ?
Comments, please!
--Craeg Strong
-
To unsubscribe, e-mail: [EMAIL PROTECTED
Although it will only interest a small number of developers, i would
happily contribute a ecmascript/javascript with Ant including JSdoc
(similar with javadoc) and JSLint (instead of checkstyle) integration,
unit test etc.
Manos
Yes, Please!
I am involved with a large project that is
This tutorial is incredibly valuable, IMO.
I would love to see this checked into CVS and given
a permanent home on the ant website, kind of like
ant in anger...
2c,
--Craeg
The first place was a very long time ago and there was a lot of history
for
why Ant is the way it is. You might be
