Add support for per-module versions to core by mharriger · Pull Request #247

Add support for per-module versions to core by mharriger · Pull Request #247 · git-commit-id/git-commit-id-plugin-core

marked this pull request as ready for review

July 28, 2025 16:55

…ule basedir is git repo root.

TheSnoozer added a commit that referenced this pull request

Mar 28, 2026

TheSnoozer added a commit to git-commit-id/git-commit-id-maven-plugin that referenced this pull request

Mar 29, 2026

github-merge-queue bot pushed a commit to camunda/camunda that referenced this pull request

Mar 30, 2026

…lugin to v9.1.0 (main) (#49972)

This PR contains the following updates:

| Package | Change |
[Age](https://docs.renovatebot.com/merge-confidence/) |
[Confidence](https://docs.renovatebot.com/merge-confidence/) |
|---|---|---|---|
|
[io.github.git-commit-id:git-commit-id-maven-plugin](https://redirect.github.com/git-commit-id/git-commit-id-maven-plugin)
| `9.0.2` → `9.1.0` |
![age](https://developer.mend.io/api/mc/badges/age/maven/io.github.git-commit-id:git-commit-id-maven-plugin/9.1.0?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/maven/io.github.git-commit-id:git-commit-id-maven-plugin/9.0.2/9.1.0?slim=true)
|

---

> [!WARNING]
> Some dependencies could not be looked up. Check the [Dependency
Dashboard](../issues/12605) for more information.

---

### Release Notes

<details>
<summary>git-commit-id/git-commit-id-maven-plugin
(io.github.git-commit-id:git-commit-id-maven-plugin)</summary>

###
[`v9.1.0`](https://redirect.github.com/git-commit-id/git-commit-id-maven-plugin/releases/tag/v9.1.0):
Version 9.1.0

[Compare
Source](https://redirect.github.com/git-commit-id/git-commit-id-maven-plugin/compare/v9.0.2...v9.1.0)

Version 9.1.0 is finally there and includes various [bug-fixes and
improvements](https://redirect.github.com/git-commit-id/git-commit-id-maven-plugin/issues?q=milestone%3A9.1.0\&closed=1)
:-)

#### New Features / Bug-Fixes:

The main key-aspects that have been improved or being worked on are the
following:

-
[git-commit-id/git-commit-id-plugin-core#247](https://redirect.github.com/git-commit-id/git-commit-id-plugin-core/pull/247)
/
[#&#8203;136](https://redirect.github.com/git-commit-id/git-commit-id-maven-plugin/issues/136)
/
[#&#8203;535](https://redirect.github.com/git-commit-id/git-commit-id-maven-plugin/pull/535):
Add support for perModuleVersions (thanks
[@&#8203;mharriger](https://redirect.github.com/mharriger))
- Extended testing support to Java 24, 25, and 26
- Migrated from oss-parent to central-publishing-maven-plugin for
deployment

* bump several plugins
- bump `io.github.git-commit-id:git-commit-id-plugin-core` from `6.0.0`
to `6.1.5`
- bump `org.eclipse.jgit:org.eclipse.jgit` from `6.10.0.202406032230-r`
to `6.10.1.202505221210-r`
- bump `org.eclipse.jgit:org.eclipse.jgit.ssh.jsch` from
`6.10.0.202406032230-r` to `6.10.1.202505221210-r`
    - bump `joda-time:joda-time` from `2.14.0` to `2.14.1`
    - bump `org.yaml:snakeyaml` from `2.4` to `2.6`
- Full list:
<https://github.com/git-commit-id/git-commit-id-plugin-core/releases/tag/v6.1.5>
  - bump `commons-io:commons-io` from `2.19.0` to `2.21.0` (scope test)
  - bump `org.junit.jupiter:*` from `5.12.2` to `5.13.4` (scope test)
- bump `org.mockito:mockito-core` from `5.18.0` to `5.23.0` (scope test)
- bump `org.assertj:assertj-core` from `3.27.3` to `3.27.7` (scope test)
* bump several maven plugins
- bump `org.apache.maven.plugins:maven-antrun-plugin` from `3.1.0` to
`3.2.0`
- bump `org.apache.maven.plugins:maven-assembly-plugin` from `3.7.1` to
`3.8.0`
- bump `org.apache.maven.plugins:maven-clean-plugin` from `3.4.1` to
`3.5.0`
- bump `org.apache.maven.plugins:maven-compiler-plugin` from `3.14.0` to
`3.15.0`
- bump `org.apache.maven.plugins:maven-dependency-plugin` from `3.8.1`
to `3.10.0`
- bump `org.apache.maven.plugins:maven-enforcer-plugin` from `3.5.0` to
`3.6.2`
- bump `org.apache.maven.plugins:maven-gpg-plugin` from `3.2.7` to
`3.2.8`
- bump `org.apache.maven.plugins:maven-jar-plugin` from `3.4.2` to
`3.5.0`
- bump `org.apache.maven.plugins:maven-javadoc-plugin` from `3.11.2` to
`3.12.0`
- bump `org.apache.maven.plugins:maven-plugin-plugin` from `3.15.1` to
`3.15.2`
- bump `org.apache.maven.plugins:maven-release-plugin` from `3.1.1` to
`3.3.1`
- bump `org.apache.maven.plugins:maven-resources-plugin` from `3.3.1` to
`3.5.0`
- bump `org.apache.maven.plugins:maven-source-plugin` from `3.3.1` to
`3.4.0`
- bump `org.apache.maven.plugins:maven-surefire-plugin` from `3.5.3` to
`3.5.5`
- bump `org.codehaus.mojo:versions-maven-plugin` from `2.18.0` to
`2.21.0`
  - bump `org.codehaus.mojo:exec-maven-plugin` from `3.5.0` to `3.6.3`
  - bump `org.jacoco:jacoco-maven-plugin` from `0.8.13` to `0.8.14`
- bump `org.apache.maven.plugin-tools:maven-plugin-annotations` from
`3.15.1` to `3.15.2`

#### Getting the latest release

The plugin is available from Maven Central ([see
here](https://search.maven.org/search?q=g:io.github.git-commit-id%20AND%20a:git-commit-id-maven-plugin)),
so you don't have to configure any additional repositories to use this
plugin. All you need to do is to configure it inside your project as
dependency:

```xml
<dependency>
    <groupId>io.github.git-commit-id</groupId>
    <artifactId>git-commit-id-maven-plugin</artifactId>
    <version>9.1.0</version>
</dependency>
```

#### Getting the latest snapshot (build automatically)

If you can't wait for the next release, you can also get the latest
snapshot version from sonatype, that is being deployed automatically by
github actions:

```xml
<pluginRepositories>
    <pluginRepository>
        <id>sonatype-snapshots</id>
        <name>Sonatype Snapshots</name>
         <url>https://s01.oss.sonatype.org/content/repositories/snapshots/</url>
    </pluginRepository>
</pluginRepositories>
```

Even though the github actions will only deploy a new snapshot once all
tests have finished, it is recommended to rely on the released and more
stable version.

#### Known Issues / Limitations:

- This plugin is unfortunately not working with Heroku which is due to
the fact how Heroku works. In summary Heroku does not copy over the
.git-repository but in order to determine the git properties this plugin
relies on the fact that it has access to the git-repository. A somewhat
*workaround* to get some information is outlined in
[git-commit-id/git-commit-id-maven-plugin#279
(comment)](https://redirect.github.com/ktoso/maven-git-commit-id-plugin/issues/279#issuecomment-301284022)
- Using maven's plugin prefix resolution (e.g. `mvn
com.test.plugins:myPlugin:myMojo`) might result in unresolved properties
even with `<injectAllReactorProjects>true</injectAllReactorProjects>`.
Please refer to
[git-commit-id/git-commit-id-maven-plugin#287](https://redirect.github.com/git-commit-id/maven-git-commit-id-plugin/issues/287)
or [git-commit-id/git-commit-id-maven-plugin#413
(comment)](https://redirect.github.com/git-commit-id/maven-git-commit-id-plugin/issues/413#issuecomment-487952607)
for details and potential workarounds

#### Reporting Problems

If you find any problem with this plugin, feel free to report it
[here](https://redirect.github.com/git-commit-id/git-commit-id-maven-plugin/issues)

**Full Changelog**:
<git-commit-id/git-commit-id-maven-plugin@v9.0.2...v9.1.0>

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At 08:00 PM through 11:59 PM and 12:00
AM through 08:59 AM, Monday through Friday ( * 20-23,0-8 * * 1-5 ), Only
on Sunday and Saturday ( * * * * 0,6 ) (UTC), Automerge - At any time
(no schedule defined).

🚦 **Automerge**: Enabled.

♻ **Rebasing**: Whenever PR is behind base branch, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/camunda/camunda).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My45NC4xIiwidXBkYXRlZEluVmVyIjoiNDMuOTQuMSIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiYXJlYS9iYWNrZW5kIiwiYXV0b21lcmdlIiwiZGVwZW5kZW5jaWVzIl19-->

github-merge-queue bot pushed a commit to camunda/camunda that referenced this pull request

Mar 30, 2026

…lugin to v9.1.0 (main) (#49971)

This PR contains the following updates:

| Package | Change |
[Age](https://docs.renovatebot.com/merge-confidence/) |
[Confidence](https://docs.renovatebot.com/merge-confidence/) |
|---|---|---|---|
|
[io.github.git-commit-id:git-commit-id-maven-plugin](https://redirect.github.com/git-commit-id/git-commit-id-maven-plugin)
| `9.0.2` → `9.1.0` |
![age](https://developer.mend.io/api/mc/badges/age/maven/io.github.git-commit-id:git-commit-id-maven-plugin/9.1.0?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/maven/io.github.git-commit-id:git-commit-id-maven-plugin/9.0.2/9.1.0?slim=true)
|

---

> [!WARNING]
> Some dependencies could not be looked up. Check the [Dependency
Dashboard](../issues/12605) for more information.

---

### Release Notes

<details>
<summary>git-commit-id/git-commit-id-maven-plugin
(io.github.git-commit-id:git-commit-id-maven-plugin)</summary>

###
[`v9.1.0`](https://redirect.github.com/git-commit-id/git-commit-id-maven-plugin/releases/tag/v9.1.0):
Version 9.1.0

[Compare
Source](https://redirect.github.com/git-commit-id/git-commit-id-maven-plugin/compare/v9.0.2...v9.1.0)

Version 9.1.0 is finally there and includes various [bug-fixes and
improvements](https://redirect.github.com/git-commit-id/git-commit-id-maven-plugin/issues?q=milestone%3A9.1.0\&closed=1)
:-)

#### New Features / Bug-Fixes:

The main key-aspects that have been improved or being worked on are the
following:

-
[git-commit-id/git-commit-id-plugin-core#247](https://redirect.github.com/git-commit-id/git-commit-id-plugin-core/pull/247)
/
[#&#8203;136](https://redirect.github.com/git-commit-id/git-commit-id-maven-plugin/issues/136)
/
[#&#8203;535](https://redirect.github.com/git-commit-id/git-commit-id-maven-plugin/pull/535):
Add support for perModuleVersions (thanks
[@&#8203;mharriger](https://redirect.github.com/mharriger))
- Extended testing support to Java 24, 25, and 26
- Migrated from oss-parent to central-publishing-maven-plugin for
deployment

* bump several plugins
- bump `io.github.git-commit-id:git-commit-id-plugin-core` from `6.0.0`
to `6.1.5`
- bump `org.eclipse.jgit:org.eclipse.jgit` from `6.10.0.202406032230-r`
to `6.10.1.202505221210-r`
- bump `org.eclipse.jgit:org.eclipse.jgit.ssh.jsch` from
`6.10.0.202406032230-r` to `6.10.1.202505221210-r`
    - bump `joda-time:joda-time` from `2.14.0` to `2.14.1`
    - bump `org.yaml:snakeyaml` from `2.4` to `2.6`
- Full list:
<https://github.com/git-commit-id/git-commit-id-plugin-core/releases/tag/v6.1.5>
  - bump `commons-io:commons-io` from `2.19.0` to `2.21.0` (scope test)
  - bump `org.junit.jupiter:*` from `5.12.2` to `5.13.4` (scope test)
- bump `org.mockito:mockito-core` from `5.18.0` to `5.23.0` (scope test)
- bump `org.assertj:assertj-core` from `3.27.3` to `3.27.7` (scope test)
* bump several maven plugins
- bump `org.apache.maven.plugins:maven-antrun-plugin` from `3.1.0` to
`3.2.0`
- bump `org.apache.maven.plugins:maven-assembly-plugin` from `3.7.1` to
`3.8.0`
- bump `org.apache.maven.plugins:maven-clean-plugin` from `3.4.1` to
`3.5.0`
- bump `org.apache.maven.plugins:maven-compiler-plugin` from `3.14.0` to
`3.15.0`
- bump `org.apache.maven.plugins:maven-dependency-plugin` from `3.8.1`
to `3.10.0`
- bump `org.apache.maven.plugins:maven-enforcer-plugin` from `3.5.0` to
`3.6.2`
- bump `org.apache.maven.plugins:maven-gpg-plugin` from `3.2.7` to
`3.2.8`
- bump `org.apache.maven.plugins:maven-jar-plugin` from `3.4.2` to
`3.5.0`
- bump `org.apache.maven.plugins:maven-javadoc-plugin` from `3.11.2` to
`3.12.0`
- bump `org.apache.maven.plugins:maven-plugin-plugin` from `3.15.1` to
`3.15.2`
- bump `org.apache.maven.plugins:maven-release-plugin` from `3.1.1` to
`3.3.1`
- bump `org.apache.maven.plugins:maven-resources-plugin` from `3.3.1` to
`3.5.0`
- bump `org.apache.maven.plugins:maven-source-plugin` from `3.3.1` to
`3.4.0`
- bump `org.apache.maven.plugins:maven-surefire-plugin` from `3.5.3` to
`3.5.5`
- bump `org.codehaus.mojo:versions-maven-plugin` from `2.18.0` to
`2.21.0`
  - bump `org.codehaus.mojo:exec-maven-plugin` from `3.5.0` to `3.6.3`
  - bump `org.jacoco:jacoco-maven-plugin` from `0.8.13` to `0.8.14`
- bump `org.apache.maven.plugin-tools:maven-plugin-annotations` from
`3.15.1` to `3.15.2`

#### Getting the latest release

The plugin is available from Maven Central ([see
here](https://search.maven.org/search?q=g:io.github.git-commit-id%20AND%20a:git-commit-id-maven-plugin)),
so you don't have to configure any additional repositories to use this
plugin. All you need to do is to configure it inside your project as
dependency:

```xml
<dependency>
    <groupId>io.github.git-commit-id</groupId>
    <artifactId>git-commit-id-maven-plugin</artifactId>
    <version>9.1.0</version>
</dependency>
```

#### Getting the latest snapshot (build automatically)

If you can't wait for the next release, you can also get the latest
snapshot version from sonatype, that is being deployed automatically by
github actions:

```xml
<pluginRepositories>
    <pluginRepository>
        <id>sonatype-snapshots</id>
        <name>Sonatype Snapshots</name>
         <url>https://s01.oss.sonatype.org/content/repositories/snapshots/</url>
    </pluginRepository>
</pluginRepositories>
```

Even though the github actions will only deploy a new snapshot once all
tests have finished, it is recommended to rely on the released and more
stable version.

#### Known Issues / Limitations:

- This plugin is unfortunately not working with Heroku which is due to
the fact how Heroku works. In summary Heroku does not copy over the
.git-repository but in order to determine the git properties this plugin
relies on the fact that it has access to the git-repository. A somewhat
*workaround* to get some information is outlined in
[git-commit-id/git-commit-id-maven-plugin#279
(comment)](https://redirect.github.com/ktoso/maven-git-commit-id-plugin/issues/279#issuecomment-301284022)
- Using maven's plugin prefix resolution (e.g. `mvn
com.test.plugins:myPlugin:myMojo`) might result in unresolved properties
even with `<injectAllReactorProjects>true</injectAllReactorProjects>`.
Please refer to
[git-commit-id/git-commit-id-maven-plugin#287](https://redirect.github.com/git-commit-id/maven-git-commit-id-plugin/issues/287)
or [git-commit-id/git-commit-id-maven-plugin#413
(comment)](https://redirect.github.com/git-commit-id/maven-git-commit-id-plugin/issues/413#issuecomment-487952607)
for details and potential workarounds

#### Reporting Problems

If you find any problem with this plugin, feel free to report it
[here](https://redirect.github.com/git-commit-id/git-commit-id-maven-plugin/issues)

**Full Changelog**:
<git-commit-id/git-commit-id-maven-plugin@v9.0.2...v9.1.0>

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At 08:00 PM through 11:59 PM and 12:00
AM through 08:59 AM, Monday through Friday ( * 20-23,0-8 * * 1-5 ), Only
on Sunday and Saturday ( * * * * 0,6 ) (UTC), Automerge - At any time
(no schedule defined).

🚦 **Automerge**: Enabled.

♻ **Rebasing**: Whenever PR is behind base branch, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/camunda/camunda).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My45NC4xIiwidXBkYXRlZEluVmVyIjoiNDMuOTQuMSIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiYXJlYS9iYWNrZW5kIiwiYXV0b21lcmdlIiwiZGVwZW5kZW5jaWVzIl19-->