Skip to content

spring-boot-starter-data-jpa 3.2.0 version alignment issue #38712

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
maurice85 opened this issue Dec 8, 2023 · 1 comment
Closed

spring-boot-starter-data-jpa 3.2.0 version alignment issue #38712

maurice85 opened this issue Dec 8, 2023 · 1 comment
Labels
for: external-project For an external project and not something we can fix status: invalid An issue that we don't feel is valid

Comments

@maurice85
Copy link

Hibernate 6.4.0.Final uses antlr4 version 4.13.0 but spring-boot-starter-data-jpa 3.2.0 still uses antlr4 version 4.10.1. This causes the warning message

ANTLR Tool version 4.13.0 used for code generation does not match the current runtime version 4.10.1.

I've resolve this problem by excluding the dependency 4.10.1 from spring-boot-starter-data-jpa 3.2.0 and explicitly adding antlr 4.13.0 with

    <dependency>
        <groupId>org.antlr</groupId>
        <artifactId>antlr4-runtime</artifactId>
        <version>4.13.0</version>
        <scope>runtime</scope>
    </dependency>

However because the version is hardcoded in org.data.jpa.repository.query.HqlLexer and other jpa classes that use RuntimeMetaData.checkVersion(); I still get the same warning during application startup.

Please make spring boot jpa use antlr4 4.13.0 and update the hardcoded string "4.10.1" to "4.13.0"

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Dec 8, 2023
@wilkinsona
Copy link
Member

wilkinsona commented Dec 8, 2023

This needs to be addressed in Spring Data JPA as part of their Hibernate 6.4.0 upgrade. Please open an issue there.

@wilkinsona wilkinsona closed this as not planned Won't fix, can't repro, duplicate, stale Dec 8, 2023
@wilkinsona wilkinsona added status: invalid An issue that we don't feel is valid for: external-project For an external project and not something we can fix and removed status: waiting-for-triage An issue we've not yet triaged labels Dec 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
for: external-project For an external project and not something we can fix status: invalid An issue that we don't feel is valid
Projects
None yet
Development

No branches or pull requests

3 participants