From: Dominik G. <os...@gu...> - 2010-03-26 09:08:19
|
Am 25.03.2010 17:12, schrieb Gert Driesen: > Hi Ryan, > > I guess it won't make it in time for the 0.90 release. > Personally, I even consider the sysinfo task deprecated. > >>>> >>>> On Mar 25, 2010, at 8:10 AM, "Gert Driesen" <ger...@te...> >>>> wrote: >>>> >>>>> Ryan, >>>>> >>>>> We cannot allow parenthesis in property names, as that would screw >>>>> up our expression tokenizer. >>>>> I'm more enclined to a machanism that allows explicit control over >>>>> the property names that a given environment variable is mapped to. >>>>> Something similar to the file mappers in Ant would be great. >>>>> >>>> If I understand you correctly, are you referring to something like: >>>> >>>> <sysinfo> >>>> <mapper type="glob" from="*(* to="*_*" /> >>>> </sysinfo> >>>> >>>> Am I understanding you right? >>> Hi, sorry, I did not write that I checked the parens handling in properties and found out that the parser will fail. The mapper solution looks good but as Gert stated <sysinfo> is kind of deprecated. So we might not put to much effort into it. Another point which needs attantion (propably for 1.0) is that I was able to define a property with parens without getting an exception at definition time. More detail later. First of all I want to get these tests green for 0.90 release. My proposal: - add "failonerror='true'" to all existing tests - add a new test which throws BuildException for "Environment.ProgramFiles(64)" - fix docu - sort output What do you think? Regards Dominik -- The answer to the great question of life, the universe and everything is 42 (Douglas Adams) |