You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2007/04/03 02:44:08 UTC
[jira] Updated: (MSITE-170) [ERROR] VM #displayTree: error : too
few arguments to macro
[ http://jira.codehaus.org/browse/MSITE-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MSITE-170:
-------------------------------
Fix Version/s: 2.0-beta-6
Does velocity 1.5 help with this?
> [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-beta-6
> Reporter: fabrizio giustina
> Fix For: 2.0-beta-6
>
>
> 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/%3COF0D830C11.BA641EAF-ON85256E30.00736DF8@chase.com%3E
> 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