Bug 1213

The Javac task makes use of the build.compiler property to determine the 
compiler it should use (javac, jikes, etc.).  The EJBJar task uses an attribute 
in the nested Weblogic element to do the same thing (the attribute 
is 'compiler').  It would be nice if either 

1) EJBJar used the build.compiler property just as Javac does.  This would 
effectively link the two tasks ensuring they use the same compiler.  I've had 
UnmarshallingExceptions galore when using EJBs where container classes are 
generated using Javac but the bean classes are compiled using Jikes.  This 
option is a little less flexible.

2) Javac used an attribute to control the compiler, the same way that EJBJar 
does.  This way, they could be linked by a property if that's what you want, 
but it's flexible enough to have them use seperate compilers if THAT's what you 
want (for whatever reason).

Not a high priority, since I'm sure there's a workaround right now.
Thanks,
David