Bug 345218 - Java perspective is completely empty, no views, editors, NOTHING
Summary: Java perspective is completely empty, no views, editors, NOTHING
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows 7
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2011-05-09 18:51 EDT by Chris Gage CLA
Modified: 2011-05-19 02:07 EDT (History)
4 users (show)

See Also:


Attachments
metadata log for #345218 (17.59 KB, text/plain)
2011-05-10 08:25 EDT, Chris Gage CLA
no flags Details
Configuration as requested (194.49 KB, text/plain)
2011-05-18 18:47 EDT, Chris Gage CLA
no flags Details
workspace metadata log (150.05 KB, text/plain)
2011-05-18 18:47 EDT, Chris Gage CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Gage CLA 2011-05-09 18:51:25 EDT
Build Identifier: Version: Helios Service Release 2 Build id: 20110301-1815

I have been using this build (Helios Release 1, J2EE flavour) since early release to Friends of Eclipse last year.  My current project uses XML, XSLT and Java, and I had some problems with the XML editor going into a loop opening a file which is not well-formed, so I did Help->Check for Updates, and accepted all the prompts, and restarted.  After the restart, the Java perspective still exists, but there is no content in the perspective, ie no views, editors etc.  I'll have to go back to Release 1 as I am 100% broken and can do no work at all.

Reproducible: Always

Steps to Reproduce:
1. Start eclipse
2. Open perspective->Java
3. Empty
4. Reset Perspective
5. Empty
Comment 1 Paul Webster CLA 2011-05-09 18:59:01 EDT
Have a look at your <workspace>/.metadata/.log

