Vladimir, Federated build does "svn switch" for each "working_*" subdirectory, pointing to corresponding svn location. You can do the same manually. For example:
cd working_classlib svn switch https://svn.apache.org/repos/asf/harmony/enhanced/classlib/trunk Then you'll be able to update your local copy by usual "svn update". Thanks. Ivan On 3/28/07, Vladimir Beliaev <[EMAIL PROTECTED]> wrote:
Does not work... does not work... I wrote about this... :( >> $ cd trunk/working_classlib >> $ svn cleanup >> $ svn update >> At revision 520884. and you proposed me almost the same (cvn cleanup can be ignored): > 1: > cd trunk/working_classlib > svn up > cd ../.. May be I'm not clear here: mentioned 'svn update' does nothing but print the current revision - no new files actually bringovered.... Looks like I have to get familiar with federated build structure and find the "patch" for "ant populate_sources"... Thanks anyway Vladimir Beliaev Egor Pasko wrote: > On the 0x2A0 day of Apache Harmony Vladimir Beliaev wrote: >> Hello, >> >> > so doing the cleanup and an update should be fine. >> >> I think I did not do myself clear. Let me say in other words: >> >> - I'm doing "ant populate_source" & I got the error... >> >> - I believe this means some of sources were not populated (checked out). >> >> - so 'svn cleanup; svn update' does not work - some sources may be >> missed as result... >> >> I've double checked (sorry I do not spend time reading through >> documentation & inspecting build files) directly following your >> recommendation - simulating the case when "populate sources" was >> broken at very beginning (like it was not run at all): >> >> $ svn co https://svn.apache.org/repos/asf/harmony/enhanced/trunk >> A trunk/NOTICE >> A trunk/LICENSE >> A trunk/common_resources >> A trunk/working_vm >> A trunk/COPYRIGHT >> A trunk/working_jdktools >> A trunk/THIRD_PARTY_NOTICES.txt >> A trunk/working_classlib >> A trunk/build.xml >> Checked out revision 520880. >> $ cd trunk/working_classlib >> $ svn cleanup >> $ svn update >> At revision 520884. >> $ cd .. >> $ svn update >> At revision 520884. >> >> So no new sources were got of 'ant populate_source' was not executed >> (or broken at very beginning). >> >> So my question is still valid - what is the right way to proceed (not >> restart) if 'ant populate_source' fails? > > 1: > cd trunk/working_classlib > svn up > cd ../.. > > 2: > cd trunk/working_vm > svn up > cd ../.. > > >> Thanks >> Vladimir Beliaev >> >> Geir Magnusson Jr. wrote: >>> On Mar 14, 2007, at 4:04 PM, Nathan Beyer wrote: >>> >>>> If you haven't deleted the contents of the working_* folders, you may >>>> want to try running "svn cleanup" on them. This will cleanup any SVN >>>> file locks that might be blocking access. Another option is to run >>>> "svn update" from within the working_* folders individually. >>>> >>>> What OS are you running SVN on? If it's windows, you may want to try >>>> checking out the top folders closer to the root of the drive. There >>>> can be some trouble with windows paths that are very long. >>> Good suggestions - I can't think of anything else either. IIRC, >>> populate_source is a checkout, so doing the cleanup and an update >>> should be fine. >>> geir >>> >>>> -Nathan >>>> >>>> On 3/14/07, Vladimir Beliaev <[EMAIL PROTECTED]> wrote: >>>>> Hello, >>>>> >>>>> may be I'm asking the known things, still.. >>>>> >>>>> Issue: >>>>> >>>>> I'm building Harmony according to instruction at: >>>>> http://harmony.apache.org/quickhelp_contributors.html >>>>> >>>>> I'm doing "Populating the VM and ClassLibrary Source Trees" step >>>>> which means executing "ant populate_source" from <trunk> directory >>>>> >>>>> This "ant populate_source" fails from time to time... >>>>> >>>>> So I need to remove <trunk> & start from scratch (takes time) - >>>>> issue. >>>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >>>>> >>>>> Question: >>>>> >>>>> Could you share a right command to do if "ant populate_source" >>>>> failed? >>>>> >>>>> Error output: >>>>> >>>>> Often I get something like: >>>>> >>>>> [exec] svn: REPORT request failed on '/repos/asf/!svn/vcc/default' >>>>> [exec] svn: REPORT of '/repos/asf/!svn/vcc/default': >>>>> Compressed response was truncated (_https://svn.apache.org) >>>>> >>>>> Today I get: >>>>> >>>>> [exec] svn: Can't move >>>>> 'modules/text/src/main/java/org/apache/.svn/tmp/entries' >>>>> to >>>>> 'modules/text/src/main/java/org/apache/.svn/entries': >>>>> Permission denied >>>>> >>>>> Thanks >>>>> Vladimir Beliaev >>>>> >>>>> >> >
