[ http://jira.codehaus.org/browse/MSITE-170?page=comments#action_79832 ] Dennis Lundberg commented on MSITE-170: ---------------------------------------
The issue in Velocity can now be found at this address: http://issues.apache.org/jira/browse/VELOCITY-71 It seems to have been resolved. I'll try to build the site plugin with a nightly build of Velocity, to see if it solves the issue in the site plugin. > [ERROR] VM #displayTree: error : too few arguments to macro > ----------------------------------------------------------- > > Key: MSITE-170 > URL: http://jira.codehaus.org/browse/MSITE-170 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Affects Versions: 2.0 > Reporter: fabrizio giustina > > when running mvn site:site a couple of "too few arguments to macro" always > pop up. This is extremely bad in terms of user experience, and we should find > a way to remove these logs: > [ERROR] VM #displayTree: error : too few arguments to macro. Wanted 2 got 0 > [ERROR] VM #menuItem: error : too few arguments to macro. Wanted 1 got 0 > These errors are due to a known velocity bug related to the use of recursive > macros: > http://issues.apache.org/bugzilla/show_bug.cgi?id=13623 > http://mail-archives.apache.org/mod_mbox/jakarta-velocity-user/200402.mbox/[EMAIL > PROTECTED] > Recursive macros are defined in > org/apache/maven/doxia/siterenderer/resources/default-site.vm in the doxia > site-renderer component. > Logging is handled in the plexus velocity component. > This velocity bug is still open in velocity and no patch will be available > anytime soon. In the meanwhile we should try to handle this situation in some > way by filtering out messages or removing the use of recursive macros (very > hard, they are used to print out the site tree)... or switching to a better > templating engine like freemarker. > This issue could probably be addressed in the plexus velocity component or in > the doxia site renderer (given that waiting for a bugfixed velocity release > is not an option). I'm anyway assigning it to the site plugin since it's > where users see these logs coming from and where probably users could open > similar issues. > Any suggestion on how to dirty-patch this? -- 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
