Sorry for the late reply...
The maven dependency I found is
tomcat
jasper-compiler-jdt
5.5.12
Uh ...looks like a self-assembled version. Not nice. I would give it
go with jardiff and see how much it differs from the original jar.
Don't ask me how I found it, I jus
Curdt
Sent: July 19, 2006 4:48
To: Jakarta Commons Developers List
Subject: Re: RE: [JCI] RE: JCI, JDT and Tomcat/JBoss
> Concerning the statics, I was referring to the INSTANCE in
> JavaCompilerFactory. The instance has a class cache which could
> potentially lead to non-garbag
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.
Well, the usual singleton ...should be alright. But I am not religious
on that one.
Also concerning the versions, what I did is
ta Commons Developers List
Subject: Re: [JCI] RE: JCI, JDT and Tomcat/JBoss
> 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.
That sou
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.
That sounds rather bizarre to me ...I will investigate a bit
The error I had with JDT 3.1 was
java.lang.N
