I have a similiar problem as well.
On Feb 9, 11:14 am, P-J <[email protected]> wrote: > What's the status on this? I have the same problem. > > When the LastChangeLabeller starts to remember the last label, it > would also be a good idea to add the "AllowDuplicateSubsequentLabels" > property and suffix functionality from the FileLabeller. > > //P-J > > On 2 Feb, 11:09, CinnamonDonkey <[email protected]> wrote: > > > > > Thank you for the quick response Ruben. > > > I'll check out the latest build. > > > On 2 Feb, 10:05, Ruben Willems <[email protected]> wrote: > > > > Hi > > > > can you simulate this with the latest build > > > see previous mail > > > > with kind regards > > > Ruben Willems > > > > On Mon, Feb 2, 2009 at 10:46 AM, CinnamonDonkey < > > > > [email protected]> wrote: > > > > > Hi All, > > > > > I am using the "lastChangeLabeller" with our Perforce source control > > > > system. I have noticed that if a build process is triggered and "No > > > > Modifications" are detected. The labeller labels the build as > > > > "UNKNOWN". > > > > > Surely, if no modifications are detected, then the label should simply > > > > remain unchanged and be what it was for the previous build? > > > > > Is there a way around this? > > > > > Regards, > > > > Shaun- Hide quoted text - > > - Show quoted text -
