#3: implementation component rules C5 - C7 - violations#42
#3: implementation component rules C5 - C7 - violations#42NicolasVanBellen wants to merge 5 commits intodevonfw-sample:violations/componentfrom
Conversation
| @@ -0,0 +1,7 @@ | |||
| package com.devonfw.sample.batch.task.batchLayer; | |||
There was a problem hiding this comment.
The term Layer is not part of the package definition. It is just logic, dataaccess, batch, etc.
There was a problem hiding this comment.
that was a following mistake from my misunderstanding earlier. I will fix that now.
hohwille
left a comment
There was a problem hiding this comment.
@NicolasVanBellen thanks for your PR with the violations. Looks good. 👍
I left a small comment for you to have a look.
BTW: In Java by conventions package segments are lowercaseonly so no pascalCase like componentA would be used to follow best-practices. However, in this case where we actually demonstrate anti-patterns this is fully fine.
|
The violation messages from your ArchUnit rules look very clear and self-explanatory to me: However, due to the comment I already left, you are violating a different rule than you actually intended: |
#3
DO NOT MERGE
This fork branch contains classes demonstrating archunit component rules violations:
Rules C5 - C7