[news.eclipse.tools] Re: Possible to recover from corrupt workspace (.tr

["Andrew McCullough" <mccull1NOSPAMPLEASE@xxxxxxxxxx>]

Assuming no one gives you a good answer on recovering the workspace:

You should be able to import your projects from the old workspace into a new
one (File-->Import-->Existing Project).   That should preserve everything
you "really" need - minus the preferences and such.

Alternatively, if you post the specific errors from your .log file, someone
may be able to suggest a better solution.

-Andrew


"Eric Rizzo" <eric.rizzo@xxxxxxxxxxx> wrote in message
news:3E48153D.1090805@xxxxxxxxxxxxxx
> I've found some rumblings about corrupt workspaces on the newsgroups and
> bug list. Specifically, http://dev.eclipse.org/bugs/show_bug.cgi?id=3128
> talks about the .tree file being corrupt. My situation appears to be
> almost (if not exactly) the same as described in bug 3128 - I had
> OutOfMemory errors right before exiting Eclipse, and the shutdown
> reported an "Internal error."
> Now my workspace won't start up, and I've got 2-3 days' worth of
> uncommitted changes in there that I'm trying to salvage. Is there any
> hope of getting my workspace to at least come up so I can determine
> which files I need to grab that haven't been committed to CVS? Ideally,
> I'd like to get all my preferences, launch configs, etc, but that's
> icing on the cake at this point.
>
> Does anyone have a way to recover from this type of corrupt workspace?
>
> TIA,
> Eric
> --
> Eric Rizzo
> Software Architect
> Jibe, Inc.
> http://www.jibeinc.com
>
>