You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dennis Lundberg (JIRA)" <ji...@codehaus.org> on 2011/01/10 23:25:58 UTC

[jira] Updated: (MRESOURCES-40) Filtering of resources using a templating engine (e.g. Freemarker)

     [ http://jira.codehaus.org/browse/MRESOURCES-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dennis Lundberg updated MRESOURCES-40:
--------------------------------------

    Component/s: filtering

> Filtering of resources using a templating engine (e.g. Freemarker)
> ------------------------------------------------------------------
>
>                 Key: MRESOURCES-40
>                 URL: http://jira.codehaus.org/browse/MRESOURCES-40
>             Project: Maven 2.x Resources Plugin
>          Issue Type: New Feature
>          Components: filtering
>            Reporter: Sami Dalouche
>
> Resource Filtering is often used to generate different configuration files for different environments...
> It often makes sense to use different values (debug set to true for the development profile, to false for the production environment). However, it is sometimes impossible to just switch values, and additional sections need to be added or removed depending on the environment.
> Additionally, the configuration could sometimes be cleaner by adopting conventions based on the environment name. (if the application needs to connect to 5 databases whose url depends on the environment name, only part of the settings can be required in the .properties files).
> That's why I believe it would be nice to have a plugin that would filter a set of resources using some templating engine (freemarker, velocity, ...). Each resource would then be a freemarker/velocity-compliant file, and the possibilities then become endless :)

-- 
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