Right...the only reason this is different is because the <!--#include is valid HTML, and #if is not...
On Wed, Aug 20, 2008 at 4:32 PM, Nathan Bubna (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/VELOCITY-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Nathan Bubna resolved VELOCITY-584. > ----------------------------------- > > Resolution: Won't Fix > Fix Version/s: 2.0 > > On further thought, we throw errors for any erroneous VTL. Stray #if, > #foreach, or #end would also require some escaping work. I don't see any > reason to be flexible with #include when we're not with the rest. Perhaps in > 2.0? > >> Change the #include directive ignore the SSI version of include >> --------------------------------------------------------------- >> >> Key: VELOCITY-584 >> URL: https://issues.apache.org/jira/browse/VELOCITY-584 >> Project: Velocity >> Issue Type: Improvement >> Components: Engine >> Affects Versions: 1.5 >> Reporter: Tim White >> Fix For: 2.0 >> >> >> When processing a file that happens to have the SSI version of 'include' in >> it, the velocity engine breaks. >> There are many cases where we end up with files that contain both, before >> they are cleaned up. >> <!--#include file="wisdom.inc"--> >> Essentially, if it sees that syntax, it needs to ignore the include. A >> suggestion would be to check for any amount of whitespace after the >> #include, and then "file=". I don't think that will step on proper Velocity >> include syntax. > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
