[ http://jira.codehaus.org/browse/DOXIA-82?page=comments#action_83352 ] Henning Schmiedehausen commented on DOXIA-82: ---------------------------------------------
The default for logging messages from the VelociMacros will be changing in Velocity 1.5 Either you must set "velocimacro.messages.on = false" in the defaults of the Plexus Velocity component. It would be much better if the Doxia Renderer splits the VelociMacros into its own macro library and a skin template. Then you would declare the macro file to be a macro library. However, this again would need changes to the plexus velocity component (which is a bad idea anyway as it is as a singleton very inflexible and the usage of Velocity in different parts of Maven and Doxia interferes with each other (e.g. in the availability of macros). Either Plexus should declare a Factory that returns VelocityEngine instances that can be configured by e.g. Doxia) or you should not use any Plexus component here but build the Velocity engine yourself. > Doxia default site renderer redefines local macros over and over again > ---------------------------------------------------------------------- > > Key: DOXIA-82 > URL: http://jira.codehaus.org/browse/DOXIA-82 > Project: doxia > Issue Type: Bug > Reporter: Henning Schmiedehausen > > The Doxia default site renderer uses Apache Velocity to render its pages. > Every time a page is rendered, Doxia tries to define Velocity Macros but the > Plexus Velocity component sets the replacement of Velocity Macro to false > (the default). > In Velocity Version 1.4, these error messages are silently discarded. In > newer Versions (1.5 beta 2 and beyond), these messages are logged out and > appear to be errors. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
