How to configure maven jar plugin to exclude properties on profile

Question

I have this configuration in my pom

<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-jar-plugin</artifactId>
    <version>2.2</version>
    <configuration>
        <excludes>                      
            <exclude>**/logging/*</exclude>
            <exclude>**/config/*</exclude>
        </excludes>
    </configuration>
</plugin>

I use profiles to handle different behaviour from local environment to production environment. Is it possible not activate the exclusions when executing mvn install with local profile? I tried to set a blank properties on local environment like this but the plugin complains.

score 1 · Answer 1 · answered Sep 07 '12 at 12:19

This is a workaround solution, maybe a better one exists. I think the easiest you could do is to let your DEV environment free from any config of the jar plugin. And then place your PROD config in a dedicated profile :

<profiles>                                                         
    <profile>                                                      
        <id>PROD</id>                                              
        <build>                                                    
            <plugins>                                              
                <plugin>                                           
                    <groupId>org.apache.maven.plugins</groupId>    
                    <artifactId>maven-jar-plugin</artifactId>      
                    <version>2.2</version>                         
                    <configuration>                                
                        <excludes>                                 
                            <exclude>**/logging/*</exclude>        
                            <exclude>**/config/*</exclude>         
                        </excludes>                                
                    </configuration>                               
                </plugin>                                          
            </plugins>                                             
        </build>                                                   
    </profile>                                                     
</profiles>

When you need to build the production jar, launch :

mvn clean install -PPROD

score 0 · Answer 2 · answered Sep 07 '12 at 13:21

0

Are the logging and config files resources for testing only? If yes, put them in ${basedir}/src/test/resources. They'll be on the classpath for your tests but will not end up in the final jar, and you won't need specific jar plugin config.

answered Sep 07 '12 at 13:21

user944849

14,524
2
61
83

Nope, they are needed from the application to execute. – Massimo Ugues Sep 14 '12 at 14:53
That's true, but the files are develop/system/production ones. – Massimo Ugues Oct 09 '12 at 14:36

score 0 · Accepted Answer · answered Sep 14 '12 at 15:00

The best workaround I found is to use an invalid value to filter on when executing on DEV environment.

<profiles>
    <profile>
        <id>env-local</id>
        <activation>
            <property>
                <name>env</name>
                <value>local</value>
            </property>
        </activation>
        <properties>
            <jndi.iban0>cont0Data</jndi.iban0>
            <config.file.path>classpath:config</config.file.path>
            <logging.file.path>classpath:logging</logging.file.path>
            <exclude.logging>none</exclude.logging>
            <exclude.config>none</exclude.config>
        </properties>
    </profile>
</profiles>

How to configure maven jar plugin to exclude properties on profile

3 Answers3