hawk9821 opened a new pull request, #28:
URL: https://github.com/apache/seatunnel-shade/pull/28

   ## Purpose
   
   
   - Introduce the Maven `${revision}` property so the project version is 
managed
     at a single point in the root `pom.xml`, removing the need to bump 
`<version>`
     in 15 POM files for every release (works with `maven-release-plugin`'s
     `autoVersionSubmodules=true`).
   - Bump the development version to `3.0.1-SNAPSHOT`.
   - Fix a `maven-release-plugin` SCM provider version conflict that breaks
     `release:prepare` / `release:perform` (see "Why the jgit version bump"
     below), by aligning `maven-scm-provider-jgit` to `2.0.0` and pinning
     `maven-release-plugin` to `3.0.1`.
   
   ## Why the `maven-scm-provider-jgit` version bump (1.9.5 → 2.0.0)
   
   `maven-release-plugin` drives the Git operations during a release
   (tag / commit / push) through an SCM provider. This project uses the **JGit**
   provider (pure-Java, no native git client required), declared as a 
dependency of
   the release plugin.
   
   - `maven-release-plugin` `3.0.1` depends on the **maven-scm 2.0.0** API line.
   - The project previously overrode the provider version via the property
     `maven-scm-provider-jgit.version = 1.9.5`, which belongs to the older
     **maven-scm 1.9.x** API line.
   
   This mismatch puts two incompatible SCM API versions on the classpath at 
release
   time: the JGit provider built against scm-api 1.9.x, and the release plugin
   loading scm-api 2.0.0. As a result, `release:prepare` fails during the SCM
   step with `NoSuchMethodError` / `NoClassDefFoundError` / 
`AbstractMethodError`.
   
   Bumping `maven-scm-provider-jgit` to `2.0.0` aligns the provider with the
   maven-scm 2.0.0 API that `maven-release-plugin` `3.0.1` uses, eliminating the
   conflict. Pinning the plugin to `3.0.1` keeps the combination reproducible.
   
   
   ## Verification
   
   - `mvn -B clean install -DskipTests` builds all 14 modules at 
`3.1.0-SNAPSHOT`.
   - `mvn release:prepare -DdryRun=true` completes without the previous SCM 
provider (jgit) version conflict
     (`NoSuchMethodError` / `NoClassDefFoundError`).
   - `mvn spotless:check` passes (no formatting / license-header issues 
introduced).
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to