Will something like this be useful?

[Nico Seessle <ni...@seessle.de>]

If a task specifies it's configuration is wrong it throws a
ConfigurationException. Target then asks Task to print it's current
configuration and stops the build. (Will only work in a nice way with the
help of RuntimeConfigurable I think :-) )

What do you think?

Nico


Example:

Buildfile: build.xml

default:
Configuration error
===================
Task: vsslabel
haltonerror = not specified
output = not specified
date = not specified
ssdir = not specified
vsspath = not specified
haltonwarning = not specified
comment = not specified
version = not specified
login = not specified
label = not specified
taskname = not specified
description = not specified

BUILD FAILED

build.xml:8: vsspath attribute must be set!

Total time: 0 seconds

Re: Will something like this be useful?

[Stefan Bodewig <bo...@bost.de>]

>>>>> "NS" == Nico Seessle <ni...@seessle.de> writes:

 NS> If a task specifies it's configuration is wrong it throws a
 NS> ConfigurationException. Target then asks Task to print it's
 NS> current configuration and stops the build.

I don't really see what the benefit would be, In you example I'd know
the problem is in the <vssget> task on line 8 and the the required
attribute vsspath hasn't been set.

If I look at line 8 - which I'll have to do anyway if I want to fix
the problem, I can gather all the information at a glance.

Stefan