|
|
|
| Re: Error Starting eclipse "eclipse unable to read workbench state" [message #167076 is a reply to message #167068] |
Tue, 18 April 2006 23:14   |
 Dake Gu
Messages: 17
Registered: July 2009 |
Junior Member |
|
|
you cannot share "workspace/.metadata" for two different eclipse version.
You can create a separate workspace for wtp1.5 and import existing projects.
You don't need import project one by one, which is a nightmare before
eclipse3.1.
After eclips eversion 3.1, you can locate a root folder and import projects
in sub folders.
I have the same situation: 60+ projects in my workspace.
Create a new workspace won't lose CVS information. Right click on
"project->share...", it will find the existing "CVS" folder and ask you to
use the existing cvs info.
"Jonathan Barnes" <jonathan@ehawaii.gov> wrote in message
news:e23o1v$jue$1@utils.eclipse.org...
> Thanks for the response. Well I tried to do what you explained, but
> unfortunately it did not work. The same error occurs on startup.
>
> I now have 2 completely different versions installed
>
> eclipse v3.1.2 wtp 1.0.1
> eclipse v3.3M4 wtp 1.5M4
>
> as well as 3 separate workspaces.
>
> It seems the problem is with one of the projects in my workspace.
>
> If I have a clean workspace (no projects) then I can use the J2EE
> perspective and restart without issues. when I switch to another
> perspective then the problem startup problem occurs.
>
> unfortunately I have 15+ active projects going with at least 10 that have
> uncommitted changes to cvs.
>
> Given that this problem seems to have something to do with one or more of
> the projects is this still something that should be reported as a bug?
>
> Right now I think I am going to stick with using the 3.2M4-1.5M4 version
> and just try to import each project one by one and restart each time to
> see if I can find out any more info.
>
> If anyone has any other suggestions for recovering my existing workspaces
> I would love to hear them as this import and re-configure for each project
> is going to be a slow an painful process.
>
> -Jonathan
>
> David Williams wrote:
>> On Tue, 18 Apr 2006 16:02:37 -0400, Jonathan Barnes
>> <jonathan@ehawaii.gov> wrote:
>>
>>
>>>
>>> The logs state that there is a missing class
>>> Caused by: java.lang.NoClassDefFoundError:
>>> org/eclipse/jst/j2ee/internal/project/J2EEProjectUtilities
>>>
>>
>> Sounds like someone made a mistake and didn't "migrate" code correctly.
>> My guess is its not as serious as it sounds, that some previous
>> state/view
>> is trying to be "restored", but the previous state/view has been changed.
>>
>> You can probably "fix" it, by "opening" the J2EE perspective (even if
>> errors)
>> and then saying "reset perspective". That usually "migrates" things to
>> the
>> new code just fine.
>>
>> If this doesn't work .. a bug report would be in order.
>> And, even if this works ... sorry for the poor "upgrade" experience.
|
|
|
| Re: Error Starting eclipse "eclipse unable to read workbench state" [message #167084 is a reply to message #167076] |
Wed, 19 April 2006 02:38 |
Jonathan Barnes
Messages: 10
Registered: July 2009 |
Junior Member |
|
|
good to know about not sharing workspaces among different versions...
I was importing one by one in an attempt to locate the breaking point which was
causing my environment to be screwed up e.g.
1 Import project1
2 do refactor -> move -> default location
3 fix any other build problems
4 exit eclipse
5 restart and see if the error occurs
6 Import project2
etc....
a few days ago I was importing all projects, but then the startup errors kept
coming back. Now I am just being cautious and doing them one at a time whenever
I need to touch one of the projects.
Thanks for all the help on this though.
Hey do you think it could be that I am importing the "Server" project which
holds all the server configs? I don't know why but during one of my reload
everything attempts I think I got the feeling that using an existing server
config for a new server definition may have triggered the problem, unsure though
and am unwilling to TRY to get it to break again as it has already sucked up 40+
hrs just trying to get going again
Anyway thanks again.
-Jonathan
david wrote:
> you cannot share "workspace/.metadata" for two different eclipse version.
>
> You can create a separate workspace for wtp1.5 and import existing projects.
>
> You don't need import project one by one, which is a nightmare before
> eclipse3.1.
> After eclips eversion 3.1, you can locate a root folder and import projects
> in sub folders.
> I have the same situation: 60+ projects in my workspace.
>
> Create a new workspace won't lose CVS information. Right click on
> "project->share...", it will find the existing "CVS" folder and ask you to
> use the existing cvs info.
>
>
>
> "Jonathan Barnes" <jonathan@ehawaii.gov> wrote in message
> news:e23o1v$jue$1@utils.eclipse.org...
>> Thanks for the response. Well I tried to do what you explained, but
>> unfortunately it did not work. The same error occurs on startup.
>>
>> I now have 2 completely different versions installed
>>
>> eclipse v3.1.2 wtp 1.0.1
>> eclipse v3.3M4 wtp 1.5M4
>>
>> as well as 3 separate workspaces.
>>
>> It seems the problem is with one of the projects in my workspace.
>>
>> If I have a clean workspace (no projects) then I can use the J2EE
>> perspective and restart without issues. when I switch to another
>> perspective then the problem startup problem occurs.
>>
>> unfortunately I have 15+ active projects going with at least 10 that have
>> uncommitted changes to cvs.
>>
>> Given that this problem seems to have something to do with one or more of
>> the projects is this still something that should be reported as a bug?
>>
>> Right now I think I am going to stick with using the 3.2M4-1.5M4 version
>> and just try to import each project one by one and restart each time to
>> see if I can find out any more info.
>>
>> If anyone has any other suggestions for recovering my existing workspaces
>> I would love to hear them as this import and re-configure for each project
>> is going to be a slow an painful process.
>>
>> -Jonathan
>>
>> David Williams wrote:
>>> On Tue, 18 Apr 2006 16:02:37 -0400, Jonathan Barnes
>>> <jonathan@ehawaii.gov> wrote:
>>>
>>>
>>>> The logs state that there is a missing class
>>>> Caused by: java.lang.NoClassDefFoundError:
>>>> org/eclipse/jst/j2ee/internal/project/J2EEProjectUtilities
>>>>
>>> Sounds like someone made a mistake and didn't "migrate" code correctly.
>>> My guess is its not as serious as it sounds, that some previous
>>> state/view
>>> is trying to be "restored", but the previous state/view has been changed.
>>>
>>> You can probably "fix" it, by "opening" the J2EE perspective (even if
>>> errors)
>>> and then saying "reset perspective". That usually "migrates" things to
>>> the
>>> new code just fine.
>>>
>>> If this doesn't work .. a bug report would be in order.
>>> And, even if this works ... sorry for the poor "upgrade" experience.
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03475 seconds
] 
Search
Help
Register
Login
Home
