-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
#3: implementation component rules C5 - C7 - violations #42
base: violations/component
Are you sure you want to change the base?
#3: implementation component rules C5 - C7 - violations #42
Conversation
@@ -0,0 +1,7 @@ | |||
package com.devonfw.sample.batch.task.batchLayer; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The term Layer
is not part of the package definition. It is just logic
, dataaccess
, batch
, etc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that was a following mistake from my misunderstanding earlier. I will fix that now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@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