search

DarkEyeDragon / RandomTeleport

Randomly teleport players to a safe location
https://ci.darkeyedragon.me/
13 stars 6 forks source link

Bump maven-artifact from 3.8.6 to 3.9.1 #293

Open dependabot[bot] opened 1 year ago

dependabot[bot] commented 1 year ago

Bumps maven-artifact from 3.8.6 to 3.9.1.

Release notes

Sourced from maven-artifact's releases.

3.9.1

Release Notes - Maven - Version 3.9.1

Overview About the Changes

Regression fixes from Maven 3.9.0. General performance and other fixes.

Potentially Breaking Core Changes (if migrating from 3.8.x)

  • The Maven Resolver transport has changed from Wagon to “native HTTP”, see Resolver Transport guide.

  • Maven 2.x was auto-injecting an ancient version of plexus-utils dependency into the plugin classpath, and Maven 3.x continued doing this to preserve backward compatibility. Starting with Maven 3.9, it does not happen anymore. This change may lead to plugin breakage. The fix for affected plugin maintainers is to explicitly declare a dependency on plexus-utils. The workaround for affected plugin users is to add this dependency to plugin dependencies until issue is fixed by the affected plugin maintainer. See MNG-6965.

  • Mojos are prevented to boostrap new instance of RepositorySystem (for example by using deprecated ServiceLocator), they should reuse RepositorySystem instance provided by Maven instead. See MNG-7471.

  • Each line in .mvn/maven.config is now interpreted as a single argument. That is, if the file contains multiple arguments, these must now be placed on separate lines, see MNG-7684.

Bug

  • [MNG-7213] - StackOverflowError when version ranges are unsolvable and graph contains a cycle
  • [MNG-7544] - MavenMetadataSource#retrieve(MetadataResolutionRequest) does not check for null when reading from project map
  • [MNG-7676] - On Maven 3.9.0+ release, sha512 hashes have "null" classifier
  • [MNG-7677] - Maven 3.9.0 is ~10% slower than 3.8.7 in large multi-module builds
  • [MNG-7679] - [REGRESSION] Build fails when executing a single mojo without a POM
  • [MNG-7685] - Unable to ignore certificate errors with v3.9.0
  • [MNG-7693] - NPE in createModelCache, modelCacheFactory is null
  • [MNG-7697] - Cannot parse POM that contains an emoji in a comment
  • [MNG-7708] - Resolver in Maven 3.9+ no longer retries on a conection failure
  • [MNG-7709] - plexus-utils upgrade changes the way configuration is parsed
  • [MNG-7710] - Upgrade plexus-utils to 3.5.1
  • [MNG-7716] - ConcurrencyDependencyGraph deadlock if no root can be selected
  • [MNG-7717] - Maven warns wrongly about ${localRepository} expression
  • [MNG-7720] - [REGRESSION] Build order is incorrect and does not respect Reactor Build Order
  • [MNG-7721] - Maven 3.9 resolver ignores proxy configured via MAVEN_OPTS
  • [MNG-7726] - Maven 3.9.0 resolves properties in file profile activation incorrectly
  • [MNG-7731] - MNG-7520 incorrectly back ported to Maven 3.9.0

Improvement

  • [MNG-5185] - Improve "missing dependency" error message when _maven.repositories/_remote.repositories contains other repository ids than requested
  • [MNG-7686] - Speed up by replacing non-pattern #replaceAll() with #replace() or precompiled patterns
  • [MNG-7706] - Deprecate ${localRepository} mojo parameter expression

Task

  • [MNG-7197] - Simplify exit code handling in Windows command startup script

... (truncated)

Commits
  • 2e17850 [maven-release-plugin] prepare release maven-3.9.1
  • 79100c6 Update DOAP with Maven 3.8.8 release
  • c294ef6 [MNG-7725] Update surefire to 3.0.0 in default binding
  • 5bc322a [MNG-7726] Maven 3.9.0 resolves properties in file profile activation incorre...
  • 1498486 [MNG-7723] Upgrade to Maven Resolver 1.9.7 (#1037)
  • 7d7a431 [MNG-7731] MNG-7520 incorrectly back ported to Maven 3.9.0
  • 57acdd4 [MNG-7720] Wrong build order of forked projects (#1038)
  • 528cea3 Using Set<>() for contains()
  • 366e3f5 [MNG-7715] Update to resolver 1.9.6 (#1025)
  • 837db7a [MNG-7716] ConcurrencyDependencyGraph deadlock if no root is selected
  • 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.

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)