Spring Boot jar启动报错：创建ConfigurationPropertiesBindingPostProcessor bean失败

Hey there, I’ve run into this exact issue before—apps working fine in IDE but breaking when run as a jar. Let’s walk through the most likely fixes based on your setup:

1. Verify Your @PropertySource Setup & Configuration File Location #

First, double-check that your datasource-postgresql.properties is placed directly in src/main/resources—this ensures it gets packaged correctly into the jar’s BOOT-INF/classes directory (the classpath root for executable jars).

Also, Spring Boot’s @ConfigurationProperties works better with external configs when paired with @EnableConfigurationProperties, rather than relying solely on @PropertySource. Update your config class like this to avoid parsing issues:

@Configuration
@EnableConfigurationProperties
@PropertySource(value = {"classpath:datasource-postgresql.properties"})
public class DataSourceConfig {
    // Your datasource beans and property bindings here
}

2. Fix Your Maven Plugin Configuration #

Make sure your pom.xml includes the Spring Boot Maven Plugin with the repackage goal—this is what turns your regular jar into an executable "fat jar" with all dependencies properly bundled. Add or update this section:

<build>
    <plugins>
        <plugin>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-maven-plugin</artifactId>
            <version>your-spring-boot-version</version> <!-- Match your project's Spring Boot version -->
            <executions>
                <execution>
                    <goals>
                        <goal>repackage</goal>
                    </goals>
                </execution>
            </executions>
        </plugin>
    </plugins>
</build>

Without the repackage goal, your jar won’t have the correct classloader setup to access resources and dependencies at runtime.

3. Validate Your Properties File #

Check that datasource-postgresql.properties has no syntax errors (missing equals signs, mismatched quotes, invalid characters) and uses UTF-8 encoding. Corrupted or malformed property files can cause the configuration binding processor to fail silently during jar execution.

4. Check for Dependency Conflicts #

Sometimes runtime bean errors stem from conflicting dependencies. Run this command to generate a dependency tree:

mvn dependency:tree

Look for duplicate or mismatched versions of Spring Core/Context dependencies, then exclude the conflicting ones from your pom.xml.

Debugging Tip #

To get more detailed error logs, run your jar with the debug flag:

java -jar your-application.jar -Ddebug

This will show the full stack trace and help pinpoint exactly which part of the configuration binding is failing.

内容的提问来源于stack exchange，提问作者Thanh Dong