Strange, "svn update trunk --non-interactive" left the empty "modules/tools" directory. Probably it depends on svn client version and / or configuration.
Thanks, 2007/5/2, Ivan Popov <[EMAIL PROTECTED]>:
Alexei, I used 'svn update' in command prompt without any additional options and it removed tools directory from classlib component, so I have no problems with building/cleaning classlib. Thanks. Ivan On 5/2/07, Alexei Zakharov <[EMAIL PROTECTED]> wrote: > It should also be mentioned that the empty modules/tools dir needs to > be removed by hand since "ant clean" complains about missing > modules/tools/build.xml (or smth. like it). At least I wasn't able to > move any further until I removed it. > > Regards, > > 2007/5/2, Tim Ellison <[EMAIL PROTECTED]>: > > Ivan Popov wrote: > > > Thanks, Tim. It's a long waiting solution, it was discussed several > > > times and I'd like to see the problem with duplicating modules is > > > finally resolved. > > > > > > AFAIK, nobody worked on jdktools copies of tools and launcher modules > > > except of applying some of classlib's patches and updating build > > > scripts. So, if there are conflicts in merging sources, the easier way > > > might be just to move new sources from classlib and leave current > > > build scripts in jdktools. > > > > Yep, that's what I did (at r534390). > > > > The classlib 'clean' will complain about remaining files next time you > > run it because the tools sources have disappeared, but it will only > > complain once.
-- Alexei Zakharov, Intel ESSD
