Release notes
*Sourced from [git-commit-id-plugin's releases](https://github.com/git-commit-id/maven-git-commit-id-plugin/releases).*
> Version 3.0.1 is finally there and includes various [bug-fixes and improvements](https://github.com/ktoso/maven-git-commit-id-plugin/issues?q=milestone%3A3.0.1&closed=1) :-)
>
> ## New Features / Bug-Fixes:
> The main key-aspects that have been improved or being worked on are the following:
> * Added a new setting to control if the plugin should operate in offline mode -- [#424](https://github-redirect.dependabot.com/git-commit-id/maven-git-commit-id-plugin/pull/424) (by default the plugin will assume an 'online' mode and since version 3.0 will perform a `git fetch` operation to determine the properties `git.local.branch.ahead` and `git.local.branch.behind`. If the plugin is operating in 'offline' mode both those properties will only reflect the view of the local clone and thus might be off from the actual repository. **Note** this 'offline' mode is also respected when one set's the maven "-o" offline switch).
> * Removed the `org.apache.httpcomponents:httpclient` dependency -- [#425](https://github-redirect.dependabot.com/git-commit-id/maven-git-commit-id-plugin/pull/425)
> * Since version 3.0.0 this plugin will now only ask for properties that are essential (proposal from [#185](https://github-redirect.dependabot.com/git-commit-id/maven-git-commit-id-plugin/issues/185)). With this version the same technique is now also used when retrieving `git.build.time` since the `TimeZone.getTimeZone()` may also have an impact upon performance -- https://github-redirect.dependabot.com/git-commit-id/maven-git-commit-id-plugin/pull/428.
> * Property caching now works properly for reactor builds using property caching when using `injectAllReactorProjects` -- https://github-redirect.dependabot.com/git-commit-id/maven-git-commit-id-plugin/pull/429.
>
> ## Getting the latest release
> The plugin is available from Maven Central ([see here](http://search.maven.org/#search%7Cga%7C1%7Cpl.project13)), 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
>
> pl.project13.maven
> git-commit-id-plugin
> 3.0.1
>
> ```
>
> ## 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 travis:
> ```xml
>
>
> sonatype-snapshots
> Sonatype Snapshots
> https://oss.sonatype.org/content/repositories/snapshots/
>
>
> ```
> Even though travis 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 https://github-redirect.dependabot.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 `true`. Please refer to [#287](https://github-redirect.dependabot.com/git-commit-id/maven-git-commit-id-plugin/issues/287) or https://github-redirect.dependabot.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://github.com/ktoso/maven-git-commit-id-plugin/issues)
Commits
- [`cec8487`](https://github.com/git-commit-id/maven-git-commit-id-plugin/commit/cec8487c97e0962b2ef2958b2ebff45df9088d34) [maven-release-plugin] prepare release v3.0.1
- [`8f65b32`](https://github.com/git-commit-id/maven-git-commit-id-plugin/commit/8f65b32c9ddcc8b9b98eae8c8283fccc94823a08) Merge pull request [#430](https://github-redirect.dependabot.com/git-commit-id/maven-git-commit-id-plugin/issues/430) from TheSnoozer/update-dependencies
- [`f048763`](https://github.com/git-commit-id/maven-git-commit-id-plugin/commit/f0487637eeaabfdfda2860623561312e65bdd215) update org.mockito:mockito-core (test) 2.27.0 -> 3.0.0
- [`49214f5`](https://github.com/git-commit-id/maven-git-commit-id-plugin/commit/49214f54a3b40dfa1459a4f05fba9231f36ebd1a) update org.junit.jupiter:junit-jupiter-api (test) 5.3.1 -> 5.5.1
- [`7a72dd6`](https://github.com/git-commit-id/maven-git-commit-id-plugin/commit/7a72dd611daee383dfa96c8b276efa70d21b817f) update org.eclipse.jgit:org.eclipse.jgit 5.2.0.201812061821-r -> 5.2.2.201904...
- [`c063736`](https://github.com/git-commit-id/maven-git-commit-id-plugin/commit/c06373609736bfbb3efe7347fbf50ebc412ab593) update org.codehaus.plexus:plexus-utils (test) 3.2.0 -> 3.2.1
- [`0159d85`](https://github.com/git-commit-id/maven-git-commit-id-plugin/commit/0159d85edc996eaac23cc7c8f25f665d17731bc3) update joda-time:joda-time 2.10.2 -> 2.10.3
- [`3d76bb6`](https://github.com/git-commit-id/maven-git-commit-id-plugin/commit/3d76bb643fbbd41ac61aab61521d4436e8383cc0) update com.google.guava:guava 27.1-jre -> 28.0-jre
- [`1e8dd35`](https://github.com/git-commit-id/maven-git-commit-id-plugin/commit/1e8dd352b17a17757541eb287ab4e5f38b3bc569) update com.fasterxml.jackson.core: 2.9.9 -> 2.9.9.3 (CVE-2019-14379 / CVE-201...
- [`6b5e158`](https://github.com/git-commit-id/maven-git-commit-id-plugin/commit/6b5e1582037115ca338e0319d08566be22d2a8b7) Merge pull request [#429](https://github-redirect.dependabot.com/git-commit-id/maven-git-commit-id-plugin/issues/429) from ryantse/fix-property-cache
- Additional commits viewable in [compare view](https://github.com/git-commit-id/maven-git-commit-id-plugin/compare/v3.0.0...v3.0.1)
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
If all status checks pass Dependabot will automatically merge this pull request.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
- `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language
- `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language
- `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language
- `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language
- `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme
Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com):
- Update frequency (including time of day and day of week)
- Automerge options (never/patch/minor, and dev/runtime dependencies)
- Pull request limits (per update run and/or open at any time)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)
Finally, you can contact us by mentioning @dependabot.
⚠️ Dependabot won't automerge this PR as it didn't detect CI on it ⚠️
You have automerging enabled for this repo but Dependabot didn't detect any CI statuses or checks. You can disable automerging on this repo from here.
Bumps git-commit-id-plugin from 3.0.0 to 3.0.1.
Release notes
*Sourced from [git-commit-id-plugin's releases](https://github.com/git-commit-id/maven-git-commit-id-plugin/releases).* > Version 3.0.1 is finally there and includes various [bug-fixes and improvements](https://github.com/ktoso/maven-git-commit-id-plugin/issues?q=milestone%3A3.0.1&closed=1) :-) > > ## New Features / Bug-Fixes: > The main key-aspects that have been improved or being worked on are the following: > * Added a new setting to control if the plugin should operate in offline mode -- [#424](https://github-redirect.dependabot.com/git-commit-id/maven-git-commit-id-plugin/pull/424) (by default the plugin will assume an 'online' mode and since version 3.0 will perform a `git fetch` operation to determine the properties `git.local.branch.ahead` and `git.local.branch.behind`. If the plugin is operating in 'offline' mode both those properties will only reflect the view of the local clone and thus might be off from the actual repository. **Note** this 'offline' mode is also respected when one set's the maven "-o" offline switch). > * Removed the `org.apache.httpcomponents:httpclient` dependency -- [#425](https://github-redirect.dependabot.com/git-commit-id/maven-git-commit-id-plugin/pull/425) > * Since version 3.0.0 this plugin will now only ask for properties that are essential (proposal from [#185](https://github-redirect.dependabot.com/git-commit-id/maven-git-commit-id-plugin/issues/185)). With this version the same technique is now also used when retrieving `git.build.time` since the `TimeZone.getTimeZone()` may also have an impact upon performance -- https://github-redirect.dependabot.com/git-commit-id/maven-git-commit-id-plugin/pull/428. > * Property caching now works properly for reactor builds using property caching when using `injectAllReactorProjects` -- https://github-redirect.dependabot.com/git-commit-id/maven-git-commit-id-plugin/pull/429. > > ## Getting the latest release > The plugin is available from Maven Central ([see here](http://search.maven.org/#search%7Cga%7C1%7Cpl.project13)), 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 >Commits
- [`cec8487`](https://github.com/git-commit-id/maven-git-commit-id-plugin/commit/cec8487c97e0962b2ef2958b2ebff45df9088d34) [maven-release-plugin] prepare release v3.0.1 - [`8f65b32`](https://github.com/git-commit-id/maven-git-commit-id-plugin/commit/8f65b32c9ddcc8b9b98eae8c8283fccc94823a08) Merge pull request [#430](https://github-redirect.dependabot.com/git-commit-id/maven-git-commit-id-plugin/issues/430) from TheSnoozer/update-dependencies - [`f048763`](https://github.com/git-commit-id/maven-git-commit-id-plugin/commit/f0487637eeaabfdfda2860623561312e65bdd215) update org.mockito:mockito-core (test) 2.27.0 -> 3.0.0 - [`49214f5`](https://github.com/git-commit-id/maven-git-commit-id-plugin/commit/49214f54a3b40dfa1459a4f05fba9231f36ebd1a) update org.junit.jupiter:junit-jupiter-api (test) 5.3.1 -> 5.5.1 - [`7a72dd6`](https://github.com/git-commit-id/maven-git-commit-id-plugin/commit/7a72dd611daee383dfa96c8b276efa70d21b817f) update org.eclipse.jgit:org.eclipse.jgit 5.2.0.201812061821-r -> 5.2.2.201904... - [`c063736`](https://github.com/git-commit-id/maven-git-commit-id-plugin/commit/c06373609736bfbb3efe7347fbf50ebc412ab593) update org.codehaus.plexus:plexus-utils (test) 3.2.0 -> 3.2.1 - [`0159d85`](https://github.com/git-commit-id/maven-git-commit-id-plugin/commit/0159d85edc996eaac23cc7c8f25f665d17731bc3) update joda-time:joda-time 2.10.2 -> 2.10.3 - [`3d76bb6`](https://github.com/git-commit-id/maven-git-commit-id-plugin/commit/3d76bb643fbbd41ac61aab61521d4436e8383cc0) update com.google.guava:guava 27.1-jre -> 28.0-jre - [`1e8dd35`](https://github.com/git-commit-id/maven-git-commit-id-plugin/commit/1e8dd352b17a17757541eb287ab4e5f38b3bc569) update com.fasterxml.jackson.core: 2.9.9 -> 2.9.9.3 (CVE-2019-14379 / CVE-201... - [`6b5e158`](https://github.com/git-commit-id/maven-git-commit-id-plugin/commit/6b5e1582037115ca338e0319d08566be22d2a8b7) Merge pull request [#429](https://github-redirect.dependabot.com/git-commit-id/maven-git-commit-id-plugin/issues/429) from ryantse/fix-property-cache - Additional commits viewable in [compare view](https://github.com/git-commit-id/maven-git-commit-id-plugin/compare/v3.0.0...v3.0.1)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.If all status checks pass Dependabot will automatically merge this pull request.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) Finally, you can contact us by mentioning @dependabot.
⚠️ Dependabot won't automerge this PR as it didn't detect CI on it ⚠️
You have automerging enabled for this repo but Dependabot didn't detect any CI statuses or checks. You can disable automerging on this repo from here.