Uses of Package
dev.archunitjava.rules
Packages that use dev.archunitjava.rules
Package
Description
-
Classes in dev.archunitjava.rules used by dev.archunitjava.cliClassDescriptionImmutable architecture rule with uniform metadata decoration.Shared dependency assertion moods evaluated by one graph engine.Treatment of graph targets absent from the imported type/package model.Whether an edge whose projected origin equals its target participates in a rule.
-
Classes in dev.archunitjava.rules used by dev.archunitjava.junit
-
Classes in dev.archunitjava.rules used by dev.archunitjava.metrics
-
Classes in dev.archunitjava.rules used by dev.archunitjava.presets
-
Classes in dev.archunitjava.rules used by dev.archunitjava.rulesClassDescriptionRequired and forbidden annotation moods evaluated by one assertion implementation.Immutable annotation relationship, mood, typed values, and traversal-gap policy.One typed condition over an explicitly encoded annotation element.Deterministic operations over explicitly encoded, typed annotation elements.Immutable architecture rule with uniform metadata decoration.Explicit treatment of accesses originating in synthetic types, methods, or bridges.Explicit dependency semantics and output bounds for type and package cycle rules.Shared dependency assertion moods evaluated by one graph engine.Immutable dependency mood and edge-boundary policies.Match policy for a boolean JPMS directive modifier.Qualified-target shape required of an exports or opens directive.Treatment of graph targets absent from the imported type/package model.Whether a hierarchy rule inspects only declarations or the complete reachable hierarchy.Java hierarchy relationship kept distinct instead of being flattened into dependencies.Positive and negative moods evaluated by the same hierarchy assertion.Immutable relationship, traversal, mood, and unknown-ancestor policy.Java/JVM access classification kept separate from JPMS package exports.Negative, constrained, group-positive, and per-caller member-access policies.Immutable access mood, independently selected opcode kinds, and compiler-artifact policy.A named, inspectable policy assignment for imported JPMS module identities.Detached comparison of declared readability and bytecode-observed module dependencies.One detached declared or observed module dependency with its evidence domain kept explicit.JPMS export classification for a resolved cross-boundary access.Stable result identity that cannot collapse explicit, automatic, and unnamed modules.Exports/opens mode with qualification and optional qualified target matching.Requires-directive mode plus exact transitive/static-phase modifier constraints.Negative, allow-list, or existence semantics for module descriptor declarations.Explicit opt-ins for subjects commonly created by compilers or generators.Distinct Java naming and provenance values; each has one required pattern domain.Explicit caller decision for automatic and unnamed modules, which have no Module attribute.A named, inspectable policy assignment for imported Java packages.Positive and negative pattern assertions sharing one implementation.Declared interpretation of configured graph entry points.Explicit dependency semantics and finding bounds for reachability rules.Pure rule terminal supplied with the immutable metadata that must be attached to its result.Builds the ordinary result while retaining diagnostics supplied by the shared terminal.One named selector/count pair inspected by the shared rule terminal.Whether an edge whose projected origin equals its target participates in a rule.Whether evidence owned only by synthetic types, synthetic members, or bridge methods is used.A named, inspectable policy assignment for imported Java types.Whether declaration/signature and other non-call type-use edges participate in cycle rules.Treatment of a meta-annotation or inherited-annotation traversal gap.Policy for a transitive conclusion whose external inheritance is not fully known.