On Wed, Jul 29, 2009 at 4:31 PM, Uwe Schindler<u...@thetaphi.de> wrote:
> My suggestion was to write the build script in a way that it checks out the > branch with the same revision number as the current base dir (trunk). I think this would work, as long as we always commit top-level and back-compat tag in one transaction (commit)? (And, even if we don't do it as one commit, the risk that someone happens to do a checkout between the two commits is presumably negligible). > Alternatively instead of putting a tag name into common-build.xml, it could > be the revision number. So it would check out …/branches/ > lucene_2_4_back_compat_tests with the revision given in common-build. This would also be better than what we have today (saves the extra "svn copy" step), but if we can make the first approach work that's even better! Mike --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
