Currently the layer for connecting with database is called dataaccess.
This is compliant with the classic project structure.
However, with the modern project structure the layer has been renamed to domain.
A JUnit test has to be part of this story that tests multiple Java packages with default configuration (new Configuration()) via DevonPackageImpl. It should test the three layers valid for dataaccess/domain layer as well as a the other valid layers (service, logic, common) and also an invalid layer (e.g. with typo such as domian) and assert proper expected results.
Currently the layer for connecting with database is called
dataaccess. This is compliant with the classic project structure. However, with the modern project structure the layer has been renamed todomain.This story is about changing this sonar-devon4j-plugin so that
domainis accepted as synonym todataaccess. If we already change this, we should also acceptpersistenceas a synonym as well that is used by RegisterFactory / IsyFact. This is already archivable via custom configuration inarchitecture.jsonbut should be supported out of the box with the default config. See also https://github.com/devonfw/sonar-devon4j-plugin/blob/master/src/main/java/com/devonfw/ide/sonarqube/common/api/config/DevonPackageImpl.javaA JUnit test has to be part of this story that tests multiple Java packages with default configuration (
new Configuration()) via DevonPackageImpl. It should test the three layers valid for dataaccess/domain layer as well as a the other valid layers (service,logic,common) and also an invalid layer (e.g. with typo such asdomian) and assert proper expected results.