>- in build.xml, in the task trim-whitespace there is a reference to >*.wtkx , but now we have also *.wtkd files, so i think it would be >better to change this filter to *.wtk*, or add a reference to *.wtkd
Good catch. I have added "*.jsp" and "*.wtkx" to the "trim-whitespace" target. >- in build.xml, html pages are as .template.html, and then copied as .html, Ok. > For jsp pages I have to do the same, right ? The templates are used to make sure that the HTML files use the right Pivot version (see the "@version@" tags in the *.template.html files). Now that I think about it, it occurs to me that there might be a better alternative. We could simply define one version.template.js file that is processed by the build and use that to dynamically construct the JAR file names in JavaScript. You could do something similar in JSP (e.g. version.template.jsp). > And add jsp in some filter, like already done for jnlp, right ? Not sure what you mean by this. >- in README maybe we should add also the requirement that some pages >are dynamic and requires JSP to work. I've used stripped version of >Jetty without jsp for example, but this is not an usual configuration, >so should not be a problem. I think the fact that we package these files into a WAR is probably sufficient notice that a servlet container is required.
