[ 
http://jira.codehaus.org/browse/MRESOURCES-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_104819
 ] 

Brian Jackson commented on MRESOURCES-46:
-----------------------------------------

Two use cases I need that are currently not supported.

1) Conditionally include/exclude sections of a file based on  property.  This 
is not possible currently
2) Inject file fragment into another file.  We have a DAO framework that 
generates a fragment of a config file.  I would like to be able to inject this 
generated file into a template of a full config file.

These relate to managing configuration files for our application.  We have many 
instance of our application with different config as well as differences per 
instance across deployment environments.  Example:

Football instance has 5 config files and is deployed to 4 environments, 
local-dev, dev, qa, prod.
Baseball instance has 5 config files and is deployed to 4 environments, 
local-dev, dev, qa, prod.

What sounds like 40 files is more since each developer has there own version of 
local-dev.  I'd like to reduce this to maintaining 5 templates for Football and 
5 templates for Baseball with the environment differences specified in a Maven 
profile.  The config files would then be generated from the templates.

> Provide support for more complex filtering (Velocity, etc)
> ----------------------------------------------------------
>
>                 Key: MRESOURCES-46
>                 URL: http://jira.codehaus.org/browse/MRESOURCES-46
>             Project: Maven 2.x Resources Plugin
>          Issue Type: New Feature
>            Reporter: Brian Jackson
>
> My resources (ex. configuration files that have conditional blocks based on 
> target environment) need more complex filtering then simple token 
> replacement.  Support for any templating language would be helpful.  An 
> abstraction to plugin the language desired would be even better.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to