The maven dependency I found is
tomcat
jasper-compiler-jdt
5.5.12
Don't ask me how I found it, I just made a search using the maven
eclipse plugin, except that, I'm not too maven fluent.
The mock + abstract test classes sounds very good to me.
I just started writing
Concerning the statics, I was referring to the INSTANCE in
JavaCompilerFactory. The instance has a class cache which could
potentially lead to non-garbageable stuff.
Also concerning the versions, what I did is use the tomcat JDT in the
maven dependencies. I'm not even 100% if it is a vanilla 3.1
I believe the compiler links somehow to a particular version of an
interface... Even if the methods signatures are the same, if the
interface is different, I'm not sure it links correctly.
The error I had with JDT 3.1 was
java.lang.NoSuchMethodError:
org.eclipse.jdt.internal.compiler.CompilationR
I've been having some issues lately with JBoss Rules running inside JBoss AS.
JBoss Rules uses JCI as backend for compiling the rules.
The JDT plugin for JCI is compiled against the version 3.2 of JDT but JBoss and
Tomcat contain version 3.1 of JDT.
I downloaded all the SVN sources from the tru
