Steven Schlansker

Some minor progress here - by reducing Mockito usage to only interfaces, and disabling codegen and using Proxy mocks instead, the "more than one class" problem goes away and instead...

We now removed all uses of the bytebuddy agent and Mockito only runs with pure JVM proxies in mainline. Rebased on top of that, running the build again...

``` Failures (3): JUnit Jupiter:ConstructorMapperTest:allColumnsOfNullableNestedObjectAbsent() MethodSource [className = 'org.jdbi.v3.core.mapper.reflect.ConstructorMapperTest', methodName = 'allColumnsOfNullableNestedObjectAbsent', methodParameterTypes = ''] => java.lang.IllegalArgumentException: Instance factory 'org.jdbi.v3.core.mapper.reflect.ConstructorMapperTest$NullableNestedBean(java.lang.String,org.jdbi.v3.core.mapper.reflect.ConstructorMapperTest$NullableParameterBean)' parameter '[nested]' has no matching columns in the result set....

> How about creating the native metadata configuration files manually? The main reason is that it is a pain in the ass to get right, for something that a human...

Thanks for the reference to the Netty config - theirs is very short, so I can see how it's not too big of a deal to maintain. Ours is probably...

Ok, I have a bit more information on the test failures. It looks like a constructor parameter for a test case `@Nullable String s` loses its annotation and looks like...

I looked through the `reflect-config.json` syntax and didn't see anything about including or excluding annotations. So, I guess the agent cannot generate config around this. Therefore this is a Graal...

Interesting, I extracted the code in question into a sample project to have a reproducer, and it works there ???

Ok, so I think the problem is somehow introduced from the jdbi parent pom. When I inherit from our Jdbi build pom, the test fails. When I inline the native-image...

I think this is a native-image bug. I filed https://github.com/graalvm/native-build-tools/issues/562