PW
Comment 2 Chris Gage CLA 2011-05-09 22:23:06 EDT
(In reply to comment #1)
> Have a look at your <workspace>/.metadata/.log
> 
> PW

In trying to fix the problem (or more precisely to make it go away), one of the things I tried was to delete the metadata folder, and then re-import the projects.

It did not fix the problem with the updated Eclipse, but I was able to get started again with a newly downloaded base Java Eclipse Version: Helios Service Release 2 Build id: 20110218-0911.  Then I switched back to the broken one, and it went empty again, and now it is empty with the newly downloaded build as well, so I am truly hosed. 

I think the updated build is corrupting the metadata somehow.  I assume/hope I'll be able to delete the metadata again and get it back, which I'll try tomorrow after I have downloaded the latest JEE Eclipse flavour.
Comment 3 Dani Megert CLA 2011-05-10 01:28:27 EDT
Please attach the .metadata/.log as already requested by Paul.

>I have downloaded the latest JEE Eclipse flavour.
Please paste the download URL here?

Also try the following:
1. Window > Preferences
2. General > Perspectives
3. select 'Java' in the list
4. is the 'Reset' button enabled?
   - if so, it means the defaults got changed somehow
     ==> click on it
5. click 'OK'
6. back in the Java perspective select Window > Reset Perspective...
7. click 'OK'
==> is it back to normal now?
Comment 4 Chris Gage CLA 2011-05-10 08:25:22 EDT
Created attachment 195201 [details]
metadata log for #345218
Comment 5 Chris Gage CLA 2011-05-10 08:28:24 EDT
I just attched the metadata log.

I always download from the Friends of Eclipse mirror, I am downloading JEE SR2 as I type,
http://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/helios/SR2/eclipse-jee-helios-SR2-win32.zip

I went into that preferences section you mentioned (for the first time ever), and Reset was not enabled.

Background on me: I am not a beginner here. I am a retired IBMer and have been using Eclipse inside and outside IBM since WSAD4.0 (2001). I was development team lead in RTP on IBM's very first shipped Java product (Feb 1997).
Comment 6 Remy Suen CLA 2011-05-10 08:36:15 EDT
Comment on attachment 195201 [details]
metadata log for #345218

If you start with the OSGi console, do you see any JDT bundles there? Are they being resolved properly?
Comment 7 Dani Megert CLA 2011-05-10 08:41:06 EDT
(In reply to comment #6)
> Comment on attachment 195201 [details]
> metadata log for #345218
> 
> If you start with the OSGi console, do you see any JDT bundles there? Are they
> being resolved properly?

or start with -debug.

It looks like the JDT bundles don't get resolved. Are you using the original download or do you mix it with other bundles?
Comment 8 Chris Gage CLA 2011-05-10 09:00:28 EDT
(In reply to comment #7)
> (In reply to comment #6)
> > Comment on attachment 195201 [details] [details]
> > metadata log for #345218
> > 
> > If you start with the OSGi console, do you see any JDT bundles there? Are they
> > being resolved properly?
> 
> or start with -debug.
> 
> It looks like the JDT bundles don't get resolved. Are you using the original
> download or do you mix it with other bundles?

I am only minimally aware of the OSGI console.  What do I need to enter on the console to see what you want?  I did a "status" and got a huge amount of output which exceeded my commandline buffer, but I could increase it and send the result if that would be useful.

But I have to go to work now!
Comment 9 Dani Megert CLA 2011-05-10 10:29:49 EDT
> I am only minimally aware of the OSGI console. 
Use -debug. That's easier.

Are you using the original download or do you mix it with other bundles?
Comment 10 Dani Megert CLA 2011-05-17 04:37:29 EDT
Nothing we can do without further information.
Comment 11 Chris Gage CLA 2011-05-17 07:33:31 EDT
(In reply to comment #10)
> Nothing we can do without further information.

I do not do anything additional.  I have been using this particular build since Helios early release, and apart from the pesky XML editor, I have not encountered any problems.

I will try again this evening.  I will try the -debug option, but it would help if you could give me an idea of what to look for.
Comment 12 Dani Megert CLA 2011-05-17 07:35:46 EDT
(In reply to comment #11)
> (In reply to comment #10)
> > Nothing we can do without further information.
> 
> I do not do anything additional.  I have been using this particular build since
> Helios early release, and apart from the pesky XML editor, I have not
> encountered any problems.
> 
> I will try again this evening.  I will try the -debug option, but it would help
> if you could give me an idea of what to look for.

Once -debug is used I hope to get a list of bundles that can't be loaded.
Comment 13 Chris Gage CLA 2011-05-17 18:04:11 EDT
I started with eclipse -debug, and second command-line window opened, and this is what I saw in it before eclipse came up:

-Dosgi.requiredJavaVersion=1.5
-Xms40m
-Xmx512m
-XX:MaxPermSize=256m
-Djava.class.path=C:\eclipseOldHelios\\plugins/org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar
Install location:
    file:/c:/eclipseOldHelios/
Configuration file:
    file:/c:/eclipseOldHelios/configuration/config.ini loaded
Configuration location:
    file:/c:/eclipseOldHelios/configuration/
Framework located:
    file:/c:/eclipseOldHelios/plugins/org.eclipse.osgi_3.6.2.R36x_v20110210.jar
Framework classpath:
    file:/c:/eclipseOldHelios/plugins/org.eclipse.osgi_3.6.2.R36x_v20110210.jar
Splash location:
    C:\eclipseOldHelios\\plugins\org.eclipse.platform_3.6.2.v201102101200\splash.bmp
Debug options:
    file:/C:/eclipseOldHelios/.options not found
Time to load bundles: 16
Starting application: 1201
Application Started: 22729

At this point my empty perspective comes up, and there is more or lerss nothing left to do.
Comment 14 Dani Megert CLA 2011-05-18 02:06:18 EDT
And nothing is written to the console or into .log?

Please attach the configuration:
1. Help > About Eclipse SDK
2. click 'Installation Details'
3. click 'Configuration' tab
4. click 'Copy to Clipboard'
5. paste this into a new file
6. attach the file here
Comment 15 Chris Gage CLA 2011-05-18 18:47:04 EDT
Created attachment 196062 [details]
Configuration as requested
Comment 16 Chris Gage CLA 2011-05-18 18:47:56 EDT
Created attachment 196063 [details]
workspace metadata log
Comment 17 Chris Gage CLA 2011-05-18 18:51:31 EDT
Interesting thing I just found out ... Closing the Java perspective and reopening it clears the problem.  So at least I have a workaround...
Comment 18 Dani Megert CLA 2011-05-19 02:07:46 EDT
(In reply to comment #17)
> Interesting thing I just found out ... Closing the Java perspective and
> reopening it clears the problem.  So at least I have a workaround...

That sounds strange. Looking at the .log and the configuration, it looks like JDT UI is not activated (still starting) and hence I don't see how the Java perspective would show up.

After reopening, does it work then i.e. can you exit and restart and the perspective is there? If not, does the workaround work again? If so, can you attach the configuration after that?