MLG-Fortress / CustomItemRegistry

Create your own custom items and recipes, all in-game or via configuration files!
https://dev.bukkit.org/projects/customitemrecipes
1 stars 2 forks source link

Bump git-commit-id-plugin from 2.2.6 to 3.0.0 #5

Closed dependabot-preview[bot] closed 5 years ago

dependabot-preview[bot] commented 5 years ago

Bumps git-commit-id-plugin from 2.2.6 to 3.0.0.

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.0 is finally there and includes various [bug-fixes and improvements](https://github.com/ktoso/maven-git-commit-id-plugin/issues?q=milestone%3A3.0.0&closed=1) :-) > > ## New Features / Bug-Fixes: > The main key-aspects that have been improved or being worked on are the following: > * **Java 1.7 is no longer supported** with this version and at least **Java 8 is required** - [#346](https://github-redirect.dependabot.com/git-commit-id/maven-git-commit-id-plugin/issues/346) > * Introduced a more reliable way to deal with incremental builds for eclipse IDE - [#385](https://github-redirect.dependabot.com/git-commit-id/maven-git-commit-id-plugin/issues/385) / [#366](https://github-redirect.dependabot.com/git-commit-id/maven-git-commit-id-plugin/issues/366) / [#269](https://github-redirect.dependabot.com/git-commit-id/maven-git-commit-id-plugin/issues/269) > * Added a new property for setting if branch name should be taken from build environment or not (e.g. set ``false``). This behaviour might be useful in combination with the JGitflow maven plugin [#393](https://github-redirect.dependabot.com/git-commit-id/maven-git-commit-id-plugin/issues/393). > * Moved the project to a new `git-commit-id` organization account [#384](https://github-redirect.dependabot.com/git-commit-id/maven-git-commit-id-plugin/issues/384) > * Fixed a problem where the plugin hangs on windows under certain conditions and when there are too many changes in the git-repo [#396](https://github-redirect.dependabot.com/git-commit-id/maven-git-commit-id-plugin/issues/396) / [#336](https://github-redirect.dependabot.com/git-commit-id/maven-git-commit-id-plugin/issues/336) > * Allow the value of an replacementProperty to be empty [#400](https://github-redirect.dependabot.com/git-commit-id/maven-git-commit-id-plugin/issues/400) / [#389](https://github-redirect.dependabot.com/git-commit-id/maven-git-commit-id-plugin/issues/389) > * Introduced the new properties `git.local.branch.ahead` and `git.local.branch.behind` that provide some information if the local branch is either ahead or behind the remote. **Note** that using this property will perform a `git fetch` operation and **may have a performance impact on the overall execution of the plugin**. [#395](https://github-redirect.dependabot.com/git-commit-id/maven-git-commit-id-plugin/issues/395) > * Instead of determine all properties and then exclude properties, 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)). For a detailed performance comparison refer to the [latest benchmark](https://github-redirect.dependabot.com/git-commit-id/maven-git-commit-id-plugin/issues/408#issuecomment-487631736). **Note**: For users who want to avoid the the `git fetch` operation performed when gathering the properties `git.local.branch.ahead` and `git.local.branch.behind` simply exclude those to avoid that step: > ```xml > > ^git.local.branch.*$ > > ``` > * Cleanup readme & Introduce coveralls [#380](https://github-redirect.dependabot.com/git-commit-id/maven-git-commit-id-plugin/issues/380) / [#401](https://github-redirect.dependabot.com/git-commit-id/maven-git-commit-id-plugin/issues/401) / [#405](https://github-redirect.dependabot.com/git-commit-id/maven-git-commit-id-plugin/issues/405) > * The plugin tried to extract the Bamboo build variables with the wrong case [#410](https://github-redirect.dependabot.com/git-commit-id/maven-git-commit-id-plugin/issues/410) > * Setting `evaluateOnCommit` to anything besides the default `HEAD` resulted only in the commit-id. in case users want to `evaluateOnCommit` on any commit or branch that is not the default `HEAD`, please be advised that this plugin will run `git branch --points-at` that may or may not result in a `git.branch` property that has multiple branches that are comma separated. If `evaluateOnCommit` is kept as the default `HEAD` the `git.branch` property still may fallback to the commit-id. [#403](https://github-redirect.dependabot.com/git-commit-id/maven-git-commit-id-plugin/issues/403) > * Have travis finally automatically deploy the snapshot version of the plugin [#344](https://github-redirect.dependabot.com/git-commit-id/maven-git-commit-id-plugin/issues/344) (see below how to get it) > * Setting `injectAllReactorProjects` to true for multi-modules project now stores the computed properties in the project context. If the properties are present in the project context this plugin will essentially reuse those properties from a previously computed version (kudus to https://github-redirect.dependabot.com/git-commit-id/maven-git-commit-id-plugin/pull/411, implemented in https://github-redirect.dependabot.com/git-commit-id/maven-git-commit-id-plugin/pull/414) > > > ## 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.0 > > ``` > > ## 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 > ... (truncated)
Commits - [`9d0ba6d`](https://github.com/git-commit-id/maven-git-commit-id-plugin/commit/9d0ba6dcfbaefa1414d016d9df86f3c627f643b8) [maven-release-plugin] prepare release v3.0.0 - [`ff72bb2`](https://github.com/git-commit-id/maven-git-commit-id-plugin/commit/ff72bb21febd8ad762b936e93d933cf07cbfb995) Merge pull request [#416](https://github-redirect.dependabot.com/git-commit-id/maven-git-commit-id-plugin/issues/416) from TheSnoozer/skip-git-invocation-correctly - [`0c89d09`](https://github.com/git-commit-id/maven-git-commit-id-plugin/commit/0c89d09807d8f3bdeac7856a1ae1991c9de89fe0) use a simlar cache concept for gathering the BuildHostData since this operati... - [`8b0bb77`](https://github.com/git-commit-id/maven-git-commit-id-plugin/commit/8b0bb77ccbc95805f04e560e5d03eebbe06a8429) https://github-redirect.dependabot.com/git-commit-id/maven-git-commit-id-plugin/pull/411#discussi... - [`9821efc`](https://github.com/git-commit-id/maven-git-commit-id-plugin/commit/9821efca95152acc4d54b619e122eac25d7628fe) Merge pull request [#414](https://github-redirect.dependabot.com/git-commit-id/maven-git-commit-id-plugin/issues/414) from TheSnoozer/minor-updates - [`9582d7c`](https://github.com/git-commit-id/maven-git-commit-id-plugin/commit/9582d7c6766e73575e4700d4f08894184990dfb5) update org.mockito:mockito-core (test) from 2.23.4 to 2.27.0 - [`c55210d`](https://github.com/git-commit-id/maven-git-commit-id-plugin/commit/c55210d96123b43bb91b2759191507e6bf32b522) update org.codehaus.plexus:plexus-utils (test) from 3.1.1 to 3.2.0 - [`c2e8244`](https://github.com/git-commit-id/maven-git-commit-id-plugin/commit/c2e8244b747934ff89b06e28d8448e05df40f571) update org.apache.httpcomponents:httpclient from 4.5.6 to 4.5.8 - [`ff82250`](https://github.com/git-commit-id/maven-git-commit-id-plugin/commit/ff82250912f0e46a9ea691472cc60cfdbd087187) update com.google.guava:guava from 27.0.1-jre to 27.1-jre - [`dd128c0`](https://github.com/git-commit-id/maven-git-commit-id-plugin/commit/dd128c06929b5a6300a87f04bc33b996c9b91779) avoid java.io.IOException: Could not delete file /tmp/junit387495489739528804... - Additional commits viewable in [compare view](https://github.com/git-commit-id/maven-git-commit-id-plugin/compare/v2.2.6...v3.0.0)


Dependabot compatibility score

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 ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major 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.