jpamodelgen fails with range out of bounds about quarkus

[yrodiere]

I am however not sure if it describes the same situation as mine - and wanted the issue to be tracked here as well, so it is easier to find for other quarkus users.

Given there is little specific to Quarkus in jpamodelgen... I'd bet on this being totally unrelated to Quarkus.

There is already a similar issue on the hibernate tracker: https://hibernate.atlassian.net/jira/software/c/projects/HHH/issues/HHH-17514 Which has a PR hibernate/hibernate-orm#7637.

Thanks for linking to the upstream issue. Let's close when we upgrade to the relevant upstream version then.

[yrodiere]

Wait... that's wrong. https://hibernate.atlassian.net/browse/HHH-17514 affects 6.4.0, it's not fixed there. The issue is still open upstream.

Reopening...

[quarkus-bot]

/cc @gsmet (hibernate-orm), @yrodiere (hibernate-orm)

[Postremus]

There is already a similar issue on the hibernate tracker: https://hibernate.atlassian.net/jira/software/c/projects/HHH/issues/HHH-17514
Which has a PR hibernate/hibernate-orm#7637.

I am however not sure if it describes the same situation as mine - and wanted the issue to be tracked here as well, so it is easier to find for other quarkus users.

[Postremus]

FTR.
As a workaround, I declare a known good version of the jpamodelgen in my own dependencymanagement.

<dependencyManagement>
        <dependencies>
            <dependency>
                <groupId>org.hibernate.orm</groupId>
                <artifactId>hibernate-jpamodelgen</artifactId>
                <version>6.2.13.Final</version>
            </dependency>
        </dependencies>
    </dependencyManagement>

Now I can already switch to declaring my annotationProcessors using the compiler plugin.

<build>
        <plugins>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-compiler-plugin</artifactId>
                <configuration>
                    <annotationProcessorPaths>
                        <path>
                            <groupId>org.hibernate.orm</groupId>
                            <artifactId>hibernate-jpamodelgen</artifactId>
                        </path>
                    </annotationProcessorPaths>
                </configuration>
            </plugin>
        </plugins>
    </build>

This uses my own declared version of 6.2.13.Final - and the build is succesfull. Once the bug is fixed upstream (and quarkus updated), I can simply remove the entry from my own dependency-management.

[geoand]

Has this since been fixed?

[yrodiere]

The fix was in Hibernate ORM 6.4.0, which we upgraded to in #36978, first released in Quarkus 3.7.0.CR1.

So yes it's been fixed, I just forgot to list it in the relevant PR, sorry.

Closing.

[geoand]

Thanks!

[yrodiere]

So the bug was apparently fixed somewhere between 6.4.1 and 6.4.8, see https://hibernate.atlassian.net/browse/HHH-17514. But since it was fixed by an unrelated change, I don't know which version

I don't think it matters anyway; in Quarkus, it's fixed for sure by #40102 in Quarkus 3.11.0.CR1, and should also be fixed in any version that upgrades to Hibernate ORM 6.4.8 (I'll send a PR shortly for Quarkus 3.8).