Lukas Eder

The first. As a matter of fact, there doesn't need to be formal Xtend support in fluflu. It would be sufficient if a templating SPI was exposed, which can be...

I had also thought of the ServiceLoader. I guess, at such a low level (APT), this might seem appropriate.

That should be pretty obvious. A versatile code generator is always better than a rigid one. XJC may be poorly documented, but it's very powerful in its extensibility. Obviously, this...

You're probably speaking from bad experience :-) A well-defined SPI doesn't necessarily introduce complexity, it may even reduce it by externalising complex solutions to SPI implementations. I'll leave this up...

> The loss in developer productivity, long runtimes on build pipelines and time it takes to maintain the scripts and environments grew to a significant amount of money, which is...

> by removing various packages related to special features that weren't needed by that project Sounds like what the utplsql folks are doing as well: https://twitter.com/Pazus/status/1362030711637766145

Cool, thank you. I'll send a PR during the next days

Hmm, I'm not sure if that's related. But that "Wikipedia Featured" dropdown contains items such as "Metro Layouts" linking to http://aozora.github.io/bootmetro/demo/metro-layouts.html, which is a dead link...

This also pops up in the jOOQ integration tests. Simple reproducer: ```sql create table t (i int) ``` And then: ```java System.out.println( Flux.from(cf.create()) .flatMap(c -> c.createStatement("insert into t values ($1)")...

@gregturn My PR did, at the time, I think? I'm sorry, I have a lot on my plate, can't prioritise building the next snapshot of this for another test spin...