I have tried it now without the maven Nature, with the same project hierarchy, and the same log4j dependency, the problem doesn't exist in this case.
Interesting to note, that in the M2E environment, if I remove the log4j dependency from the test-jar project, the problem is gone.