i'm experiencing similar problems when i use the precompiler. in my
case, with layouts. i'm using 1.6.0-SNAPSHOT and SSP templates.
my templates are in a scalate dir under the source/main/webapp dir.
this scalate dir contains 2 subdirs: layouts and templates.
it seems that when i use relative paths in my templates (which are
stored under webapp/scalate/templates), like this:
<% layout("../layouts/base.ssp") { %>
it doesn't find the precompiled template, and so i guess it will try
to compile this template, which doesn't work since i don't include the
scala compiler in production.
but when i change it to this:
<% layout("scalate/layouts/base.ssp") { %>
it just works.
so it might be that referencing templates with relative paths might be
broken. i'm sure that relative paths work when i don't precompile and
let scalate compile at runtime, cause that's what i do in development
mode.
i'll get back on this and add a stacktrace and maybe a patch if i can
find what's wrong.
Thanks,
Stefan De Boey
On Jun 9, 9:46 am, James Strachan <
ja...@fusesource.com> wrote:
> Sorry for the delay replying Sébastien! A combination of being snowed
> for CamelOne conference then vacation...
>
> This maybe sounds like a bug; I wonder if the maven compile plugin
> isn't detecting the partial for some reason. I've raised an issue to
> track it...
https://www.assembla.com/spaces/scalate/support/tickets/247