Easy - I'm English *grin* http://www3.telus.net/linguisticsissues/BritishCanadianAmerican.htm
From: [email protected] [mailto:[email protected]] On Behalf Of Daniel Nauck Sent: Monday, 15 March 2010 11:43 PM To: [email protected] Subject: Re: [ccnet-user] SvnRevisionLabeler Hi, looks like the "labeller"-typo is very very old ;) I dont know if this has some special meaning, etc ... maybe dave knows this. Daniel Am 15.03.2010 09:54, schrieb Essl, Markus: Hello Daniel! Thanks, I'll try that out. Actually, I thought this labeller would get it's information from an assembly, not provide a format that is usable for assemblies. Another note: My spellchecker always wants to correct 'labeller' to 'labeler' - could someone shed some light on this? Markus Von: [email protected]<mailto:[email protected]> [mailto:[email protected]] Im Auftrag von Daniel Nauck Gesendet: Sonntag, 14. März 2010 15:06 An: [email protected]<mailto:[email protected]> Betreff: Re: [ccnet-user] SvnRevisionLabeler Hello, you can switch to the build-in AssemblyVersionLabeller [1] if you like. It also uses the svn revision number. Daniel [1] http://confluence.public.thoughtworks.org/display/CCNET/Assembly+Version+Labeller Am 11.03.2010 18:12, schrieb Essl, Markus: Hello! I am using the current nightly of the 1.5 branch and was using the "svn revision labeler" to give my build a label that includes the svn revision number. But it looks to me like it does not work anymore correcty - it seems that the labeler is called before the source code is updated, where in the 1.4 it was called afterwards - or I did not look carefully enough and only recognized that just now. So how is the flow? a) [Check For Modification] -> [Labeler] -> [Update Repository] -> [Tasks] -> [Publishers] b) [Check For Modification] -> [Update Repository] -> [Labeler] -> [Tasks] -> [Publishers] Thanks, Markus Markus Essl Abteilungsleiter Softwareentwicklung The information contained in this e-mail message and any accompanying files is or may be confidential. If you are not the intended recipient, any use, dissemination, reliance, forwarding, printing or copying of this e-mail or any attached files is unauthorised. This e-mail is subject to copyright. No part of it should be reproduced, adapted or communicated without the written consent of the copyright owner. If you have received this e-mail in error please advise the sender immediately by return e-mail or telephone and delete all copies. Fairfax does not guarantee the accuracy or completeness of any information contained in this e-mail or attached files. Internet communications are not secure, therefore Fairfax does not accept legal responsibility for the contents of this message or attached files.
