#112 use of presetdef confuses error message parsing

[Shankar Unni]

I created a presetdef called "csi.javac" as follows:

<presetdef name="csi.javac">
<javac classpathref="build.classpath"
debug="${debug}"
deprecation="${deprecation}"
verbose="${verbose}"
optimize="${optimize}"/>
</presetdef>

Now, the messages come out as

[csi.javac]
C:/workarea/main/src/java/com/cotagesoft/xyz/Foo.java:
cannot resolve symbol: etc..

(I.e. instead of [javac], the prefix is [csi.javac]).

The problem is, the Compiler pane shows no errors, and
these errors which are normally colored in red in the
ANT output pane, are a plain black.

Just as if somebody (Antrunner, or JBuilder, or
someone) does not recognize the presetdef name, and is
looking for a hardcoded "[javac]".

What gives?

[Shankar Unni]

Logged In: YES
user_id=167432

Further investigation shows that it is the "." in the task
name that confuses AntRunner. If I call the task "csijavac",
it seems quite happy.

Now I can't find anywhere in the source where AntRunner
would care about such a ".". But I got lost following the
data flow of a message within AntRunner: who parses the
line, and decides whether it is an error?

[Shankar Unni]

Logged In: YES
user_id=167432

Note that this bug refers to Antrunner 2.1. I'm forced to
use this, because Antrunner 2.2 choked all over my Ant 1.6
build file with imports, etc.

[Dirk Schnelle-Walka]

Logged In: YES
user_id=192116

JBuilder is not involved in this.

AntRunner is not looking for a hardcoded javac, since aother
compilers like jikes should work, too.

Maybe it is the '.' in the task name. I'll have a look at it.

/dirk