You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm particularly interested in this feature in the Gradle plugin, but this feature could totally benefit the Maven plugin as well, which is why I've created this request here.
Type of Issue
It is a :
bug
request
question regarding the documentation
Motivation
When it comes to implementing ArchUnit in existing projects, the Freezing rules feature is very useful for implementing an iterative approach.
As it is, I haven't found any workaround other than declaring each rule twice, once "normally", and once wrapping it with FreezingArchRule.freeze(rule). By doing this, it is then possible to decide in the plugin configuration whether to use the "normal" rule or the frozen rule. In the meantime, if anyone sees a better workaround, don't hesitate to share :-)
A new configuration point in ConfigurableRules seems to me more appropriate for deciding whether a rule is frozen or not. WDYT?
Summary
A new configuration point for ConfigurableRules could be very useful to specify whether a rule is frozen or not.
See https://www.archunit.org/userguide/html/000_Index.html#_freezing_arch_rules for reference documentation.
I'm particularly interested in this feature in the Gradle plugin, but this feature could totally benefit the Maven plugin as well, which is why I've created this request here.
Type of Issue
It is a :
Motivation
When it comes to implementing ArchUnit in existing projects, the Freezing rules feature is very useful for implementing an iterative approach.
As it is, I haven't found any workaround other than declaring each rule twice, once "normally", and once wrapping it with
FreezingArchRule.freeze(rule)
. By doing this, it is then possible to decide in the plugin configuration whether to use the "normal" rule or the frozen rule. In the meantime, if anyone sees a better workaround, don't hesitate to share :-)A new configuration point in ConfigurableRules seems to me more appropriate for deciding whether a rule is frozen or not. WDYT?
Current Behavior
Expected Behavior
Your Environment
Version used:
OS and version: MacOS Ventura (13.5.1)
The text was updated successfully, but these errors were encountered: