Re: [Bulk] Re: [Bulk] Re: Scheduled build always say build not required

I should have researched more before posting, we clearly have sort of 
build or deployment problem - quite embarrassing. The neither the 
source, nor binary versions of 1.81 contain I fix I show as committed in 
October. I'll look into this issue and correct it. For now, there's no 
need to put together a patch Jim.

Eric Minick wrote:

> Shockingly enough, I have been watching the conversation and now that 
> I dive into the code, I'm a bit confused. I see this:
>
>            headerRE = new RE("^r(\\d+) \\| ([^\\|]+) \\| ([^\\(]+)");
>            //headerRE = new ("^r(\\d+) \\| (\\S+) \\| ([^\\(]+)");
>
> Looks like Varban had corrected this problem back in October when we 
> tripped across it in Anthill Pro (we have to apologize for not 
> remembering that and putting 2 and 2 together). Is this cropping up in 
> a different spot, or are we looking at different code?
>
> -- Eric
>
> Jim Hague wrote:
>
>> On Tuesday 4 April 2006 05:32, gnugy wrote:
>>  
>>
>>> My Regular Expressions are a little rusty my interpretation of
>>> the pattern is that it will match any line that starts with
>>> an r, followed by 1 or more digits.  Then a space followed by a 
>>> pipe(|).
>>> This is followed by another space then any number of non-whitespace
>>> characters.  Followed again by space, pipe, space.  Followed by
>>> 1 or more characters that aren't ('s.
>>>   
>>
>>
>> That's correct. You're obviously not *that* rusty :-)
>>
>>  
>>
>>> If this is the case then I thought the problem was with the
>>> fact that my author, I have "(no author)", contains a space.
>>>   
>>
>>
>> Ahhhhh! Or, indeed, aaarrgggghhhhh! Yes, that would indeed cause the 
>> problem. I didn't realise this was possible. Having checked the 
>> Subversions FAQ, do I assume someone is accessing the repository via 
>> anonymous write acces to Apache?
>>
>>  
>>
>>> So the space would break the (\\S+) part of the expression but this
>>> isn't followed by a ' | '.  So I tried replacing the  expression with:
>>>
>>> "^r(\\d+) \\| ([^\\|]+)\\| ([^\\(]+)"
>>>
>>> Running with this expression worked, awesome, thanks for your help.
>>>   
>>
>>
>> Good news, and thank you for your persistence and getting to the 
>> bottom of this.
>>
>> I'll redo the regular expression along the lines you outlined and 
>> send a patch to Urbancode.
>>
>> (I know that in one sense I should be using the 'svn log' XML output 
>> here. But frankly, I don't want to haul in an XML parser when parsing 
>> the regular output via REs is so quick and easy).
>>  
>>
>
> _______________________________________________
> Anthill mailing list
> Anthill-IWHQxnLZ/[email protected]
> http://lists.urbancode.com/mailman/listinfo/anthill