Bump org.jenkins-ci.plugins:plugin from 5.9 to 5.12#175
Conversation
dependabot
Bot
added
dependencies
gounthar
left a comment
gounthar
left a comment
There was a problem hiding this comment.
02:30:35 [ERROR] Failed to execute goal com.diffplug.spotless:spotless-maven-plugin:2.44.4:check (default) on project plot: The following files had format violations:
192
02:30:35 [ERROR] src/main/java/hudson/plugins/plot/Plot.java
193
Bumps [org.jenkins-ci.plugins:plugin](https://github.com/jenkinsci/plugin-pom) from 5.9 to 5.12. - [Release notes](https://github.com/jenkinsci/plugin-pom/releases) - [Changelog](https://github.com/jenkinsci/plugin-pom/blob/master/CHANGELOG.md) - [Commits](jenkinsci/plugin-pom@plugin-5.9...plugin-5.12) --- updated-dependencies: - dependency-name: org.jenkins-ci.plugins:plugin dependency-version: '5.12' dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/maven/org.jenkins-ci.plugins-plugin-5.12
branch
from
20b6e79 to
e98e3e2
Compare
This is another example of a spotless case that has perplexed me. The formatting does not need to be fixed on Windows by |
|
@strangelookingnerd I think that you found a solution for the spotless failures on Windows, but I don't recall the solution. Can you recall what it was? |
|
See jenkinsci/badge-plugin#251 (comment) I excluded the problematic code section using |
jenkinsci#175 intentionally disabled spotless checking so that the parent pom update could be merged. Enable spotless checking again.
* Enable spotless check #175 intentionally disabled spotless checking so that the parent pom update could be merged. Enable spotless checking again. * Skip spotless formatting in two problem areas
3 participants
Bumps org.jenkins-ci.plugins:plugin from 5.9 to 5.12.
Release notes
Sourced from org.jenkins-ci.plugins:plugin's releases.
Commits
7536338[maven-release-plugin] prepare release plugin-5.12d782fd7Bump org.jenkins-ci.tools:maven-hpi-plugin from 3.63 to 3.64 (#1128)d276b05Bump org.kohsuke:access-modifier-checker from 1.34 to 1.35 (#1127)8d81d8aBump com.infradna.tool:bridge-method-injector from 1.30 to 1.31 (#1126)54abe65Addbridge-method-injectorsupport (#1125)2c1afb0[maven-release-plugin] prepare for next development iterationbdb4b20[maven-release-plugin] prepare release plugin-5.118e2d202Add corepack support for yarn berry (#1122)defcdb9Bump org.junit:junit-bom from 5.12.1 to 5.12.2 (#1121)c4f78bcBump com.diffplug.spotless:spotless-maven-plugin from 2.44.3 to 2.44.4 (#1120)Most Recent Ignore Conditions Applied to This Pull Request
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.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)