[ 
https://issues.apache.org/jira/browse/MSHARED-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16734226#comment-16734226
 ] 

Jean-Charles Manoury commented on MSHARED-793:
----------------------------------------------

Sorry I shouldn't have mentioned Spring compatibility, it's confusing.

Here an example :

We are using a properties file for each environment of our project (dev, QA, 
pre-production, etc...) and we setup this .properties file during the build 
with maven-filters (at the end properties are read by Spring but that's not the 
point), I would like to avoid empty properties when they are not set 
specifically for an environment, that's why I would like to have a default 
value.

> Support for default value
> -------------------------
>
>                 Key: MSHARED-793
>                 URL: https://issues.apache.org/jira/browse/MSHARED-793
>             Project: Maven Shared Components
>          Issue Type: New Feature
>          Components: maven-filtering
>    Affects Versions: maven-filtering-3.1.2
>            Reporter: Jean-Charles Manoury
>            Priority: Major
>              Labels: pull-request-available
>
> The goal is to manage default value like ${toto:tutu} where tutu is used when 
> no value for toto is found.
>  It is the same behavior as Spring's 
> [PropertyPlaceholderConfigurer|https://www.mkyong.com/spring/spring-propertyplaceholderconfigurer-example/]
> This will make properties files from a Spring project compatible with 
> maven-filtering.
> A pull request had been created on Github : 
> https://github.com/apache/maven-filtering/pull/1



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to