You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Alex Boisvert (JIRA)" <ji...@apache.org> on 2009/11/20 19:51:42 UTC
[jira] Updated: (BUILDR-349) resources.filter should use defaults
from profile.yaml even if mapping is provided
[ https://issues.apache.org/jira/browse/BUILDR-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Boisvert updated BUILDR-349:
---------------------------------
Description:
Peter Schröder wrote:
if i use a filter like this:
resources.filter.using 'date'=>Time.new
the filter defined in the yaml (which are static) wont get applied
( See thread http://markmail.org/message/lqmiglkh74nkyoo5 )
was:
Peter Schröder wrote:
if i use a filter like this:
resources.filter.using 'date'=>Time.new
the filter defined in the yaml (which are static) wont get applied
(See thread http://markmail.org/message/lqmiglkh74nkyoo5)
> resources.filter should use defaults from profile.yaml even if mapping is provided
> ----------------------------------------------------------------------------------
>
> Key: BUILDR-349
> URL: https://issues.apache.org/jira/browse/BUILDR-349
> Project: Buildr
> Issue Type: Bug
> Components: Core features
> Affects Versions: 1.3.5
> Reporter: Alex Boisvert
> Assignee: Alex Boisvert
> Fix For: 1.4
>
>
> Peter Schröder wrote:
> if i use a filter like this:
> resources.filter.using 'date'=>Time.new
> the filter defined in the yaml (which are static) wont get applied
> ( See thread http://markmail.org/message/lqmiglkh74nkyoo5 )
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.