On Mon, Dec 7, 2020 at 11:30 PM Rob Sargent <[email protected]> wrote:
> Thank you for your patience. I don't know that I'm reporting a bug (or > suspicion of one). Let me try to re-phrase: > I see, makes sense. > Is the config.xml in the first message well formed (at least well formed > enough that the warnings can be ignored)? > You mean valid? Well-formedness is easy to check. It's probably valid, if it was valid before... Do check if namespaces are correct, and if the correct versions of jOOQ are used. > Is the "illegal reflection" safe to ignore or preferably correctable? > It is always safe to ignore for now. It just means that some library is trying to access JDK internals that it shouldn't access (but everyone did it for the past 25 years). Future JDK versions (16 or 17 I think) will start preventing such access by default, but as far as I know, it will still be possible to make it work for quite a while. > With these answered I can go back to digging and should I find or suspect > a bug I will do my best to make a MCVE. But as this may be strictly > related to gradle I'm not sure how that will turn out when translated to a > pom. > A gradle MCVE template is overdue! I might create one, soon. The examples by Etienne Studer might work too, though: https://github.com/etiennestuder/gradle-jooq-plugin/tree/master/example Thanks, Lukas -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jooq-user/CAB4ELO4uDsk1KdQVmt%3DVP7s9fsz4x_6Y6hPP42k6E9Vhocz%2BAQ%40mail.gmail.com.
