Lukas - does this mean that JOOQ doesn’t promise to get binary (or source) compatible even between patch releases?
I don’t use the code-gen myself favouring manually constructing the table/fields declarations where we use it (and we lock down our versions and prevent mismatched versions) but not everyone is doing crazy things like that.
But yeh, if doing code-gen - probably best to use the generator for the version you’re shipping with.
If code is re-generated using version X, it is always a good idea to also
upgrade the library version to X. However, just upgrading the library to
version X should not cause any trouble if the generated code is still on an
older version Y.
In general, we are binary compatible between patch releases. I cannot think
of a binary incompatible change between 3.11.7 and 3.11.12, although I
might overlook something, of course.
I found solution I use springBootVersion = "2.1.1.RELEASE" and this have
dependency jooq 3.11.7 then I change with springBootVersion =
"2.1.7.RELEASE" and this have dependency jooq 3.11.11
and I set jooqversion to 3.11.11 and now work
Il giorno mercoledì 28 agosto 2019 12:00:06 UTC+2, Lukas Eder ha scritto:
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to [hidden email].