java.lang.NoSuchMethodError: org.jooq.impl.Internal.createParameter(Ljava/lang/String;Lorg/jooq/DataType;ZZ)Lorg/jooq/Parameter;

[Nicola Micheli]

I use jooqversion 3.11.7 and it works fine with version 3.11.12 I have this error 

java.lang.NoSuchMethodError: org.jooq.impl.Internal.createParameter(Ljava/lang/String;Lorg/jooq/DataType;ZZ)Lorg/jooq/Parameter;

[Lukas Eder]

Hi Nicola,

This is probably due to your using jOOQ 3.11 for source code generation but still have an older version on your classpath during runtime. If you're using Maven, you can use "mvn dependency:tree -Dverbose" to find out where the additional dependency gets pulled from.

I hope this helps,

Lukas

On Mon, Aug 26, 2019 at 2:42 PM Nicola Micheli <micheli...@gmail.com> wrote:

I use jooqversion 3.11.7 and it works fine with version 3.11.12 I have this error 

java.lang.NoSuchMethodError: org.jooq.impl.Internal.createParameter(Ljava/lang/String;Lorg/jooq/DataType;ZZ)Lorg/jooq/Parameter;

--
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 jooq-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jooq-user/925df31b-7acd-40da-9362-fcb8040600e1%40googlegroups.com.

[Mark Derricutt]

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.

Mark

[Lukas Eder]

Hi Mark,

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 hope this helps,

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 jooq-user+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jooq-user/54ee6e07-7fa8-47e6-8f5e-7033422c0077%40Spark.

[Nicola Micheli]

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:

Hi Mark,

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 hope this helps,

Lukas

On Wed, Aug 28, 2019 at 11:03 AM Mark Derricutt <ma...@talios.com> wrote:

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.

Mark

On 27 Aug 2019, 5:44 PM +1200, jooq...@googlegroups.com, wrote:

This is probably due to your using jOOQ 3.11 for source code generation but still have an older version on your classpath during runtime

--
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 jooq...@googlegroups.com.

[Lukas Eder]

Thanks for sharing this, Nicola,

Do note we've recently published a blog post about how to override Spring Boot's default jOOQ version with Maven:

https://blog.jooq.org/2019/06/26/how-to-use-jooqs-commercial-distributions-with-spring-boot/ 

I hope this helps,

Lukas 

To unsubscribe from this group and stop receiving emails from it, send an email to jooq-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jooq-user/8adf1de4-5b70-489c-889c-29239549de47%40googlegroups.com.