brooth/jeta

NOTICE: Project sadly discontinued

jeta's Issues

Default Metasitory implementation has performance flaws

Using *.class constants in MapMetasitory triggers eager loading of those classes (including invocation of static initializers). Classloading is slow and triggering too much of it early is a major anti-pattern. Square (creators of Dagger) stumbled upon the issue of excess classloading in Dagger 1, which was combining moderate use of reflection with APT. That caused some Dagger contributors to become so deeply disillusioned with whole thing, that they created Dagger 2, which forces it's users to write names of not-yet-generated classes in code (which IMO is a bit too much).

A possible workaround is to map class names to constructors instead:

private static getMetacodeInner(String className) {
    switch(className) {
        case "com.example.HelloWorld":
            return new HelloWorldMetacode();
         case "com.example.SomeOtherClass":
            return new SomeOtherClassMetacode();
        default:
            return null;
    }
}

This approach is still Proguard-friendly and does not cause excess classloading in any modern JVMs. In addition it avoids creation of an unnecessary map (especially since all required information is already available at compile time).

Document for MetasitoryContainer is missing

I followed the userguide but there is an error at runtime: Failed to load class com.example.MetasitoryContainer

I did some search but no idea how to make it works

Library purposes in README.md missed

Jeta - is an Open Source library, built on the top of javax.annotation.processing.

Is that wrap just for wrap?:)

Metacode rebuild very slow

metacode rebuild take very long time, even there is only one file modified.
utd.enable set to true in jeta.properties