Jasper Reports

After upgrading to Lucee, Denny’s Jasper Reports custom tag was not working.

For some reason assuming by design it was no longer looking in the
following directory for the custom tag
WEB-INF\lucee\library\tag

I was able to get it running by moving the files from that location to
WEB-INF\lucee\customtags

just thought I’d throw that out there if anyone else experiences the issue.

Will this also be the case for any custom functions we’ve built etc?

After upgrading to Lucee, Denny’s Jasper Reports custom tag was not
working.

For some reason assuming by design it was no longer looking in the
following directory for the custom tag
WEB-INF\lucee\library\tag

I was able to get it running by moving the files from that location to
WEB-INF\lucee\customtags

just thought I’d throw that out there if anyone else experiences the issue.

Will this also be the case for any custom functions we’ve built etc?

Ja, I imagine so.

FWIW, there is an Ant macrodef for building extensions, which I ported
already, so one can build them for both engines if necessary-- though it
would be cool to come up with a cleaner solution (doable, with a bit of
thought).

Maybe the updated JasperReports extension will be the first to work with
both, without needing separate artifacts.

-DenOn Thu, Feb 5, 2015 at 10:53 AM, Terry Bankert wrote: