Change in SVN ADD behaviour between 1.6.5 and 1.7.5
From: Mark Bertenshaw <mark.bertenshaw_at_fidessa.com>
Date: Tue, 26 Jun 2012 13:58:56 +0000
Hi -
I have just cleared up a build issue which resulted from upgrading from Subversion 1.6.5 and 1.7.5. There is a point in the process where we add any newly created component logs with:
SVN ADD -q $APPROOT/LOGS/*
In both versions of Subversion, this raises an error saying that the log file is already under version control. That's fine - the NANT script doesn't care about that. However, it seems that whilst 1.6.5 simply raised a warning for this process, 1.7.5 actually sets a return code of 1. NANT interprets this as an error, and the build process fails.
Was this change by design? I would prefer not to have to ignore errors in NANT, because it is feasible that other errors could occur and we would be none the wiser. On the other hand, I can't find an option for SVN ADD which says "ignore versioned files". I could write a script filtering by SVN STATUS, but this would be inelegant. At the moment, I am just ignoring errors for the NANT entry that calls SVN ADD.
Regards,
Mark Bertenshaw
[Description: Description: Description: Description: Description: http://www.services.fidessa.com/banneradverts/email-signature-logos/Fidessa-Logo-Email-Signature-Blue.png]<http://www.fidessa.com/>
********************************************************************************************************************************************************************************************
Fidessa plc - Registered office:
Fidessa LatentZero Limited - Registered office:
Fidessa group plc - Registered Office:
|
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.