layer rules treating sub-packages as different layer?

[hohwille]

I have an ArchRule with something like

layeredArchitecture().consideringAllDependencies().layer("soap").definedBy("..soap..")
...
.whereLayer("soap").mayNotBeAccessedByAnyLayer()
...

And now I get violations like this:

Constructor <com.example.app.component.soap.generated.ISearchServiceGetSearchFaultFaultFaultMessage.(java.lang.String, com.example.app.component.soap.generated.data.SearchFault)> has parameter of type <com.example.app.component.soap.generated.data.SearchFault> in (ISearchServiceGetSearchFaultFaultFaultMessage.java:0)

For me this is unexpected since I expect both classes to be recognized in the same layer.
The second one is just in a sub-package of the first.
Is this a bug in ArchUnit or is there something I can do in my ArchRule to make it work as expected?
Also it would be helpful if the violation messages would also print the layer that was detected by ArchUnit.
Maybe it did not detect the classes in soap layer what is an important difference for debugging if both classes are considered to be in the soap layer.
WDYT?
Thanks in advance for any help
Cheers, Jörg