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 weld-junit4 from 1.3.1.Final to 3.1.0.Final #49

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

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jun 2, 2022

Bumps weld-junit4 from 1.3.1.Final to 3.1.0.Final.

Release notes

Sourced from weld-junit4's releases.

3.1.0.Final

Version 3 of this library keeps supporting Weld 4, Jakarta EE 9.

While there are no significant changes to JUnit extensions, the minor version bump is due to the addition of Spock support. If you want to learn more, the README file captures it nicely.

Note that unless there are severe bugs, we are not planning any further releases for 3.x branch due to the fact that the Weld version is it designed for has entered maintenance mode as well. We of course keep supporting newer versions and have already released 4.0.0.Final of this library which is tailored for Weld 5 (Jakarta EE 10).

3.0.0.Final - Jakarta EE 9 variant of weld-junit

This new major version switches to EE 9 meaning it supports and uses Weld 4/CDI 3.0 and with it the jakarta namespace. Otherwise it brings no functional changes over the latest 2.x release.

Note that this also means that anyone who needs to still run on top of older versions/namespaces will have to keep using version 2.x which we now have a branch for and which will keep getting updated as well.

If you find any issues, please report them via GH issues and we'll into them as soon as possible.

Happy testing!

2.0.2.Final

This new version brings few more polishments and QoL updates. Let's take a look at those:

  • MockBean now correctly adds @Any qualifier
  • Allow injection into test classes when using @ClassRule
  • CDI contexts are now activated prior to any injection attempts
  • @EnableAutoWeld now scans injected Instance<SomeClass> fields for bean candidates
  • @EnableAutoWeld now correctly respects inherited injected fields and considers their types beans
  • Extension now uses Weld 3.1.6.Final by default
  • Make use of new JUnit APIs to improve extension lifecycle and annotation handling
  • Several updates to README files to make them more user-friendly and accurate

2.0.1.Final

This is a small release with sole purpose of bumping the Weld version in weld-junit to 3.1.2.Final. This hopefully solves the problems people were having when running on newer JDKs and remove the need to override some internal dependencies brought in by Weld.

2.0.0.Final

We have a new major version in which we are dropping support CDI 1.2 (Weld 2.4) and fully moving to CDI 2.0 (Weld 3). Apart from that, this release brings:

  • Removal of @OverrideBean, as it effectively duplicating what can be achieved by declaring an alternative
  • Introduction of @ExcludeBean and @ExcludeBeanClasses which allow to exclude some classes from automatic discovery and replace them with ad-hoc producers
  • Users can now define MockBean with priority, making it a globally enabled alternative
  • Synthetic bean archive now adds a dummy bean in case there is an alternative enabled to avoid a corner case where the archive would be considered empty if no other bean than alternative was present
  • Update to JUnit versions used internally
Commits
  • 2d94ae0 [maven-release-plugin] prepare release 3.1.0.Final
  • 3833b3a Update CI setup to acknowledge 3.1 branch
  • f1234de Changes to primary README
  • 4f8027b Add a Spock module
  • 634e197 Add some explanatory comment to AutoConfigWithWeldSetupTest.
  • 2413e0e Improve various details in the JUnit Jupiter module
  • c84f492 Fix broken AbstractWeldInitiator#isRunning if container is not yet initialized
  • 4fbbae2 Make sure CI runs for 4.x branch.
  • 92e2ed9 Introduce recursive search for WeldInitiator in nested test classes
  • b8ecc45 [maven-release-plugin] prepare for next development iteration
  • 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 [weld-junit4](https://github.com/weld/weld-junit) from 1.3.1.Final to 3.1.0.Final.
- [Release notes](https://github.com/weld/weld-junit/releases)
- [Commits](weld/weld-testing@1.3.1.Final...3.1.0.Final)

---
updated-dependencies:
- dependency-name: org.jboss.weld:weld-junit4
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
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.

0 participants