Tests run under regular classpath, not the custom one defined by the plugin. This works for some tests where this is expected, but other tests it’s just retesting the `test` sourceset tests, not the custom provided ones (ex: slickTest).
Disable JIT in Java7 for 1 Bytebuddy method. Hopefully this will help
with this error:
```
Stack: [0x00007f892f079000,0x00007f892f17a000], sp=0x00007f892f174e30, free space=1007k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V [libjvm.so+0x73db30] PhaseIdealLoop::build_loop_late_post(Node*)+0x130
V [libjvm.so+0x73e06b] PhaseIdealLoop::build_loop_late(VectorSet&, Node_List&, Node_Stack&)+0x10b
V [libjvm.so+0x745239] PhaseIdealLoop::build_and_optimize(bool, bool)+0x899
V [libjvm.so+0x4589b0] Compile::Optimize()+0x8f0
V [libjvm.so+0x459e87] Compile::Compile(ciEnv*, C2Compiler*, ciMethod*, int, bool, bool)+0x10c7
V [libjvm.so+0x3c9c5c] C2Compiler::compile_method(ciEnv*, ciMethod*, int)+0xec
V [libjvm.so+0x45f5bb] CompileBroker::invoke_compiler_on_method(CompileTask*)+0x32b
V [libjvm.so+0x460960] CompileBroker::compiler_thread_loop()+0x440
V [libjvm.so+0x9283ab] JavaThread::thread_main_inner()+0xdb
V [libjvm.so+0x928590] JavaThread::run()+0x1d0
V [libjvm.so+0x7f56e2] java_start(Thread*)+0x122
Current CompileTask:
C2: 3653 733
net.bytebuddy.description.type.TypeDescription$Generic$Visitor$Substitutor::onParameterizedType (129
bytes)
```
By default, instrumentation is enabled, and can be disabled by default by overriding the `defaultEnabled` method. Instrumentation can also be disabled individually or enabled when default is disabled.
Java 9 is commented out because there are some test failures that will be investigated later.
Some tests had to be excluded from Java 7 because they don’t have a Java 7 compatible version.
This should only be used for local development. This makes it easier for command line testing to have consistent file references that don’t change each release.
If caught with a format violation, executing `./gradlew googleJavaFormat` should fix it.
There are currently some warnings, but they’re not causing failures, so we can clean that up as we go.