Hi,
I'm continuing the release process for Ratis 3.2.2 following up on the two
commits from yesterday. During the process, I encountered two issues:
1. ratis-bom module fails to deploy due to missing distributionManagement
configuration
This has been fixed in https://github.com/apache/ratis/pull/1371
2. artifact:compare fails with version mismatch error during 3-publish-mvn step
The error message is as follows:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-artifact-plugin:3.5.0:compare
(default-cli) on project ratis-thirdparty-mvn: The file
'/Users/xytan/.m2/repository/org/apache/ratis/rat
is-thirdparty-mvn/3.2.2-rc1/ratis-thirdparty-mvn-3.2.2-rc1.pom' differs from
the POM file in the current
project. The version in the file is '3.2.2-rc1' but expected '3.2.2'
I'm not sure about the root cause. It seems like the artifact:compare
plugin is comparing against a cached version in the local Maven repository.
Has anyone encountered this issue before? Any suggestions would be
appreciated.
Best
------------
Xinyu Tan
On 2026/03/08 14:15:13 Attila Doroszlai wrote:
> Hi Xinyu,
>
> Thanks for working on the release.
>
> > - Why was ratis-bom designed not to inherit from the parent POM?
>
> If ratis-bom inherited Ratis root POM (ratis), downstream project
> (e.g. Ozone) would unexpectedly get all dependency definitions (e.g.
> slf4j-simple) from Ratis, not only Ratis module definitions. See PR
> discussion [1] for slightly more details.
>
> > - What is the recommended way to keep ratis-bom version in sync during
> > releases?
>
> We can enable processAllModules [2] for versions:set. Created
> RATIS-2425 to fix the bug.
>
> -Attila
>
> [1] https://github.com/apache/ratis/pull/1335#discussion_r2709910877
> [2]
> https://www.mojohaus.org/versions/versions-maven-plugin/set-mojo.html#processAllModules
>
