Allow all classes from a JAR, Module, or Package to be Included for Reflection about native-build-tools

[pompiuses]

This feature is very welcomed! We're currently using the tracing agent together with our test suite to automatically pick up all use of reflection (which is somewhat error prone if low test coverage). This new feature in combination with the tracing agent would eliminate all reflection related runtime errors we get. So it'd be nice if it's made to work seamlessly together.

[kristofdho]

Looks promising. A couple questions/suggestions.

1. Is it possible to combine filters? E.g. Only package org.example.foo from dependency org.example:bar:*?
2. If you know you only need constructors, is it possible to only add them for an entire package?
3. Is it possible to provide a custom filter to the plugin? A Predicate<Class> and Predicate<Executable> for example?
4. Is it possible to still specify a "typeReachable" condition on the generated entries?

A specific use-case I have now, for which I have a Feature with a subtype reachability handler:
For all subclasses of Foo Register all methods prefixed with create* with a matching return type and parameter list.
Which is extremely specific I guess. I'd imagine specifying a custom filter class in the lines of this, which is still missing the "typeReachable" part:

class CustomFilter implements PluginFilter {
    @Override
    boolean includeClass(Class<?> clazz) {
        return Foo.class.isAssignableFrom(clazz);
    }

    @Override
    boolean includeMethod(Method method) {
        return method.getName().startsWith("create"); // + check returntype & parameter types
    }

    @Override
    boolean includeConstructor(Constructor<?> cconstructor) {
        return false;
    }

    @Override
    boolean includeField(Field field) {
        return false;
    }
}

[vjovanov]

@kristofdho this is possible, we need to be careful not to duplicate too much of functionality. Such fine-grained adjustments can currently be done with Native Image features.