Mark,
I've verified that your fix in rev 890479 works great for this.
Many thanks for fixing it so quickly!
david jencks
On Dec 14, 2009, at 11:25 AM, Mark Thomas wrote:
On 14/12/2009 03:58, David Jencks wrote:
I can verify by experiment that the 2nd solution fixes the problem
with
jspC.
On 14/12/2009 03:58, David Jencks wrote:
> I can verify by experiment that the 2nd solution fixes the problem with
> jspC. I agree that there's a strong case to be made for moving
> DefaultJarScanner to org.apache.tomcat but doing so introduces a lot of
> dependencies from that package to
>
> org
On Dec 13, 2009, at 12:46 PM, Mark Thomas wrote:
On 13/12/2009 09:50, David Jencks wrote:
It looks to me as if the problem is that no JarScanner is installed
in
the ServletContext used by JspC. (There definitely isn't one
installed,
and I think that is the cause of the problem). So, jaspe
On 13/12/2009 09:50, David Jencks wrote:
> It looks to me as if the problem is that no JarScanner is installed in
> the ServletContext used by JspC. (There definitely isn't one installed,
> and I think that is the cause of the problem). So, jasper cant find the
> jstl jar which is in the classlo
Jar scanning for tld files seems to have been refactored recently in
rev 817685 (sept 22 2009) with the introduction of the jasper
JarScannerFactory.
I'm getting a stack trace:
[INFO] [jspc:compile {execution: default}]
Created dir: /Users/david/projects/geronimo/server/trunk/plugins/
activ
