Current JAR resolution assumes the following:
- The class used for JAR lookup is effectively in a JAR
- A System property is set for testing with the location of the JAR
The problem with #1 is that in some cases (when using the class in the same Maven module where the class is, the class is not in a JAR but in a directory 'target/test-classes').
The problem with #2 is the JAR does not exists at the time of running the test (packaging comes after test and we are not doing integration testing yet thus won't work)
In addition, this is required for streaming testcases, to have the JAR with streaming classes for testing.