You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Assaf Arkin (JIRA)" <ji...@apache.org> on 2008/10/22 20:45:44 UTC

[jira] Resolved: (BUILDR-149) cannot specify foo.bar=value as argument

     [ https://issues.apache.org/jira/browse/BUILDR-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Assaf Arkin resolved BUILDR-149.
--------------------------------

    Resolution: Won't Fix

Inherited from Rake.  I'm guessing to keep behavior consistent -- variables can be inherited from the environment or set on the command line, and dots are not supported in environment variable names (at least not on bash).

> cannot specify foo.bar=value as argument
> ----------------------------------------
>
>                 Key: BUILDR-149
>                 URL: https://issues.apache.org/jira/browse/BUILDR-149
>             Project: Buildr
>          Issue Type: Bug
>          Components: Core features
>    Affects Versions: 1.3.2
>            Reporter: Ittay Dror
>
> > buildr foo.bar=value
> (in /work/HEAD, development)
> Don't know how to build task 'foo.bar=value'
> [Failed] Your build failed with an error: /work/HEAD:
> Don't know how to build task 'foo.bar=value'
> buildr aborted!
> The reason is that Buildr.application.collect_tasks parses arguments using the \w regexp which takes dots to be word separators. similarly, foo:bar=value, foo-bar=value, will not work.
> Maybe just use /^(.+)=(.*)$/ to recognize variables? This means task names cannot contain '=', but variables and task names can still contain all special symbols.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.