Thomas Nielsen wrote:
Vemund Ostgaard wrote:
* You need to download emma.jar and emma_ant.jar and put them in your
tools/java/ directory.
Could we have the emma target check for presence of emma.jar and post
a friendly errormessage if it can't find it?
I guess we could do that. I did a quick check to see what is actually
printed if both of these jars are missing and saw the following:
BUILD FAILED
/usr/local/cluwin/vo136787/derby/source/trunk/build.xml:2185: Problem:
failed to create task or type emma
Cause: The name is undefined.
Action: Check the spelling.
Action: Check that any custom tasks/types have been declared.
Action: Check that any <presetdef>/<macrodef> declarations have taken place.
So, I guess this is not what happened to Manjula, and it could be more
informative than this.
I'm looking at a different EMMA issue, to get the right permissions set
for some tests that spawn a network server with a default policy. I'll
see if I can improve the output if emma*.jar is missing as well.
Come to think of it, would it be possible to just have emma.jar and
emma_ant.jar checked into the derby codeline under tools/java/ to avoid
developers having to download it themselves, figuring out what version
to use, etc.?
As far as I can see EMMA has a CPL v1.0 license;
http://emma.sourceforge.net/license.html
Anyone know if that would be a problem?
Vemund
