Lära Integrating Configuration with Maven | Advanced Java Configuration Techniques

Maven is a powerful build automation tool that can simplify configuration management in Java projects. One of its most useful features is resource filtering, which allows you to inject dynamic values into properties files during the build process. With resource filtering, you can define placeholders in your properties files and have Maven replace them with actual values specified in your pom.xml or provided as system properties. This technique helps ensure that configuration values—such as application version, build timestamp, or environment-specific settings—are always up to date and consistent across your deployments.

pom.xml

src/main/resources/application.properties


              123456789101112131415161718192021
            
<project xmlns="http://maven.apache.org/POM/4.0.0"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>
    <groupId>com.example</groupId>
    <artifactId>config-demo</artifactId>
    <version>1.0-SNAPSHOT</version>
    <properties>
        <app.name>ConfigDemoApp</app.name>
        <app.version>${project.version}</app.version>
    </properties>
    <build>
        <resources>
            <resource>
                <directory>src/main/resources</directory>
                <filtering>true</filtering>
            </resource>
        </resources>
    </build>
</project>

When using Maven resource filtering, it is important to carefully separate build-time and runtime configuration. Build-time configuration includes values that are determined during the build process, such as the application version or build number, and can be safely embedded into the artifacts. Runtime configuration, on the other hand, consists of values that may change between deployments or environments, such as database URLs or API keys. To avoid leaking sensitive or environment-specific information into your builds, keep runtime configuration outside of version control and inject it at deployment time. This separation helps maintain security and flexibility across your development, testing, and production environments.

pom.xml

src/main/resources/config.properties


              123456789101112131415161718192021222324252627282930313233
            
<project xmlns="http://maven.apache.org/POM/4.0.0"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>
    <groupId>com.example</groupId>
    <artifactId>env-config-demo</artifactId>
    <version>1.0-SNAPSHOT</version>
    <profiles>
        <profile>
            <id>dev</id>
            <properties>
                <env.name>development</env.name>
                <db.url>jdbc:h2:mem:devdb</db.url>
            </properties>
        </profile>
        <profile>
            <id>prod</id>
            <properties>
                <env.name>production</env.name>
                <db.url>jdbc:mysql://prod-db-server/proddb</db.url>
            </properties>
        </profile>
    </profiles>
    <build>
        <resources>
            <resource>
                <directory>src/main/resources</directory>
                <filtering>true</filtering>
            </resource>
        </resources>
    </build>
</project>

1. What is Maven resource filtering used for?

2. How can Maven profiles help manage environment-specific configuration?

Var allt tydligt?

Tack för dina kommentarer!

Avsnitt 3. Kapitel 3

Fråga AI

Fråga vad du vill eller prova någon av de föreslagna frågorna för att starta vårt samtal

Suggested prompts:

Can you show me an example of how to enable resource filtering in the pom.xml?

How do I define and activate Maven profiles for different environments?

What are some best practices for separating build-time and runtime configuration in Maven?

Svep för att visa menyn

pom.xml

src/main/resources/application.properties


              123456789101112131415161718192021
            
<project xmlns="http://maven.apache.org/POM/4.0.0"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>
    <groupId>com.example</groupId>
    <artifactId>config-demo</artifactId>
    <version>1.0-SNAPSHOT</version>
    <properties>
        <app.name>ConfigDemoApp</app.name>
        <app.version>${project.version}</app.version>
    </properties>
    <build>
        <resources>
            <resource>
                <directory>src/main/resources</directory>
                <filtering>true</filtering>
            </resource>
        </resources>
    </build>
</project>

pom.xml

src/main/resources/config.properties


              123456789101112131415161718192021222324252627282930313233
            
<project xmlns="http://maven.apache.org/POM/4.0.0"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>
    <groupId>com.example</groupId>
    <artifactId>env-config-demo</artifactId>
    <version>1.0-SNAPSHOT</version>
    <profiles>
        <profile>
            <id>dev</id>
            <properties>
                <env.name>development</env.name>
                <db.url>jdbc:h2:mem:devdb</db.url>
            </properties>
        </profile>
        <profile>
            <id>prod</id>
            <properties>
                <env.name>production</env.name>
                <db.url>jdbc:mysql://prod-db-server/proddb</db.url>
            </properties>
        </profile>
    </profiles>
    <build>
        <resources>
            <resource>
                <directory>src/main/resources</directory>
                <filtering>true</filtering>
            </resource>
        </resources>
    </build>
</project>

1. What is Maven resource filtering used for?

2. How can Maven profiles help manage environment-specific configuration?

Var allt tydligt?

Tack för dina kommentarer!

Avsnitt 3. Kapitel 3