Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
3.2.0
-
None
Description
When I run: mvn site, using my project's pom: https://github.com/nahsra/antisamy/blob/main/pom.xml
I'm seeing the following warnings. I think this means these jxr-plugins are using old resource names. Unless I'm doing something wrong in my pom. But I can't find any references to these resources in my project, so I'm assuming its a problem in your project. Can you confirm this is an issue in maven-jxr and you can fix it? Or is it my fault?
The velocity configuration key changes are described here: https://velocity.apache.org/engine/devel/configuration-property-changes-in-2.1.html
[*INFO*] Generating "Source Xref" report --- maven-jxr-plugin:3.2.0:jxr
[*WARNING*] configuration key 'resource.loader' has been deprecated in favor of 'resource.loaders'
[*WARNING*] configuration key 'classpath.resource.loader.class' has been deprecated in favor of 'resource.loader.classpath.class'
[*WARNING*] configuration key 'velocimacro.library' has been deprecated in favor of 'velocimacro.library.path'
[*INFO*] Generating "Test Source Xref" report --- maven-jxr-plugin:3.2.0:test-jxr
[*WARNING*] configuration key 'resource.loader' has been deprecated in favor of 'resource.loaders'
[*WARNING*] configuration key 'classpath.resource.loader.class' has been deprecated in favor of 'resource.loader.classpath.class'
[*WARNING*] configuration key 'velocimacro.library' has been deprecated in favor of 'velocimacro.library.path'
Attachments
Issue Links
- depends upon
-
JXR-188 Upgrade to Doxia 2.0.0 Milestone Stack
- Closed
- is related to
-
JXR-166 Two versions of velocity engines on plugin classpath
- Closed
-
JXR-174 Revert JXR-157 until next major version
- Closed
-
DOXIASITETOOLS-230 Upgrade to Velocity Engine 2.3 and Velocity Tools 3.1
- Closed