Skip to content

Bump maven-jar-plugin from 3.2.2 to 3.3.0#524

Merged
mergify[bot] merged 1 commit intomainfrom
dependabot/maven/org.apache.maven.plugins-maven-jar-plugin-3.3.0
Sep 24, 2022
Merged

Bump maven-jar-plugin from 3.2.2 to 3.3.0#524
mergify[bot] merged 1 commit intomainfrom
dependabot/maven/org.apache.maven.plugins-maven-jar-plugin-3.3.0

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github Sep 19, 2022

Bumps maven-jar-plugin from 3.2.2 to 3.3.0.

Release notes

Sourced from maven-jar-plugin's releases.

3.3.0

🚀 New features and improvements

🐛 Bug Fixes

📦 Dependency updates

📝 Documentation updates

  • Restore mavenArchiverVersion property used in the site (#51) @​jorsol
  • (doc) Updated create-test-jar.apt.vm removing 'and' in Maven site Create Test JAR documentation (#34) @​focbenz

👻 Maintenance

Commits
  • d68df4b [maven-release-plugin] prepare release maven-jar-plugin-3.3.0
  • fb2299a Restore mavenArchiverVersion property used in the site
  • 1204127 [MJAR-290] - Update Plexus Utils to 3.4.2
  • 5fd2fc9 [MJAR-291] - Upgrade Parent to 37
  • 56344da use shared action v3 (#49)
  • 4148491 Code simplifications in AbstractMojo (#47)
  • 46c017d [MJAR-275] - Fix outputTimestamp not applied to module-info; breaks reproduci...
  • c02be20 [MJAR-278] Update plugin (requires Maven 3.2.5+) (#19)
  • b6fe3eb Bump junit from 4.11 to 4.13.2 in /src/it/MJAR-228
  • 78a28dd Ignore Maven Core updates
  • 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)

Bumps [maven-jar-plugin](https://github.com/apache/maven-jar-plugin) from 3.2.2 to 3.3.0.
- [Release notes](https://github.com/apache/maven-jar-plugin/releases)
- [Commits](apache/maven-jar-plugin@maven-jar-plugin-3.2.2...maven-jar-plugin-3.3.0)

---
updated-dependencies:
- dependency-name: org.apache.maven.plugins:maven-jar-plugin
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file java labels Sep 19, 2022
@mergify mergify Bot merged commit 5d2a4ca into main Sep 24, 2022
@dependabot dependabot Bot deleted the dependabot/maven/org.apache.maven.plugins-maven-jar-plugin-3.3.0 branch September 24, 2022 08:06
mergify Bot added a commit that referenced this pull request Apr 26, 2026
…o 5.21.0 in /studio [skip ci]

Bumps [enhanced-resolve](https://github.com/webpack/enhanced-resolve) from 5.20.1 to 5.21.0.
Release notes

*Sourced from [enhanced-resolve's releases](https://github.com/webpack/enhanced-resolve/releases).*

> v5.21.0
> -------
>
> ### Minor Changes
>
> * Added promise API and support to resolve without `context` and `resolveContext`. (by [`@​alexander-akait`](https://github.com/alexander-akait) in [#520](https://redirect.github.com/webpack/enhanced-resolve/pull/520))
> * Add `extensionAliasForExports` option. When `true`, `extensionAlias` also applies to paths resolved through the `package.json` `exports` field. Off by default to match Node.js; opt in for full TypeScript-resolver parity with packages that ship `.ts` sources alongside the compiled `.js` they declare in `exports`. (by [`@​alexander-akait`](https://github.com/alexander-akait) in [#554](https://redirect.github.com/webpack/enhanced-resolve/pull/554))
>
> ### Patch Changes
>
> * Properly handle DOS device paths (`\\?\…` and `\\.\…`). (by [`@​alexander-akait`](https://github.com/alexander-akait) in [#551](https://redirect.github.com/webpack/enhanced-resolve/pull/551))
> * Prevent fallback to parent node\_modules when the `exports` field target file is not found. (by [`@​xiaoxiaojx`](https://github.com/xiaoxiaojx) in [#495](https://redirect.github.com/webpack/enhanced-resolve/pull/495))
> * Imports field spec deviation: non-relative targets (e.g. `"#a": "#b"`) no longer re-enter imports resolution, aligning with the Node.js ESM spec where `PACKAGE_IMPORTS_RESOLVE` does not recursively resolve `#` specifiers. (by [`@​xiaoxiaojx`](https://github.com/xiaoxiaojx) in [#503](https://redirect.github.com/webpack/enhanced-resolve/pull/503))
>
>   Previously `{ "#a": "#b", "#b": "./the.js" }` would chain-resolve `#a` to `./the.js`; now it correctly fails, matching Node.js behavior.
> * Move `cachedJoin`/`cachedDirname`/`createCachedBasename` caches from module-level globals to per-Resolver instances. This prevents unbounded memory growth in long-running processes — when a Resolver is garbage collected, its join/dirname/basename caches are released with it. (by [`@​xiaoxiaojx`](https://github.com/xiaoxiaojx) in [#507](https://redirect.github.com/webpack/enhanced-resolve/pull/507))
> * Fixed when `tsconfig: true` is used (default config file) and no `tsconfig.json` exists. (by [`@​xiaoxiaojx`](https://github.com/xiaoxiaojx) in [#502](https://redirect.github.com/webpack/enhanced-resolve/pull/502))
> * Apply the `extensionAlias` option to the `imports` field to be align with typescript resolution. (by [`@​alexander-akait`](https://github.com/alexander-akait) in [#549](https://redirect.github.com/webpack/enhanced-resolve/pull/549))
> * Improved performance of the many plugins. (by [`@​alexander-akait`](https://github.com/alexander-akait) in [#529](https://redirect.github.com/webpack/enhanced-resolve/pull/529))
> * Replace the `Set<string>`-based resolver stack with a singly-linked `StackEntry` class that exposes a Set-compatible API. (by [`@​xiaoxiaojx`](https://github.com/xiaoxiaojx) in [#526](https://redirect.github.com/webpack/enhanced-resolve/pull/526))
>
>   Each `doResolve` call now prepends a single linked-list node instead of cloning the entire Set, making stack push O(1) in time and memory. Recursion detection walks the linked list (O(n)), but because the stack is typically shallow this is much cheaper than cloning a Set per call.
> * Cache the result of `stripJsonComments` + `JSON.parse` in `readJson` using a `WeakMap` keyed by the raw file buffer. This avoids redundant comment-stripping and JSON parsing on every resolve call that reads tsconfig.json files (via `stripComments: true`), improving TsconfigPathsPlugin warm performance by ~20-35% depending on the depth of the `extends` chain. (by [`@​xiaoxiaojx`](https://github.com/xiaoxiaojx) in [#524](https://redirect.github.com/webpack/enhanced-resolve/pull/524))
> * Avoid OOM in CachedInputFileSystem when duration is Infinity. (by [`@​alexander-akait`](https://github.com/alexander-akait) in [#527](https://redirect.github.com/webpack/enhanced-resolve/pull/527))


Changelog

*Sourced from [enhanced-resolve's changelog](https://github.com/webpack/enhanced-resolve/blob/main/CHANGELOG.md).*

> 5.21.0
> ------
>
> ### Minor Changes
>
> * Added promise API and support to resolve without `context` and `resolveContext`. (by [`@​alexander-akait`](https://github.com/alexander-akait) in [#520](https://redirect.github.com/webpack/enhanced-resolve/pull/520))
> * Add `extensionAliasForExports` option. When `true`, `extensionAlias` also applies to paths resolved through the `package.json` `exports` field. Off by default to match Node.js; opt in for full TypeScript-resolver parity with packages that ship `.ts` sources alongside the compiled `.js` they declare in `exports`. (by [`@​alexander-akait`](https://github.com/alexander-akait) in [#554](https://redirect.github.com/webpack/enhanced-resolve/pull/554))
>
> ### Patch Changes
>
> * Properly handle DOS device paths (`\\?\…` and `\\.\…`). (by [`@​alexander-akait`](https://github.com/alexander-akait) in [#551](https://redirect.github.com/webpack/enhanced-resolve/pull/551))
> * Prevent fallback to parent node\_modules when the `exports` field target file is not found. (by [`@​xiaoxiaojx`](https://github.com/xiaoxiaojx) in [#495](https://redirect.github.com/webpack/enhanced-resolve/pull/495))
> * Imports field spec deviation: non-relative targets (e.g. `"#a": "#b"`) no longer re-enter imports resolution, aligning with the Node.js ESM spec where `PACKAGE_IMPORTS_RESOLVE` does not recursively resolve `#` specifiers. (by [`@​xiaoxiaojx`](https://github.com/xiaoxiaojx) in [#503](https://redirect.github.com/webpack/enhanced-resolve/pull/503))
>
>   Previously `{ "#a": "#b", "#b": "./the.js" }` would chain-resolve `#a` to `./the.js`; now it correctly fails, matching Node.js behavior.
> * Move `cachedJoin`/`cachedDirname`/`createCachedBasename` caches from module-level globals to per-Resolver instances. This prevents unbounded memory growth in long-running processes — when a Resolver is garbage collected, its join/dirname/basename caches are released with it. (by [`@​xiaoxiaojx`](https://github.com/xiaoxiaojx) in [#507](https://redirect.github.com/webpack/enhanced-resolve/pull/507))
> * Fixed when `tsconfig: true` is used (default config file) and no `tsconfig.json` exists. (by [`@​xiaoxiaojx`](https://github.com/xiaoxiaojx) in [#502](https://redirect.github.com/webpack/enhanced-resolve/pull/502))
> * Apply the `extensionAlias` option to the `imports` field to be align with typescript resolution. (by [`@​alexander-akait`](https://github.com/alexander-akait) in [#549](https://redirect.github.com/webpack/enhanced-resolve/pull/549))
> * Improved performance of the many plugins. (by [`@​alexander-akait`](https://github.com/alexander-akait) in [#529](https://redirect.github.com/webpack/enhanced-resolve/pull/529))
> * Replace the `Set<string>`-based resolver stack with a singly-linked `StackEntry` class that exposes a Set-compatible API. (by [`@​xiaoxiaojx`](https://github.com/xiaoxiaojx) in [#526](https://redirect.github.com/webpack/enhanced-resolve/pull/526))
>
>   Each `doResolve` call now prepends a single linked-list node instead of cloning the entire Set, making stack push O(1) in time and memory. Recursion detection walks the linked list (O(n)), but because the stack is typically shallow this is much cheaper than cloning a Set per call.
> * Cache the result of `stripJsonComments` + `JSON.parse` in `readJson` using a `WeakMap` keyed by the raw file buffer. This avoids redundant comment-stripping and JSON parsing on every resolve call that reads tsconfig.json files (via `stripComments: true`), improving TsconfigPathsPlugin warm performance by ~20-35% depending on the depth of the `extends` chain. (by [`@​xiaoxiaojx`](https://github.com/xiaoxiaojx) in [#524](https://redirect.github.com/webpack/enhanced-resolve/pull/524))
> * Avoid OOM in CachedInputFileSystem when duration is Infinity. (by [`@​alexander-akait`](https://github.com/alexander-akait) in [#527](https://redirect.github.com/webpack/enhanced-resolve/pull/527))


Commits

* [`35035ca`](webpack/enhanced-resolve@35035ca) chore(release): new release ([#496](https://redirect.github.com/webpack/enhanced-resolve/issues/496))
* [`fd688b1`](webpack/enhanced-resolve@fd688b1) perf: cache conditionalMapping + per-plugin description-file lookups ([#556](https://redirect.github.com/webpack/enhanced-resolve/issues/556))
* [`26f15b0`](webpack/enhanced-resolve@26f15b0) fix(path): classify DOS device paths as Windows-absolute ([#551](https://redirect.github.com/webpack/enhanced-resolve/issues/551))
* [`a04bc4c`](webpack/enhanced-resolve@a04bc4c) docs: add resolvePromise examples for Resolver and ResolverFactory ([#555](https://redirect.github.com/webpack/enhanced-resolve/issues/555))
* [`f9f6d57`](webpack/enhanced-resolve@f9f6d57) Merge pull request [#554](https://redirect.github.com/webpack/enhanced-resolve/issues/554) from webpack/claude/fix-extension-alias-alignment-xC6sZ
* [`c1319d1`](webpack/enhanced-resolve@c1319d1) chore: regenerate types.d.ts after option rename
* [`5a00e63`](webpack/enhanced-resolve@5a00e63) refactor: rename applyExtensionAliasToExportsField to extensionAliasForExports
* [`f5adeee`](webpack/enhanced-resolve@f5adeee) test(alias): guard that absolute path aliasing is not skipped ([#553](https://redirect.github.com/webpack/enhanced-resolve/issues/553))
* [`faa178f`](webpack/enhanced-resolve@faa178f) fix(TsconfigPathsPlugin): give references priority over main paths ([#552](https://redirect.github.com/webpack/enhanced-resolve/issues/552))
* [`e82275d`](webpack/enhanced-resolve@e82275d) test(imports/exports): cover query and fragment in field resolution
* Additional commits viewable in [compare view](webpack/enhanced-resolve@v5.20.1...v5.21.0)
  
[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility\_score?dependency-name=enhanced-resolve&package-manager=npm\_and\_yarn&previous-version=5.20.1&new-version=5.21.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
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-automerge-start)
[//]: # (dependabot-automerge-end)
---
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 show  ignore conditions` will show all of the ignore conditions of the specified dependency
- `@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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant