Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump duplicate-finder-maven-plugin from 1.3.0 to 1.5.0 #532

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

dependabot-preview[bot]
Copy link
Contributor

Bumps duplicate-finder-maven-plugin from 1.3.0 to 1.5.0.

Release notes

Sourced from duplicate-finder-maven-plugin's releases.

Version 1.5.0

This version is functionally (almost) unchanged from 1.4.0 except that it is using a newer build system and is built with the JDK11 compiler for JDK8 target.

The only substantial change over 1.4.0 is an additional ignored pattern (changelog.txt, #44).

added

changed

  • use github actions for CI, remove travis
  • use maven wrapper
  • build with JDK9+ only, still support JDK8 as runtime
    • CI build with JDK 11, 14
    • CI run integration tests on JDK 8, 11, 14

Version 1.4.0

added

changed

  • Build with basepom 30
  • use slf4j 1.7.28 (from 1.7.21)
  • update plugin plugin to 3.6.0 (from 3.4)
  • update groovy to 3.0.0-beta-3 (from 2.4.12)
  • changed Travis Build to use OpenJDK 8 and 11
  • Clarify much more what is a resource and what is considered a class. This changes a lot of things that used to be matched as classes to be matched as resources. Especially all path elements (directories, jar file folders etc.) now must match the Java identifier specification. This e.g. rejects classes in Multi-release jars that are located in META-INF/versions/<version> because META-INF or the version number are not valid Java identifiers. An exception is made for package-info and module-info class files, whose names are not valid Java identifiers but are still loaded as classes from the class path.

deprecated

removed

fixed

  • Do not crash if more than one artifact reference points to the same file (#25, #29, #35)
  • Fix Java 9+ module-version problems with multi-release jars (#31, #33)
  • Triage and fix outdated bugs (#23, #20, #17)

security

  • Update Guava dependency to 28.1-jre (#36)
  • Use plexus 2.0.0 to build (#37)
Changelog

Sourced from duplicate-finder-maven-plugin's changelog.

1.5.0 - 2020-09-13

This version is functionally (almost) unchanged from 1.4.0 except that it is using a newer build system and is built with the JDK11 compiler for JDK8 target.

The only substantial change over 1.4.0 is an additional ignored pattern (changelog.txt, #44).

added

changed

  • use github actions for CI, remove travis
  • use maven wrapper
  • build with JDK9+ only, still support JDK8 as runtime
    • CI build with JDK 11, 14
    • CI run integration tests on JDK 8, 11, 14

1.4.0 - 2019-10-27

changed

  • Build with basepom 30
  • use slf4j 1.7.28 (from 1.7.21)
  • update plugin plugin to 3.6.0 (from 3.4)
  • update groovy to 3.0.0-beta-3 (from 2.4.12)
  • changed Travis Build to use OpenJDK 8 and 11
  • Clarify much more what is a resource and what is considered a class. This changes a lot of things that used to be matched as classes to be matched as resources. Especially all path elements (directories, jar file folders etc.) now must match the Java identifier specification. This e.g. rejects classes in Multi-release jars that are located in META-INF/versions/<version> because META-INF or the version number are not valid Java identifiers. An exception is made for package-info and module-info class files, whose names are not valid Java identifiers but are still loaded as classes from the class path.

fixed

  • Do not crash if more than one artifact reference points to the same file (#25, #29, #35)
  • Fix Java 9+ module-version problems with multi-release jars (#31, #33)
  • Triage and fix outdated bugs (#23, #20, #17)

security

  • Update Guava dependency to 28.1-jre (#36)
  • Use plexus 2.0.0 to build (#37)
Commits
  • 6fe37ae [maven-release-plugin] prepare release duplicate-finder-maven-plugin-1.5.0
  • 59b3c8d bump to released basepom
  • 91e4867 Update CHANGES.md
  • 33132e9 Update CHANGES.md
  • 3ce74b5 Make changelog.txt a default ignored resource (#44)
  • 2e3a7c5 Update README.md
  • 991d924 update changelog for 1.4.0
  • 6cf40f1 remove conditional, running Java 14 tests on 11 code is fine.
  • d993eb0 Update build versions and enforce build profiles
  • f01859e Update README.md
  • Additional commits viewable in compare view

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 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:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Automerge options (never/patch/minor, and dev/runtime dependencies)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

@dependabot-preview
Copy link
Contributor Author

One of your CI runs failed on this pull request, so Dependabot won't merge it.

Dependabot will still automatically merge this pull request if you amend it and your tests pass.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants