startups-up fails to start on spring boot todo

[cmoulliard]

Issue

The check: startups-up fails when executed top of the migrated Spring -> Quarkus TODO application

❯ mvn -q quarkus:dev -Dquarkus.http.port=18081 -Dquarkus.devservices.enabled=false -Dquarkus.analytics.disabled=true
Listening for transport dt_socket at address: 5005
__  ____  __  _____   ___  __ ____  ______ 
 --/ __ \/ / / / _ | / _ \/ //_/ / / / __/ 
 -/ /_/ / /_/ / __ |/ , _/ ,< / /_/ /\ \   
--\___\_\____/_/ |_/_/|_/_/|_|\____/___/   
2026-05-08 12:22:15,375 WARN  [io.quarkus.config] (Quarkus Main Thread) The "quarkus.hibernate-orm.database.generation" config property is deprecated and should not be used anymore.
                                                                                                                                                                                                      
2026-05-08 12:22:15,447 INFO  [io.quarkus.deployment.dev.IsolatedDevModeMain] (main) Attempting to start live reload endpoint to recover from previous Quarkus startup failure
2026-05-08 12:22:15,447 ERROR [io.quarkus.runtime.Application] (Quarkus Main Thread) Failed to start application: java.lang.RuntimeException: Failed to start quarkus
        at io.quarkus.runner.ApplicationImpl.doStart(Unknown Source)
        at io.quarkus.runtime.Application.start(Application.java:112)
        at io.quarkus.runtime.ApplicationLifecycleManager.run(ApplicationLifecycleManager.java:127)
        at io.quarkus.runtime.Quarkus.run(Quarkus.java:79)                                                                                                                                            
        at io.quarkus.runtime.Quarkus.run(Quarkus.java:50)                                                                                                                                            
        at io.quarkus.runtime.Quarkus.run(Quarkus.java:143)                                                                                                                                           
        at io.quarkus.runner.GeneratedMain.main(Unknown Source)                                                                                                                                       
        at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)                                                                                      
        at java.base/java.lang.reflect.Method.invoke(Method.java:565)                                                                                                                                 
        at io.quarkus.runner.bootstrap.StartupActionImpl$1.run(StartupActionImpl.java:163)                                                                                                            
        at java.base/java.lang.Thread.run(Thread.java:1474)                                                                                                                                           
Caused by: io.quarkus.runtime.configuration.ConfigurationException: Unable to find datasource '<default>' for persistence unit '<default>': Bean is not active: SYNTHETIC bean [class=io.agroal.api.AgroalDataSource, id=83v3mgZs1bc75ou7lAXNtJCAcLA]                                                                                                                                                       
Reason: Datasource '<default>' was deactivated automatically because its URL is not set. To activate the datasource, set configuration property 'quarkus.datasource.jdbc.url'. Refer to https://quarkus.io/guides/datasource for guidance.                                                                                                                                                                  
To avoid this exception while keeping the bean inactive:                                                                                                                                              
        - Configure all extensions consuming this bean as inactive as well, if they allow it, e.g. 'quarkus.someextension.active=false'                                                               
        - Make sure that custom code only accesses this bean if it is active                                                                                                                          
        at io.quarkus.hibernate.orm.runtime.PersistenceUnitUtil.unableToFindDataSource(PersistenceUnitUtil.java:129)                                                                                  
        at io.quarkus.hibernate.orm.runtime.FastBootHibernatePersistenceProvider.injectDataSource(FastBootHibernatePersistenceProvider.java:474)                                                      
        at io.quarkus.hibernate.orm.runtime.FastBootHibernatePersistenceProvider.buildRuntimeSettings(FastBootHibernatePersistenceProvider.java:244)                                                  
        at io.quarkus.hibernate.orm.runtime.FastBootHibernatePersistenceProvider.getEntityManagerFactoryBuilderOrNull(FastBootHibernatePersistenceProvider.java:211)                                  
        at io.quarkus.hibernate.orm.runtime.FastBootHibernatePersistenceProvider.createEntityManagerFactory(FastBootHibernatePersistenceProvider.java:84)                                             
        at jakarta.persistence.Persistence.createEntityManagerFactory(Persistence.java:90)                                                                                                            
        at io.quarkus.hibernate.orm.runtime.JPAConfig$LazyPersistenceUnit.get(JPAConfig.java:178)                                                                                                     
        at io.quarkus.hibernate.orm.runtime.JPAConfig$1.run(JPAConfig.java:65)                                                                                                                        
        ... 1 more                                

[cmoulliard]

Can we avoid such an issue if we say explicitly to use H2 instead of a DB requiring containers and docker or podman ?

// AI thinking mentions such a message from time to time
Since both `quarkus-jdbc-mysql` (compile scope) and `quarkus-jdbc-h2` (test scope) are on the classpath during tests, I need to use the H2 approach differently. Actually, with both drivers present, Quarkus can select the right one based on the `db-kind` per profile since this is resolved at build time and both drivers are available. However, the safer approach is to use Dev Services with H2 which doesn't need Docker.

@aureamunoz