Open hohwille opened 1 year ago
Info: This taks is relevant for everyone.
I missed to review the first draft PR in all details:
-@AnalyzeClasses(packages = "com.devonfw.sample.archunit", importOptions = ImportOption.DoNotIncludeTests.class)
+@AnalyzeClasses(packages = "com.devonfw.sample.archunitviolations", importOptions = ImportOption.DoNotIncludeTests.class)
IMHO it is not a good idea to change any of the JUnits in a draft PR demonstrating violations. We should use the regular package namespace of our demo to show the violations in action.
Fortunately this pattern was not followed by all others when creating violation PRs.
Draft PRs had been created. However, I will do some rework later with the following aspects:
We need to have Java code that violates the architecture rules and shows our ArchUnit test(s) in action. For implementing this story, we should first think about the design as there are several options: