You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Trevor Harmon (JIRA)" <ji...@codehaus.org> on 2010/08/15 20:23:32 UTC
[jira] Created: (JXR-84) Spurious error message fixed in Velocity
1.5 still exists in JXR
Spurious error message fixed in Velocity 1.5 still exists in JXR
----------------------------------------------------------------
Key: JXR-84
URL: http://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
Priority: Minor
Attachments: example.zip, 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.
-
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
[jira] Commented: (JXR-84) Spurious error message fixed in Velocity
1.5 still exists in JXR
Posted by "Benson Margulies (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (JXR-84) Spurious error message fixed in Velocity
1.5 still exists in JXR
Posted by "Benson Margulies (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/JXR-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=272910#comment-272910 ]
Benson Margulies commented on JXR-84:
-------------------------------------
I'm having some sort of classpath heck with this fix; I've attached a patch in case anyone else cares to have a look.
> 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
[jira] Closed: (JXR-84) Spurious error message fixed in Velocity
1.5 still exists in JXR
Posted by "Benson Margulies (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/JXR-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benson Margulies closed JXR-84.
-------------------------------
Resolution: Fixed
Fix Version/s: 2.3
Note fiddly code to manage the thread context class loader.
> 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
> Fix For: 2.3
>
> 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
[jira] Updated: (JXR-84) Spurious error message fixed in Velocity
1.5 still exists in JXR
Posted by "Benson Margulies (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/JXR-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benson Margulies updated JXR-84:
--------------------------------
Attachment: JXR-84.patch
> 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
[jira] Updated: (JXR-84) Spurious error message fixed in Velocity
1.5 still exists in JXR
Posted by "Trevor Harmon (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/JXR-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Trevor Harmon updated JXR-84:
-----------------------------
Attachment: example.zip
Simplest possible test project that reproduces the error. Simply run "mvn site".
> Spurious error message fixed in Velocity 1.5 still exists in JXR
> ----------------------------------------------------------------
>
> Key: JXR-84
> URL: http://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
> Priority: Minor
> Attachments: example.zip, 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.
-
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