Viczian Istvan

I think there are two solutions: More modules: for some classes it is to much effort. Mark JUnit dependency as optional. And it is a good practice to move the things depend on JUnit to a separate package.

I think there are two solutions: More modules: for some classes it is to much effort. Mark JUnit dependency as optional. And it is a good practice to move the things depend on JUnit to a separate package.

There is no slf4j-nop dependency, so this issue can be closed now.

Upgrate Java version to 8 in dbunit-maven-plugin

Remove commons-collections dependency

Remove commons-io dependency

Use optional in junit and hamcrest Maven dependencies

Use optional in poi-ooxml and postgresql Maven dependencies