Thanks all for the advice. Of course I tried launching with -clean and team --> cleanup, to no avail. But I think I figured out the problem. The project points to several linked libraries which are each their own proejct under version control. To optimize performance, I occasionally close these projects while working on the main (also huge) project. I think the refresh problem is simply caused by the fact that one of the linked libraries is in a 'closed' project. Of course, this prompts a gigantic DOH! and slap of the forehead. At an rate, I'm back up and running. Wish I'd tried the obvious thing first! (It would have been nice to have some information in the error message...) Jim Kremens
On 11/15/05, Martin Wood <[EMAIL PROTECTED]> wrote: > > for more information you might want to check the eclipse log file, its > found at workspace/.metadata/.log > > that might give you more information about what is causing the problem. > > as has been said, theres some cleaning you can do thats a lot less > drastic, first is doing an SVN clean, right click project -> team -> > cleanup > > also you can start eclipse with -clean from the command line which may > clear out some bad state that has occurred. > > hope that helps, > > martin > > > >> I have all the latest versions... > >> Here's a question - are there files that I should not put in version > >> control? Like Eclipse's .project file and FDT's .as2_classpath? > >> I've done it both ways and still had the same problems, so I don't > think > >> that's the solution. Just curious... > >> Jim Kremens > > -- > want to know what i think? probably not > > http://relivethefuture.com/choronzon > _______________________________________________ > Flashcoders mailing list > [email protected] > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
