ClassTransformer

[bertung]

Okay here we go again. Our API supports multiple backends and we have our own main method. We do not force our customers to also define a static main method so that we should inject one using a transformer. For example, we also have GWT backend. Users should be able compile with our Teavm backend without changing any code. We are not an expert on your class transformation features, so we derived one by reading your source code. It does not inject the static main method when the target is wasm-gc. In another transformer, we simply setInitialValue of a field that also is not reflected to the produced code when the wasm-gc is used.

[konsoletyper]

I think this happens because of the order of application of transformers. TeaVM users transformers under the hood for exposing exported methods. Since transformers are not part of public API, I'm not going to do anything with this.

But I still not sure why are you using this particular approach. I don't know all your internal kitchen, but there must be alternative ways to do the same thing. For example, generate a separate entry point in your build system. It can be either class file (use ASM or similar library to generate it), or Java/Kotlin file. It could contain main method which simply instantiates your main class. Just provide this class, instead of user's entry point, to TeaVM.

[bertung]

Well, thank you very much for the help.

I do not think I will pursue this any further.

Signing off.