Bump archunit.version from 0.11.0 to 0.12.0

[dependabot-preview]

Bumps archunit.version from 0.11.0 to 0.12.0.

Updates archunit-junit5-api from 0.11.0 to 0.12.0

Release notes

Sourced from archunit-junit5-api's releases.

ArchUnit 0.12.0

Breaking Changes

• So far ArchUnit's terminology has been a little sloppy with respect to the naming of inner and nested classes. By the JLS "inner classes" are those classes that are nested and not static. ArchUnit's API now reflects this via JavaClass.isNestedClass() versus JavaClass.isInnerClass(). Unfortunately this means that the method formerly called JavaClass.isInnerClass() will now return a different result, i.e. it will only return true, if the class is non-static. On the other hand, the method JavaClass.isNestedClass() will behave exactly like isInnerClass() did in ArchUnit 0.11.0 (see #224; thanks a lot to @​rweisleder for the clarification and PR)
• JavaAccessCondition does not filter self-accesses anymore. This was confusing behavior that did not solve the issue it was originally intended for. However, this might lead to additional violations showing up (see #209)

Bug Fixes

• Fixed bug where simple name of local classes was incorrect (see #216; thanks a lot to @​rweisleder)
• static modifier was missing from nested classes (see #219; thanks a lot to @​rweisleder)

Enhancements

Core

• Support for Java 14 (see #230; thanks a lot to @​hankem)
• JavaModifier now contains SYNTHETIC and BRIDGE allowing more introspection and filtering of synthetic members (see #243; thanks a lot to @​alexfedorenchik)
• Every property in archunit.properties can now be overwritten by passing a system property. This can be valuable in CI environments, e.g. to specify the ViolationStore path for FreezingArchRule. Compare the user guide (see #252)
• A JavaClass representing an array can now be queried for its component type (see #187; thanks a lot to @​alexfedorenchik)
• JavaClass now offers a classpath independent version of getMethod(..) and getConstructor(..) (see #236; thanks a lot to @​rweisleder)

Lang

• Extended syntax for classes().thatAreEnums() and classes()...should().beEnums() (see #172; thanks a lot to @​rweisleder)

Library

• LayeredArchitecture now also checks that no layer is empty. While originally with good intentions, the ability to define empty layers turned out to do more harm than good (see #177; thanks a lot to @​mikomatic)
• LayeredArchitecture now allows layers to be defined by predicate. This allows for a way more flexible definition than simple package patterns (see #228; thanks a lot to @​mikomatic)
• FreezingArchRule can now be configured to be more strict, when checking rules. In particular it is possible to forbid updates of the ViolationStore or the creation of a new ViolationStore. This can serve as a safeguard in CI environments, where a missing ViolationStore is typically a misconfiguration. Compare the user guide (see #211; thanks a lot to @​hankem for reviewing and providing valuable improvements)

Commits

• f6def49 Create release news article
• 510718e Set version to 0.12.0 for next release
• 40625a3 Merge pull request #246 from rweisleder/gh-236
• 1e2401c Review: Improve test readability
• 192c0a3 Overload JavaClass.getConstructor() and JavaClass.getMethod()
• c077e0b Merge pull request #244 from alexfedorenchik/componenttype
• d63d927 Review: Add convenience method for cases where we know this type is an array ...
• b10dde6 Review: We have to always ensure the whole component type chain is present. B...
• ac545fb Review: Simplify test assertion by using ArchUnit infrastructure and Guava As...
• 7507180 Offer a way to retrieve the component type of a JavaClass that is an array.
• Additional commits viewable in compare view

Updates archunit-junit5-engine from 0.11.0 to 0.12.0

Release notes

Sourced from archunit-junit5-engine's releases.

ArchUnit 0.12.0

Breaking Changes

• So far ArchUnit's terminology has been a little sloppy with respect to the naming of inner and nested classes. By the JLS "inner classes" are those classes that are nested and not static. ArchUnit's API now reflects this via JavaClass.isNestedClass() versus JavaClass.isInnerClass(). Unfortunately this means that the method formerly called JavaClass.isInnerClass() will now return a different result, i.e. it will only return true, if the class is non-static. On the other hand, the method JavaClass.isNestedClass() will behave exactly like isInnerClass() did in ArchUnit 0.11.0 (see #224; thanks a lot to @​rweisleder for the clarification and PR)
• JavaAccessCondition does not filter self-accesses anymore. This was confusing behavior that did not solve the issue it was originally intended for. However, this might lead to additional violations showing up (see #209)

Bug Fixes

• Fixed bug where simple name of local classes was incorrect (see #216; thanks a lot to @​rweisleder)
• static modifier was missing from nested classes (see #219; thanks a lot to @​rweisleder)

Enhancements

Core

• Support for Java 14 (see #230; thanks a lot to @​hankem)
• JavaModifier now contains SYNTHETIC and BRIDGE allowing more introspection and filtering of synthetic members (see #243; thanks a lot to @​alexfedorenchik)
• Every property in archunit.properties can now be overwritten by passing a system property. This can be valuable in CI environments, e.g. to specify the ViolationStore path for FreezingArchRule. Compare the user guide (see #252)
• A JavaClass representing an array can now be queried for its component type (see #187; thanks a lot to @​alexfedorenchik)
• JavaClass now offers a classpath independent version of getMethod(..) and getConstructor(..) (see #236; thanks a lot to @​rweisleder)

Lang

• Extended syntax for classes().thatAreEnums() and classes()...should().beEnums() (see #172; thanks a lot to @​rweisleder)

Library

• LayeredArchitecture now also checks that no layer is empty. While originally with good intentions, the ability to define empty layers turned out to do more harm than good (see #177; thanks a lot to @​mikomatic)
• LayeredArchitecture now allows layers to be defined by predicate. This allows for a way more flexible definition than simple package patterns (see #228; thanks a lot to @​mikomatic)
• FreezingArchRule can now be configured to be more strict, when checking rules. In particular it is possible to forbid updates of the ViolationStore or the creation of a new ViolationStore. This can serve as a safeguard in CI environments, where a missing ViolationStore is typically a misconfiguration. Compare the user guide (see #211; thanks a lot to @​hankem for reviewing and providing valuable improvements)

Commits

• f6def49 Create release news article
• 510718e Set version to 0.12.0 for next release
• 40625a3 Merge pull request #246 from rweisleder/gh-236
• 1e2401c Review: Improve test readability
• 192c0a3 Overload JavaClass.getConstructor() and JavaClass.getMethod()
• c077e0b Merge pull request #244 from alexfedorenchik/componenttype
• d63d927 Review: Add convenience method for cases where we know this type is an array ...
• b10dde6 Review: We have to always ensure the whole component type chain is present. B...
• ac545fb Review: Simplify test assertion by using ArchUnit infrastructure and Guava As...
• 7507180 Offer a way to retrieve the component type of a JavaClass that is an array.
• Additional commits viewable in compare view

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)
• @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 the .dependabot/config.yml file in this repo:

• Update frequency
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[codecov-io]

Codecov Report

Merging #47 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #47   +/-   ##
=========================================
  Coverage     83.65%   83.65%           
  Complexity       55       55           
=========================================
  Files             7        7           
  Lines           263      263           
  Branches         43       43           
=========================================
  Hits            220      220           
  Misses           32       32           
  Partials         11       11

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6d0f5af...62cc740. Read the comment docs.