You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Will Glass-Husain (JIRA)" <ji...@apache.org> on 2005/09/18 23:14:54 UTC
[jira] Resolved: (VELOCITY-83) #include directive a bad choice...
[ http://issues.apache.org/jira/browse/VELOCITY-83?page=all ]
Will Glass-Husain resolved VELOCITY-83:
---------------------------------------
Resolution: Fixed
Assign To: (was: Velocity-Dev List)
Hi,
I'm going to close this very old issue. You can now edit the file "directive.properties" to change the name of the include directive.
> #include directive a bad choice...
> ----------------------------------
>
> Key: VELOCITY-83
> URL: http://issues.apache.org/jira/browse/VELOCITY-83
> Project: Velocity
> Type: Bug
> Components: Testing
> Versions: 1.3-rc1
> Environment: Operating System: Solaris
> Platform: Sun
> Reporter: John
>
> I've come across a situation where I need to place netscape server-side
> includes within my velocity template. <!--#include virtual="blah/blah.html" --
> > is seen to Velocity as a parse error since it's mistaking the netscape
> include for a velocity include.
> To me, this seems like a design flaw. Having netscape SSI calls in velocity
> templates increases the flexibility of the templates.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org