jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Maven 2.x Resources Plugin
  • MRESOURCES-46

Provide support for more complex filtering (Velocity, etc)

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: New Feature New Feature
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None

Description

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.

Issue Links

is duplicated by

New Feature - A new feature of the product, which has yet to be developed. MRESOURCES-40 Filtering of resources using a templating engine (e.g. Freemarker)

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Improvement - An improvement or enhancement to an existing feature or task. MRESOURCES-34 Maven2 resource filtering : could be more powerful thanks to the use of templates

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Stéphane Nicoll added a comment - 14/Aug/07 7:47 AM

should be made available to all plugins (in a shared component).

Brian, if you can refine that would be good. We can't support "everything" and "complex filtering" without valid uses cases.

Show
Stéphane Nicoll added a comment - 14/Aug/07 7:47 AM should be made available to all plugins (in a shared component). Brian, if you can refine that would be good. We can't support "everything" and "complex filtering" without valid uses cases.
Hide
Permalink
Brian Jackson added a comment - 14/Aug/07 9:11 AM

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.

Show
Brian Jackson added a comment - 14/Aug/07 9:11 AM 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.

People

  • Assignee:
    Unassigned
    Reporter:
    Brian Jackson
Vote (1)
Watch (3)

Dates

  • Created:
    13/Aug/07 11:43 PM
    Updated:
    28/Sep/09 11:09 AM
  • Atlassian JIRA (v5.0.4#731-sha1:3aa7374)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.