Spring Boot 2.0.0.SNAPSHOT/RC1集成JPA无法启动求助

Hey there, let's work through this issue you're hitting. I've dealt with my share of release candidate quirks, so here's what you can do to get your app running with JPA and Spring 5:

First, a Quick Clarification #

Wait a minute—you don't have to stick to the RC1 version to use Spring 5! All Spring Boot 2.x stable releases are built on Spring Framework 5. For example, Spring Boot 2.0.0 GA (general availability) uses Spring 5.0.4.RELEASE. Downgrading to the official stable release won't strip you of Spring 5 features, and it's the most reliable fix here since RC versions are meant for testing and often have unresolved bugs or dependency mismatches.

If You Must Stick with 2.0.0.RC1 #

If you have a specific reason to use the RC1 build, try these steps:

1. Lock in a Stable Hibernate Version #

Spring Boot RC1 might be pulling in an unstable or incompatible Hibernate version under the hood. Manually specify a Spring 5-compatible Hibernate version in your pom.xml:

<dependency>
    <groupId>org.hibernate</groupId>
    <artifactId>hibernate-core</artifactId>
    <version>5.2.12.Final</version>
</dependency>

This version is fully compatible with Spring 5 and fixes many of the early integration bugs present in the RC's default dependencies.

2. Add Required Data Source Configuration #

JPA Starter requires a data source to initialize, and the RC1 build might not auto-configure a default in-memory database like later stable releases do. Add these properties to your application.properties (or application.yml):

spring.datasource.url=jdbc:h2:mem:testdb
spring.datasource.driverClassName=org.h2.Driver
spring.datasource.username=sa
spring.datasource.password=
spring.jpa.hibernate.ddl-auto=create-drop

This sets up a temporary H2 in-memory database, which should resolve any "missing data source" errors that might be crashing your startup.

3. Diagnose the Exact Error #

If the above steps don't work, check your startup logs for the root exception (look for BeanCreationException or similar). Common culprits include:

• Conflicting dependencies from other starters
• Missing JPA entity scan configurations (add @EntityScan(basePackages = "your.package.name") to your main application class if needed)
• Incompatible third-party libraries

Final Recommendation #

Unless you're actively testing RC1-specific features, I strongly suggest moving to Spring Boot 2.0.0 GA (or a newer stable 2.x release). It's built on Spring 5, fixes the JPA starter issues, and gives you a reliable foundation for your app.

内容的提问来源于stack exchange，提问作者Fabio Franco