Am 2023-02-19 um 20:59 schrieb Guillaume Nodet:
Le dim. 19 févr. 2023 à 17:18, Michael Osipov <[email protected]> a
écrit :
Am 2023-02-18 um 11:34 schrieb Michael Osipov:
Am 2023-02-15 um 21:22 schrieb Guillaume Nodet:
I've staged a release candidate for Maven Plugin Tools 3.8.0.
The goal is to provide some initial support for plugins using the maven
4
api provided by maven 4.0.0-alpha-4. The plugin can be used for both
3.x
and 4.x plugins, so there's no major version bump.
Release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317820&version=12352545
Staging repository:
https://repository.apache.org/content/repositories/maven-1875
Staging site:
https://maven.apache.org/plugin-tools-archives/plugin-tools-LATEST/
I have to remove my vote and give a clear -1:
https://issues.apache.org/jira/browse/MPLUGIN-414
I have clearly written:
This change can only happen when the entire Doxia Stack moves to
Velocity 2.3 because it would override the transitive dep of Doxia Site
Renderer.
This must be reverted.
I missed that. Could you explain why changing dependency in m-plugin-tools
would directly affect released versions of the site renderer ? Or is that
for future versions that would also upgrade to this newer m-plugin-tools ?
Here is the problem:
[INFO] --------< org.apache.maven.plugins:maven-plugin-report-plugin >---------
[INFO] Building Maven Plugin Report Plugin 3.8.1-SNAPSHOT [14/14]
[INFO] ----------------------------[ maven-plugin ]----------------------------
Downloading from apache.snapshots:
https://repository.apache.org/snapshots/org/apache/maven/plugins/maven-plugin-plugin/3.8.1-SNAPSHOT/maven-metadata.xml
Downloaded from apache.snapshots:
https://repository.apache.org/snapshots/org/apache/maven/plugins/maven-plugin-plugin/3.8.1-SNAPSHOT/maven-metadata.xml
(793 B at 3.2 kB/s)
[INFO]
[INFO] --- maven-dependency-plugin:3.4.0:tree (default-cli) @
maven-plugin-report-plugin ---
...
[INFO] +-
org.apache.maven.plugin-tools:maven-plugin-tools-generators:jar:3.8.1-SNAPSHOT:compile
[INFO] | +- org.codehaus.plexus:plexus-velocity:jar:2.0:compile
[INFO] | +- org.apache.velocity:velocity-engine-core:jar:2.3:compile
...
[INFO] +- org.apache.maven.reporting:maven-reporting-impl:jar:3.2.0:compile
[INFO] | +- org.apache.maven.shared:maven-shared-utils:jar:3.3.4:compile
[INFO] | | \- commons-io:commons-io:jar:2.6:compile
[INFO] | +- org.apache.maven.doxia:doxia-decoration-model:jar:1.11.1:compile
[INFO] | +- org.apache.maven.doxia:doxia-core:jar:1.11.1:compile
[INFO] | | \- org.apache.commons:commons-text:jar:1.3:compile
[INFO] | +- org.apache.maven.doxia:doxia-integration-tools:jar:1.11.1:compile
[INFO] | | \- org.codehaus.plexus:plexus-i18n:jar:1.0-beta-10:compile
[INFO] | \- org.apache.maven.doxia:doxia-site-renderer:jar:1.11.1:compile
[INFO] | +- org.apache.maven.doxia:doxia-skin-model:jar:1.11.1:compile
[INFO] | +- org.apache.maven.doxia:doxia-module-xhtml:jar:1.11.1:compile
[INFO] | +- org.apache.maven.doxia:doxia-module-xhtml5:jar:1.11.1:compile
[INFO] | +- org.apache.velocity:velocity:jar:1.7:compile
[INFO] | | \- commons-lang:commons-lang:jar:2.4:compile
[INFO] | +- org.apache.velocity:velocity-tools:jar:2.0:compile
...
You now have Velocity twice on the classpath. This will lead to any kind
of funny behavior, failure, etc. Doxia Sitetools 1.x isn't supported
with Velocity Engine 2.x, so aren't Velocity Tools 2.0.
Here is the exact same issue with JXR:
https://issues.apache.org/jira/browse/JXR-166. Read the other related
issues please.
M
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
