[JXR-166] Two versions of velocity engines on plugin classpath

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.2.0
• Fix Version/s: 3.3.0
• Assignee: Michael Osipov
• Reporter: Slawomir Jaranowski
• Created: 10/Mar/22 22:44
• Updated: 16/Aug/22 09:09
• Resolved: 16/Aug/22 09:09

Description

Velocity engine change artifactId in updates 1.7.x to 2.0.x

https://velocity.apache.org/engine/2.2/upgrading.html#upgrading-from-velocity-17-to-velocity-20

Now we have both.

Dependency tree:

org.apache.maven.plugins:maven-jxr-plugin:maven-plugin:3.2.0-SNAPSHOT

+- org.apache.maven:maven-jxr:jar:3.2.0-SNAPSHOT:compile
|  +- org.apache.velocity:velocity-engine-core:jar:2.3:compile

+- org.apache.maven.reporting:maven-reporting-impl:jar:3.1.0:compile

|  \- org.apache.maven.doxia:doxia-site-renderer:jar:1.11.1:compile
|     +- org.codehaus.plexus:plexus-velocity:jar:1.2:compile
|     +- org.apache.velocity:velocity:jar:1.7:compile
|     +- org.apache.velocity:velocity-tools:jar:2.0:compile

 
I don't see any errors so far ... but should be fixed.

Issue Links

• depends upon: JXR-174 Revert JXR-157 until next major version
• is caused by: JXR-157 Upgrade Velocity templating engine
• relates to: JXR-169 Use of deprecated velocity configuration keys