[ 
https://jira.codehaus.org/browse/JXR-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=272965#comment-272965
 ] 

Benson Margulies commented on JXR-84:
-------------------------------------

r1145408 | bimargulies | 2011-07-11 20:38:49 -0400 (Mon, 11 Jul 2011) | 4 lines

[JXR-84] Spurious error message fixed in Velocity 1.5 still exists in JXR
o update the whole business to velocity 1.5, which, to match up with plexus and 
doxia, also required
updating to doxia 1.2 and making related tweaks. While here, move a few easy 
things from plexus-utils to commons.

------------------------------------------------------------------------


> Spurious error message fixed in Velocity 1.5 still exists in JXR
> ----------------------------------------------------------------
>
>                 Key: JXR-84
>                 URL: https://jira.codehaus.org/browse/JXR-84
>             Project: Maven JXR
>          Issue Type: Bug
>          Components: jxr
>         Environment: Mac OS X 10.6.4, Java 1.6.0_20, Maven 2.2.1
>            Reporter: Trevor Harmon
>            Assignee: Benson Margulies
>            Priority: Minor
>         Attachments: example.zip, JXR-84.patch, log.txt
>
>
> There was a bug in Velocity 1.4 that was causing a spurious error message to 
> be printed:
>  [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in 
> any resource loader.
>  [INFO] Velocimacro : error using  VM library template VM_global_library.vm : 
> org.apache.velocity.exception.ResourceNotFoundException: Unable to find 
> resource 'VM_global_library.vm'
> This affects many Maven users who include JXR reports with their site 
> generation. That is because JXR uses Velocity, and thus the innocuous error 
> would be displayed on every "mvn site".
> With the release of Velocity 1.5 in 2007, the bug was fixed:
>  https://issues.apache.org/jira/browse/VELOCITY-86
> But even when using the latest versions of JXR (2.2) and the Site plugin 
> (2.1.1), the error message still appears. This is because in the dependency 
> tree, the old Velocity 1.4 release is being pulled in (see attached build 
> log).
> The component with a direct dependency on Velocity 1.4 is maven-jxr (not the 
> plugin but the library). Updating it to use Velocity 1.5 would presumably 
> cause the error message to go away.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to