Hibernate ORM codestart doesn't compile out of the box, jdbc extension is needed

Describe the bug

Hibernate ORM codestart doesn’t compile out of the box, jdbc extension is needed

Hibernate ORM codestart was introduced in https://github.com/quarkusio/quarkus/pull/20879 by @loicmathieu

Expected behavior

codestart compiles

Actual behavior

codestart doesn’t compile on its own, additional changes are needed

How to Reproduce?

Download sample app with just orm extension selected from https://code.quarkus.io/

Run mvn clean verify

Output of uname -a or ver

No response

Output of java -version

No response

GraalVM version (if different from Java)

No response

Quarkus version or git rev

No response

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

[yrodiere]

I’ll let @Sanne and @yrodiere decide on this one.

Ok, so I’ll decide: we’ve been arguing for a long time with no decision, we need to move on. Let’s close this.

Two motivations:

1. Codestarts are a thing whether we like it or not. We could argue about their value, but that ship has sailed. If we provide codestarts, let’s provide them consistently.
2. Adding a JDBC extension automatically is not possible, because we don’t know which one to add. Better an application that fails and tells you why than an application that takes a decision without you knowing, and may take the wrong decision.

So let’s keep the things as they are, and keep adding codestarts. If people forget to include a JDBC driver, we’ll error out and people will just include a JDBC driver. If the current error is unclear, we’ll improve it.

AFAICS, I’m not the only one with that opinion.

Closing as not planned; thanks everyone involved for the discussion.

[loicmathieu]

So, what is the decision around this issue ? It blocks #21651

My take on it: keep it as today, an error is good and people must add a JDBC driver when using Hibernate.