You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ant.apache.org by Shorn Tolley <sh...@hotmail.com> on 2002/06/01 00:31:18 UTC
How do I get rid of the "Compile failed..." message from Ant when the javac task reports erros?
I'm pretty sure this happens with all Ant versions, but the version I'm
using at the moment is 1.4.1.
When I'm compiling a project and I have a syntax error, Ant reports line
numbers and all that guff about the error; excellent, fine, that's what I
want.
But, it also always outputs the following after outputting information about
the syntax errors:
BUILD FAILED
<location>\build.xml:<line number>: Compile failed, messages should have
been provided.
This message, which looks like Ant is reporting a syntax error within the
actual build file, is really annoying. It's annoying because some IDEs
(NetBeans and IDEA specifically, probably others too) will simply assume
this message is telling the user about an error in the XML file. When it's
not really, it's telling the user that some target within the file failed.
Is there any way to get rid of this message? I've tried providing -quiet on
the command line, I've looked in the Ant manual, Ant FAQ and JGuru Ant FAQ
and I can't find an answer.
Thanks,
Shorn.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Newbie: Building Ant 1.4.1 from within NetBeans - wierd problem with 'available' task for RegExp jar
Posted by Erik Hatcher <ja...@ehatchersolutions.com>.
I don't know what others are doing, but I only build Ant from the
command-line. There are too many moving pieces when tossing an IDE in the
middle. Sounds like you have that in your classpath through NetBeans
somehow - and whether you can disable that I don't know.
I bootstrap and then run the build, all through the scripts (bootstrap.bat
and build.bat, in my case).
Erik
----- Original Message -----
From: "Shorn Tolley" <sh...@hotmail.com>
To: <an...@jakarta.apache.org>
Sent: Saturday, June 01, 2002 8:13 PM
Subject: Newbie: Building Ant 1.4.1 from within NetBeans - wierd problem
with 'available' task for RegExp jar
> Hi folks,
>
> I am trying to build the Ant source code for 1.4.1.
> (as an aside, are there any FAQs or anything I should be reading as a
first
> time Ant builder?)
>
> I am able to build Ant 1.4.1 from the command line using a binary download
> of Ant 1.4.1.
>
> When I try to build Ant from within NetBeans (using the Ant project
> build.xml file), the compile fails because the script tries to build the
> org.apache.tools.ant.util.regexp.JakartaRegexpMatcher.java file.
>
> This does not happen from the command line because I haven't got the
> regexp.jar in my classpath or anywhere else for that matter. Which means
> the 'available' task in the 'check_for_optional_packages' target doesn't
set
> the 'jakarta.regexp.present' property, which means the
JakartaRegexpMatcher
> class gets excluded from the build.
>
> Unfortunately, when building from within NetBeans, the available task
seems
> to find the RE regexp class, which means it then sets the
> 'jakarta.regexp.present' property, which eventually causes the build to
> fail. I /think/ the RE class is being picked up from the NetBeans
> classpath. (regexp.jar /is/ in the 'netbeans.class.path').
>
> I have gotten the build to work from within NetBeans by commenting out the
> available task that sets the 'jakarta.regexp.present' property, but I was
> wondering if anyone else is building Ant from NetBeans and have seen this
> problem?
>
> Platform:
> Windows XP
> JDK 1.3.1 (although netbeans is running on 1.4)
> Ant 1.4.1 source code
> NetBeans 3.3.1
> Using Jikes as well (but it happens with ordinary javac too)
>
> Thanks,
> Shorn.
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: How do I debug what's in a path?
Posted by Peter Donald <pe...@apache.org>.
Hi,
This is what you want
<path id="test.classpath"/>
<property name="X" refid="test.classpath"/>
<echo message="test.classpath=${test.classpath}"/>
On Mon, 3 Jun 2002 00:12, Shorn Tolley wrote:
> Hi,
>
> I'm trying to track down a build problem I'm having when building Ant from
> within NetBeans (I actually have it working via two different workarounds
> now, but I want to solve the problem).
> The problem appears to be NetBeans, not Ant or the Ant build file.
>
> I have a minimal project that works on the command line and doesn't work in
> NetBeans that I'm going to use to show the NB community what's going wrong.
>
> What I was wondering is: is there any way I can debug a path element?
> I want to print out to the console eveything that's in a particular
> classpath.
> (This will make it easier to show explicitly whats going wrong)
>
> The path element I want to debug (just like in the Ant build file) is
> declared:
> <path id="test.classpath">
> </path>
>
> What I'd like to do is something like:
> <echopath pathref="test.classpath"/>
>
> And that would print out all the elements of the classpath.
> Does anyone know of anyway I can do something like this with Ant 1.4.1?
>
> Thanks,
> Shorn.
--
Cheers,
Peter Donald
--------------------------------------------------
"An intellectual is someone who has been educated
beyond their intelligence."
--------------------------------------------------
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: How do I debug what's in a path?
Posted by Erik Hatcher <ja...@ehatchersolutions.com>.
<property name="classpath.string" refid="test.classpath"/>
<echo>classpath = ${classpath.string}</echo>
----- Original Message -----
From: "Shorn Tolley" <sh...@hotmail.com>
To: "Ant Developers List" <an...@jakarta.apache.org>
Sent: Sunday, June 02, 2002 10:12 AM
Subject: How do I debug what's in a path?
> Hi,
>
> I'm trying to track down a build problem I'm having when building Ant from
> within NetBeans (I actually have it working via two different workarounds
> now, but I want to solve the problem).
> The problem appears to be NetBeans, not Ant or the Ant build file.
>
> I have a minimal project that works on the command line and doesn't work
in
> NetBeans that I'm going to use to show the NB community what's going
wrong.
>
> What I was wondering is: is there any way I can debug a path element?
> I want to print out to the console eveything that's in a particular
> classpath.
> (This will make it easier to show explicitly whats going wrong)
>
> The path element I want to debug (just like in the Ant build file) is
> declared:
> <path id="test.classpath">
> </path>
>
> What I'd like to do is something like:
> <echopath pathref="test.classpath"/>
>
> And that would print out all the elements of the classpath.
> Does anyone know of anyway I can do something like this with Ant 1.4.1?
>
> Thanks,
> Shorn.
>
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: How do I debug what's in a path?
Posted by Conor MacNeill <co...@cortexebusiness.com.au>.
Shorn Tolley wrote:
> Hi,
>
> What I'd like to do is something like:
> <echopath pathref="test.classpath"/>
>
<property name="fubar" refid="test.classpath/>
<echo message="test.classpath is ${fubar}"/>
I think that should do what you want (although I wasn't sure if you wanted
to know what was on the path, which this won't do).
Conor
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
How do I debug what's in a path?
Posted by Shorn Tolley <sh...@hotmail.com>.
Hi,
I'm trying to track down a build problem I'm having when building Ant from
within NetBeans (I actually have it working via two different workarounds
now, but I want to solve the problem).
The problem appears to be NetBeans, not Ant or the Ant build file.
I have a minimal project that works on the command line and doesn't work in
NetBeans that I'm going to use to show the NB community what's going wrong.
What I was wondering is: is there any way I can debug a path element?
I want to print out to the console eveything that's in a particular
classpath.
(This will make it easier to show explicitly whats going wrong)
The path element I want to debug (just like in the Ant build file) is
declared:
<path id="test.classpath">
</path>
What I'd like to do is something like:
<echopath pathref="test.classpath"/>
And that would print out all the elements of the classpath.
Does anyone know of anyway I can do something like this with Ant 1.4.1?
Thanks,
Shorn.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Newbie: Building Ant 1.4.1 from within NetBeans - wierd problem with 'available' task for RegExp jar
Posted by Steve Loughran <st...@iseran.com>.
----- Original Message -----
From: "Shorn Tolley" <sh...@hotmail.com>
To: <an...@jakarta.apache.org>
Sent: Saturday, June 01, 2002 5:13 PM
Subject: Newbie: Building Ant 1.4.1 from within NetBeans - wierd problem
with 'available' task for RegExp jar
>
> I have gotten the build to work from within NetBeans by commenting out the
> available task that sets the 'jakarta.regexp.present' property, but I was
> wondering if anyone else is building Ant from NetBeans and have seen this
> problem?
>
> Platform:
> Windows XP
> JDK 1.3.1 (although netbeans is running on 1.4)
> Ant 1.4.1 source code
> NetBeans 3.3.1
> Using Jikes as well (but it happens with ordinary javac too)
>
we fixed some problems with JDK1.4 on XP in ant1.5; if your build crashes in
<property env>, that is why. Dunno about why it wont build, maybe the
netbeans regexp isnt complete. Actually, on a jdk1.4 build it should pick up
the java1.4 regexp set too.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Newbie: Building Ant 1.4.1 from within NetBeans - wierd problem with 'available' task for RegExp jar
Posted by Shorn Tolley <sh...@hotmail.com>.
Hi folks,
I am trying to build the Ant source code for 1.4.1.
(as an aside, are there any FAQs or anything I should be reading as a first
time Ant builder?)
I am able to build Ant 1.4.1 from the command line using a binary download
of Ant 1.4.1.
When I try to build Ant from within NetBeans (using the Ant project
build.xml file), the compile fails because the script tries to build the
org.apache.tools.ant.util.regexp.JakartaRegexpMatcher.java file.
This does not happen from the command line because I haven't got the
regexp.jar in my classpath or anywhere else for that matter. Which means
the 'available' task in the 'check_for_optional_packages' target doesn't set
the 'jakarta.regexp.present' property, which means the JakartaRegexpMatcher
class gets excluded from the build.
Unfortunately, when building from within NetBeans, the available task seems
to find the RE regexp class, which means it then sets the
'jakarta.regexp.present' property, which eventually causes the build to
fail. I /think/ the RE class is being picked up from the NetBeans
classpath. (regexp.jar /is/ in the 'netbeans.class.path').
I have gotten the build to work from within NetBeans by commenting out the
available task that sets the 'jakarta.regexp.present' property, but I was
wondering if anyone else is building Ant from NetBeans and have seen this
problem?
Platform:
Windows XP
JDK 1.3.1 (although netbeans is running on 1.4)
Ant 1.4.1 source code
NetBeans 3.3.1
Using Jikes as well (but it happens with ordinary javac too)
Thanks,
Shorn.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: How do I get rid of the "Compile failed..." message from Ant when the javac task reports erros?
Posted by Diane Holt <ho...@yahoo.com>.
--- Shorn Tolley <sh...@hotmail.com> wrote:
> I got halfway through doing the same kind of thing, then I realised that
> it wasn't DefaultLogger's problem.
It's not? -- that's who's printing it out, so it seems like it's its
problem to me :)
> Now my approach is that I will just make the javac task not provide a
> location with the BuildException that it throws,
Yeah, but you don't really want to do that, because if there's a booboo in
the <javac> task, like a misspelled attribute or bad nesting, etc., you do
want that sort of thing printed out. Anyway, like I said, mine seems to
work fine for the various tests I've put it to (it's actually a very
small, simple change), so if you want to try it, you're welcome to. (I
actually prefer NoBannerLogger as my default logger, so I've made an
NBLogger.java that extends MyLogger, so if you also prefer NoBannerLogger
[and, really, who wouldn't :)] and you'd like both of them [ie., you'd use
NBLogger as your logger (set in ANT_ARGS, of course, to make like even
simpler)], let me know.)
Diane
=====
(holtdl@yahoo.com)
__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: How do I get rid of the "Compile failed..." message from Ant when the javac task reports erros?
Posted by Shorn Tolley <sh...@hotmail.com>.
Hi Diane,
I got halfway through doing the same kind of thing, then I realised that it
wasn't DefaultLogger's problem.
Now my approach is that I will just make the javac task not provide a
location with the BuildException that it throws, then the logger shouldn't
output the location, which means that the error message will still print,
minus the location info, which means the IDE regular expressions won't see
it as an error message.
I think it's a cleaner solution.
Unfortunately, I was just about to do it, then I got the sh*ts with IDEA and
switched back to NetBeans. Now I'm having trouble building Ant from
NetBeans.
(the 'available' task that is supposed to _not_ set the
jakarta.regexp.present property so that the
org.apache.tools.ant.util.regexp.JakartaRegexpMatcher.java file gets
excluded from the javac task is picking up the regexp package from the
NetBeans classpath, *sigh*)
Sorry for the run-on sentences, its 1am. :)
Shorn.
----- Original Message -----
From: "Diane Holt" <ho...@yahoo.com>
To: "Ant Users List" <an...@jakarta.apache.org>
Sent: Sunday, June 02, 2002 12:41 AM
Subject: Re: How do I get rid of the "Compile failed..." message from Ant
when the javac task reports erros?
> I have it check the error string, and if it contains "Compile failed",
> skip all the rest of the output; otherwise, output everything as usual.
> Seems to work fine (not exhaustively tested, but hand-tested enough to
> make me pretty sure it's fine). If anyone would like it, let me know.
>
> Diane
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: How do I get rid of the "Compile failed..." message from Ant when the javac task reports erros?
Posted by Diane Holt <ho...@yahoo.com>.
Oops -- undefined pronoun :) By "it", I mean I copied DefaultLogger.java
to MyLogger.java and modified that -- then I set my logger to be that one.
Diane
=====
(holtdl@yahoo.com)
__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: How do I get rid of the "Compile failed..." message from Ant when the javac task reports erros?
Posted by Diane Holt <ho...@yahoo.com>.
--- Erik Hatcher <ja...@ehatchersolutions.com> wrote:
> I'm not quite sure how this change should be made - perhaps a
> command-line switch that tells Ant not to print the line number
> information or something like that? Again, such a change would affect
> all tasks, not just <javac>.
I have it check the error string, and if it contains "Compile failed",
skip all the rest of the output; otherwise, output everything as usual.
Seems to work fine (not exhaustively tested, but hand-tested enough to
make me pretty sure it's fine). If anyone would like it, let me know.
Diane
=====
(holtdl@yahoo.com)
__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: How do I get rid of the "Compile failed..." message from Ant when the javac task reports erros?
Posted by Erik Hatcher <ja...@ehatchersolutions.com>.
----- Original Message -----
From: "Shorn Tolley" <sh...@hotmail.com>
To: "Ant Users List" <an...@jakarta.apache.org>
Sent: Saturday, June 01, 2002 4:22 PM
Subject: Re: How do I get rid of the "Compile failed..." message from Ant
when the javac task reports erros?
> So, it's not an effect of the javac task, but an effect of the way tasks
> communicate with the main Ant engine?
> (that is, task has problem, prints info about problem, throws exception to
> Ant to let it know task failed, Ant prints info about exception thrown?)
Thats pretty much it. Actually the task does not even print the info in this
case, it throws a BuildException with the message in the exception. The
engine prints it, along with the line number info.
> Would it not be feasible to turn off _the reporting_ of the fact that the
> exception was thrown?
You can set failonerror="false" on <javac>, which causes the message to be
logged, but no line number info, but then the build continues, which is not
usually very desirable after compilation fails.
> This is not a whinge (much), I would actually be prepared to go and play
> with the code to make this happen, it's been bugging me for aaaaages.
Have at it! :)
I'm not quite sure how this change should be made - perhaps a command-line
switch that tells Ant not to print the line number information or something
like that? Again, such a change would affect all tasks, not just <javac>.
Erik
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: How do I get rid of the "Compile failed..." message from Ant when the javac task reports erros?
Posted by Shorn Tolley <sh...@hotmail.com>.
So, it's not an effect of the javac task, but an effect of the way tasks
communicate with the main Ant engine?
(that is, task has problem, prints info about problem, throws exception to
Ant to let it know task failed, Ant prints info about exception thrown?)
Would it not be feasible to turn off _the reporting_ of the fact that the
exception was thrown?
I'm not saying all the time (I have found the automatic navigation straight
to the build file to be helpful on plenty of occasions), just when you're
pretty sure you've got everything sweet on the Ant configuration front.
Say for instance, when you specify the -emacs output mode?
This is not a whinge (much), I would actually be prepared to go and play
with the code to make this happen, it's been bugging me for aaaaages.
Shorn
----- Original Message -----
From: "Erik Hatcher" <ja...@ehatchersolutions.com>
To: "Ant Users List" <an...@jakarta.apache.org>
Sent: Saturday, June 01, 2002 8:23 PM
Subject: Re: How do I get rid of the "Compile failed..." message from Ant
when the javac task reports erros?
> If a task throws a BuildException from its execute method (or any
exception
> for that matter) it is reported along with the line number in the build
file
> that caused the error. It can be useful to navigate directly to the build
> file in the case of an error as it could have been caused by something
> incorrectly specified there. It just happens to do the same thing after
> compiling source code too.
>
> If you're using IDEA, why do you have compile errors in the first place?!
> :) It shows you in the side bar with red when there are compilation
errors.
>
> Anyway, there really is no good way to avoid this as it is using the same
> mechanism for all tasks, and is not something <javac> is doing
explicitly -
> its simply notifying the engine that the build should fail.
>
> Erik
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: How do I get rid of the "Compile failed..." message from Ant when the javac task reports erros?
Posted by Erik Hatcher <ja...@ehatchersolutions.com>.
----- Original Message -----
From: "Shorn Tolley" <sh...@hotmail.com>
To: "Ant Users List" <an...@jakarta.apache.org>
Sent: Saturday, June 01, 2002 3:09 PM
Subject: Re: How do I get rid of the "Compile failed..." message from Ant
when the javac task reports erros?
> Yep, that's basically exactly what happens with NetBeans.
> And now that I am trying out IDEA, it's even worse, because IDEA reports
the
> Ant build messages in a kind of hierarchical tree. For some reason the
IDE
> propogates the error message to every level, so the superfluous message
> tends to clutter up the display.
>
> So this message interferes with the integration of Ant and multiple IDEs
> (Emacs / Xemacs, NetBeans and IDEA)
>
> Does any one know why this message is reported?
If a task throws a BuildException from its execute method (or any exception
for that matter) it is reported along with the line number in the build file
that caused the error. It can be useful to navigate directly to the build
file in the case of an error as it could have been caused by something
incorrectly specified there. It just happens to do the same thing after
compiling source code too.
If you're using IDEA, why do you have compile errors in the first place?!
:) It shows you in the side bar with red when there are compilation errors.
Anyway, there really is no good way to avoid this as it is using the same
mechanism for all tasks, and is not something <javac> is doing explicitly -
its simply notifying the engine that the build should fail.
Erik
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: How do I get rid of the "Compile failed..." message from Ant when the javac task reports erros?
Posted by Shorn Tolley <sh...@hotmail.com>.
Yep, that's basically exactly what happens with NetBeans.
And now that I am trying out IDEA, it's even worse, because IDEA reports the
Ant build messages in a kind of hierarchical tree. For some reason the IDE
propogates the error message to every level, so the superfluous message
tends to clutter up the display.
So this message interferes with the integration of Ant and multiple IDEs
(Emacs / Xemacs, NetBeans and IDEA)
Does any one know why this message is reported?
----- Original Message -----
From: "Kendall Collett" <kc...@convio.com>
To: "Ant Users List" <an...@jakarta.apache.org>
Sent: Saturday, June 01, 2002 7:20 PM
Subject: Re: How do I get rid of the "Compile failed..." message from Ant
when the javac task reports erros?
> This is also irritating from the emacs perspective in that next-error will
> process the "error" in the build file. When I have more than a couple of
> compilation errors, I invariably go "one C-x ` too far" and end up
visiting
> the build file. I've gotten used to killing the buffer about a half
second
> after I do that, but it's still a pain.
>
> Kendall
>
> ----- Original Message -----
> From: "Shorn Tolley" <sh...@hotmail.com>
> To: <an...@jakarta.apache.org>
> Sent: Friday, May 31, 2002 17:31
> Subject: How do I get rid of the "Compile failed..." message from Ant when
> the javac task reports erros?
>
>
> > [...]
> >
> > When I'm compiling a project and I have a syntax error, Ant reports line
> > numbers and all that guff about the error; excellent, fine, that's what
I
> > want.
> > But, it also always outputs the following after outputting information
> about
> > the syntax errors:
> >
> > BUILD FAILED
> >
> > <location>\build.xml:<line number>: Compile failed, messages should have
> > been provided.
> >
> > This message, which looks like Ant is reporting a syntax error within
the
> > actual build file, is really annoying. It's annoying because some IDEs
> > (NetBeans and IDEA specifically, probably others too) will simply assume
> > this message is telling the user about an error in the XML file. When
it's
> > not really, it's telling the user that some target within the file
failed.
> >
> > [...]
>
>
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: How do I get rid of the "Compile failed..." message from Ant when the javac task reports erros?
Posted by Kendall Collett <kc...@convio.com>.
This is also irritating from the emacs perspective in that next-error will
process the "error" in the build file. When I have more than a couple of
compilation errors, I invariably go "one C-x ` too far" and end up visiting
the build file. I've gotten used to killing the buffer about a half second
after I do that, but it's still a pain.
Kendall
----- Original Message -----
From: "Shorn Tolley" <sh...@hotmail.com>
To: <an...@jakarta.apache.org>
Sent: Friday, May 31, 2002 17:31
Subject: How do I get rid of the "Compile failed..." message from Ant when
the javac task reports erros?
> [...]
>
> When I'm compiling a project and I have a syntax error, Ant reports line
> numbers and all that guff about the error; excellent, fine, that's what I
> want.
> But, it also always outputs the following after outputting information
about
> the syntax errors:
>
> BUILD FAILED
>
> <location>\build.xml:<line number>: Compile failed, messages should have
> been provided.
>
> This message, which looks like Ant is reporting a syntax error within the
> actual build file, is really annoying. It's annoying because some IDEs
> (NetBeans and IDEA specifically, probably others too) will simply assume
> this message is telling the user about an error in the XML file. When it's
> not really, it's telling the user that some target within the file failed.
>
> [...]
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>