This doesn't happen with forrest trunk (r369625) and using skins. However when using Dispatcher it does (both in 'forrest run' mode and 'forrest site' mode).
The source document (either our xdoc or source html) contains text like this:
This doesn't happen with forrest trunk (r369625) and using skins. However when using Dispatcher it does (both in 'forrest run' mode and 'forrest site' mode).
The source document (either our xdoc or source html) contains text like this:
<p>
... (usually pmc@{project-name}.apache.org)
</p>
The error is: "Can't find a compiler for js".
It can be part of FOR-745 (I still need to test this) but "Can't find a compiler for js" seems to me that cocoon is interpreting @{project-name} as expression (IMO more jx the js). What does *.body.xml give?
Thorsten Scherler added a comment - 20/Jan/06 07:50 PM It can be part of FOR-745 (I still need to test this) but "Can't find a compiler for js" seems to me that cocoon is interpreting @{project-name} as expression (IMO more jx the js). What does *.body.xml give?
Bug
Closed
Major
Dispatcher has severe parsing error when source text like pmc@{project-name} ... looks for compiler for js
FOR-745(I still need to test this) but "Can't find a compiler for js" seems to me that cocoon is interpreting @{project-name} as expression (IMO more jx the js). What does *.body.xml give?