Currently, the DeprecationRule architecture test checks all configured ArchUnit rules and fails when deprecated usage is detected.
Example:
@test
public void deprecation_rule() {
JavaClasses importedClasses = new ClassFileImporter()
.importPackages(HttpClientAdapter.class.getPackage().getName());
DeprecationRule deprecationRule = new DeprecationRule();
for (Map.Entry<String, ArchRule> entry : deprecationRule.getRules().entrySet()) {
entry.getValue().check(importedClasses);
}
}
There are cases where deprecated usage is intentional, temporary, or unavoidable, especially when integrating with third-party APIs or legacy internal APIs.
The library should support skipping/suppressing specific deprecation rule violations using @SuppressWarnings.
Currently, the DeprecationRule architecture test checks all configured ArchUnit rules and fails when deprecated usage is detected.
Example:
@test
public void deprecation_rule() {
JavaClasses importedClasses = new ClassFileImporter()
.importPackages(HttpClientAdapter.class.getPackage().getName());
}
There are cases where deprecated usage is intentional, temporary, or unavoidable, especially when integrating with third-party APIs or legacy internal APIs.
The library should support skipping/suppressing specific deprecation rule violations using @SuppressWarnings.