[I posted this on the Megg page comments, which is probably not the
right place!]

There seems to be a bug in megg's template handler. I downloaded megg
from CVS (because I wanted to have a go at writing a template) and
tried to build and test it using "ant all". It failed the Unit test
"testGenerate" which attempts to find templates/java in the current
"working diectory" (I assume that's the classpath). Message is
"template 'templates/java' does not exist".

At first I thought that templates/java needed to be copied into the
build/classes directory before the test (which might actually be the
case) so I modified the build file slightly, but when that didn't work
I looked a little deeper.

It looks like inside the "templates" bit of the filename gets removed
when you look for a template in the "." directory. It appears that you
actually look for ./java rather than ./templates/java (but I could
have misinterpreted your code). Because you can get hold of the
templates using $HOME/.megg, existing jar files, and URLs maybe you
don't see this behaviour when you run the unit tests from your end.

Is this a bug?

Chris