You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looks like similar symptoms as spring-projects/spring-framework#21515 in that only the target/test-classes path is found when specifying a package that gets translated to a resource path.
Test looks like:
@AnalyzeClasses(packages = "com.mycompany.myapp")
public class ArchitectureConstraintsTest {
@ArchTest
public static final ArchRule controllersAnnotatedProperly = classes().that().haveSimpleNameEndingWith("Controller")
.should().beAnnotatedWith(RestController.class);
@ArchTest
public static final ArchRule controllersAutowired = constructors().that().areDeclaredInClassesThat().haveSimpleNameEndingWith("Controller")
.should().beAnnotatedWith(Autowired.class);
}
The text was updated successfully, but these errors were encountered:
Could you supply a minimal example project to reproduce this? Theoretically ArchUnit should look into the module path, at least it works for JDK classes. But maybe there is some problem in modularized environments.
Looks like similar symptoms as spring-projects/spring-framework#21515 in that only the
target/test-classes
path is found when specifying a package that gets translated to a resource path.Test looks like:
The text was updated successfully, but these errors were encountered: