Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 334298

Summary: Unable to find view with id: org.eclipse.wst.jsdt.ui.PackageExplorer
Product: [WebTools] JSDT Reporter: Chris Jaun <cmjaun>
Component: GeneralAssignee: Nitin Dahyabhai <thatnitind>
Status: RESOLVED FIXED QA Contact: Nitin Dahyabhai <thatnitind>
Severity: normal    
Priority: P3 CC: david_williams
Version: 3.2.3Flags: david_williams: pmc_approved+
thatnitind: pmc_approved? (raghunathan.srinivasan)
thatnitind: pmc_approved? (naci.dai)
thatnitind: pmc_approved? (deboer)
thatnitind: pmc_approved? (neil.hauge)
thatnitind: pmc_approved? (kaloyan)
cmjaun: review+
Target Milestone: 3.2.3   
Hardware: PC   
OS: Windows XP   
Whiteboard: PMC_approved
Attachments:
Description Flags
moves the view definition back none

Description Chris Jaun CLA 2011-01-13 13:33:25 EST
Unable to find view with id: org.eclipse.wst.jsdt.ui.PackageExplorer, when creating perspective org.eclipse.wst.jsdt.ui.JavaPerspective


Saw the above error in log after changing to the JavaScript perspective.
Comment 1 Nitin Dahyabhai CLA 2011-01-13 17:13:32 EST
Created attachment 186792 [details]
moves the view definition back

In 3.2.0, we revamped our Project Explorer contributions significantly, but didn't have time to address the Script Explorer.  Toward the end, I moved the view's definition into the test plug-in and made the P.E. the default in our perspective.  Bug 329725 involved rebuilding the view so that it basically acted like the Project Explorer if it was solely displaying resources and our contributions, and that was put into M4 and mostly into 3.2.3.  Putting the view definition back will not introduce any strings (they were not removed), nor change what the default is in our perspective, it will simply rectify what is otherwise a curious feature omission in between 3.1 and 3.3.
Comment 2 Nitin Dahyabhai CLA 2011-01-14 16:03:44 EST
*Explain why you believe this is a stop-ship defect. Or, if it is a "hotbug" (requested by an adopter) please document it as such.

Opening/resetting the JavaScript perspective will always log this output.

*Is there a work-around? If so, why do you believe the work-around is insufficient?

Installing our test plug-ins from the unit test download would be a workaround, but only among the most lenient of definitions.

*How has the fix been tested? Is there a test case attached to the bugzilla record? Has a JUnit Test been added?

The view has been tested by me.

*Give a brief technical overview. Who has reviewed this fix?

Patch moves the view contribution out of the test plug-in and back into our main UI plug-in.  The code and everything else about the view is already in place.

*What is the risk associated with this fix?

Low.
Comment 3 Nitin Dahyabhai CLA 2011-01-19 14:47:41 EST
Released