search

dukecon / dukecon_server

MIT License
12 stars 6 forks source link

Update dependency pl.project13.maven:git-commit-id-plugin to v4.9.10 #172

Open renovate[bot] opened 3 years ago

renovate[bot] commented 3 years ago

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
pl.project13.maven:git-commit-id-plugin (source) 4.0.3 -> 4.9.10 age adoption passing confidence

⚠ Dependency Lookup Warnings ⚠

Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.

Release Notes

git-commit-id/git-commit-id-maven-plugin ### [`v4.9.10`](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/releases/tag/v4.9.10): Version 4.9.10 (The continued relocation saga) [Compare Source](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/compare/v4.9.9...v4.9.10) Where should I start....this release should not exists. Ideally the entire 4.9.9 "relocation" release was just intended to inform that the plugin moved to a new artifactId/groupId combination. As outlined in [https://github.com/git-commit-id/git-commit-id-maven-plugin/issues/571](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/571) or https://issues.apache.org/jira/browse/MNG-7204 there seems to be a problem where Maven will not forward the correct settings when you use the old coordinates with the 4.9.9 version. Since the 4.9.9 release contains relocation information it essentially became unusable triggering this "fix". Please note that the plugin is still moving to it's new coordinates. This 4.9.10 release is just a follow up to avoid any silent configuration issues being present somewhere.... TLDR: If you can use: io.github.git-commit-id git-commit-id-maven-plugin 5.0.0 ### [`v4.9.9`](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/releases/tag/v4.9.9): Version 4.9.9 (Relocation Release) [Compare Source](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/compare/v4.0.5...v4.9.9) This is a special release and should function in the same way as v4.0.5. | :warning: WARNING | |:--------------------------------| | Based on the issue outlined in [https://github.com/git-commit-id/git-commit-id-maven-plugin/issues/571](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/571) it is discouraged to use the old coordinates, since the plugin configuration might not be correctly applied to the plugin. Feel free to follow https://issues.apache.org/jira/browse/MNG-7204 for further informations. | Initially this release was just intended to inform that the plugin moved to a new artifactId/groupId combination, but to avoid having published a release that might be considered broken I decided to just "fix" it. Currently the 4.9.9 release works only when using the new coordinates ```xml io.github.git-commit-id git-commit-id-maven-plugin 4.9.9 ``` ### [`v4.0.5`](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/releases/tag/v4.0.5): Version 4.0.5 [Compare Source](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/compare/v4.0.4...v4.0.5) Version 4.0.5 is finally there and includes various [bug-fixes and improvements](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues?q=milestone%3A4.0.5\&closed=1) :-) #### New Features / Bug-Fixes: The main key-aspects that have been improved or being worked on are the following: - [#​547](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/547) / [#​540](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/540): add org.eclipse.jgit:org.eclipse.jgit.ssh.jsch as dependency - [#​548](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/548) / [#​549](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/549): Plugin breaks if git config log.showSignature is 'true' - [#​556](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/556): update dependencies #### 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 4.0.5 ``` #### 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.com/ktoso/maven-git-commit-id-plugin/issues/279#issuecomment-301284022](https://togithub.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 [https://github.com/git-commit-id/maven-git-commit-id-plugin/issues/287](https://togithub.com/git-commit-id/maven-git-commit-id-plugin/issues/287) or [https://github.com/git-commit-id/maven-git-commit-id-plugin/issues/413#issuecomment-487952607](https://togithub.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://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues) ### [`v4.0.4`](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/releases/tag/v4.0.4): Version 4.0.4 [Compare Source](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/compare/v4.0.3...v4.0.4) Version 4.0.4 is finally there and includes various [bug-fixes and improvements](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues?q=milestone%3A4.0.4\&closed=1) :-) #### New Features / Bug-Fixes: The main key-aspects that have been improved or being worked on are the following: - [#​531](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/531) / [#​532](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/532): fix a `NullPointerException` when `session.getProjectDependencyGraph()` might be `null` when running the plugin from eclipse - [#​523](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/523) / [#​534](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/534): Avoid illegal reflective access warning in JDK11 - [#​539](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/539): Support Bitbucket Pipelines CI for build number and branch - [#​544](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/544): add support for author and commiter times (properties will be exposed as `git.commit.author.time`, `git.commit.committer.time`) - [#​529](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues/529): update dependencies #### 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 4.0.4 ``` #### 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.com/ktoso/maven-git-commit-id-plugin/issues/279#issuecomment-301284022](https://togithub.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 [https://github.com/git-commit-id/maven-git-commit-id-plugin/issues/287](https://togithub.com/git-commit-id/maven-git-commit-id-plugin/issues/287) or [https://github.com/git-commit-id/maven-git-commit-id-plugin/issues/413#issuecomment-487952607](https://togithub.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://togithub.com/git-commit-id/git-commit-id-maven-plugin/issues)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

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

This PR has been generated by Mend Renovate. View repository job log here.

renovate[bot] commented 1 year ago

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.