Hibernate ORM and Search extensions now requires dev build profile #32004
Labels
area/hibernate-orm
Hibernate ORM
area/persistence
OBSOLETE, DO NOT USE
kind/bug
Something isn't working
Milestone
Describe the bug
I realize that opinions whether this is bug may differs heavily, but I want to create this issue (and PR that proposes fix) as it seems unnecessary. Our CI is failing because of this quarkus-qe/quarkus-test-suite#1124.
#31946 introduced
@IfBuildProfile("dev")
forHibernateOrmDevJsonRpcService
andHibernateSearchElasticsearchDevJsonRpcService
. That means that in terms of Hibernate ORM extension, DEV profile is same now as DEV launch mode. Previously it wasn't true.We curate Quarkus application and launch it in DEV mode without setting "dev" profile.
Expected behavior
There is easy fix possible on both Quarkus side or our side, however I would prefer if Hibernate ORM worked in DEV mode as previously.
Actual behavior
DEV beans are missing
How to Reproduce?
Steps to reproduce:
quarkus create app hibernate-reproducer -x hibernate-orm,resteasy-reactive,jdbc-postgresql --stream=3.0
cd hibernate-reproducer/
mvn quarkus:dev -Dquarkus.platform.version=999-SNAPSHOT -Dquarkus.platform.group-id=io.quarkus -Dquarkus.profile=stuff
I realize I can do
-Dquarkus.profile=stuff,dev
and it will work.Output of
uname -a
orver
Linux
Output of
java -version
openjdk 17.0.4 2022-07-19
GraalVM version (if different from Java)
OpenJDK Runtime Environment GraalVM CE 23.2
Quarkus version or git rev
999-SNAPSHOT
Build tool (ie. output of
mvnw --version
orgradlew --version
)Apache Maven 3.8.6
Additional information
No response
The text was updated successfully, but these errors were encountered: