Bugzilla – Full Text Bug Listing
| Summary: | Eclipse Indigo doesn't display icon decorations in navigator view | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [WebTools] WTP Java EE Tools | Reporter: | Missing name <cgamache> | ||||||
| Component: | jst.j2ee | Assignee: | Dimitar Giormov <dimitar.giormov> | ||||||
| Status: | RESOLVED WONTFIX | QA Contact: | Chuck Bridgham <cbridgha> | ||||||
| Severity: | major | ||||||||
| Priority: | P3 | CC: | daniel_megert, ecdragon, gregory.amerson, igerly.work, remy.suen, thatnitind | ||||||
| Version: | 3.3 | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows 7 | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
|
Description
Missing name
I presume the feature is missing in both Helios Eclipse Classic and Indigo Eclipse Classic? The Eclipse SDK never showed decorators (see bug 2108) and this won't change. AFAIK WTP added them at some point and now this seems broken. Thanks for the clarification. It is a useful feature which I have grown to depend on. I'm having difficulty finding the best place to report this bug. Any suggestions? It's the "Problem Marker Resource Decorator" from org.eclipse.jst.j2ee.navigator.ui in Helios, removed to fix bug 291498. (In reply to comment #4) > It's the "Problem Marker Resource Decorator" from > org.eclipse.jst.j2ee.navigator.ui in Helios, removed to fix bug 291498. The rabbit hole runs deep here. Working with maven projects in project explorer, the decorators are present on the folders in the "folder tree" section, but missing from the .java files themselves. Is the plan to move the decorators back? (In reply to comment #5) > The rabbit hole runs deep here. Working with maven projects in project > explorer, the decorators are present on the folders in the "folder tree" > section, but missing from the .java files themselves. Please provide a screenshot. I've noticed this problem on all resources even in the package explorer. So when you have a WTP build validation marker on an XML file, you will see it on the parent folder but not on the resource. Created attachment 207756 [details]
Project Explorer on Indigo
Notice no decorator on Foo.java
Created attachment 207757 [details]
Project Explorer on Helios
Notice the decorator on Bar.java
Comment on attachment 207756 [details]
Project Explorer on Indigo
er... Bar.java :)
I've tried substituting org.eclipse.jst.j2ee.navigator.ui_1.1.501.v201107261503.jar and org.eclipse.ui.navigator_3.5.100.v20110809-2227.jar content with the content of the relevant jars from the 3.7.0 release, and after some hiccuping (and resetting) of the perspectives, Eclipse seems to be up and running and the decorations are back. Dimitar, as this (at least as originally reported) is the result of fixing bug 291498, should it be resolved as wontfix (working as intended)? Thanks Nitin, you are right. A little bit of explanation here. Having the decorations in navigator in Eclipse prior to Indigo SR1 was caused by using a wrong class as a problem decorator in java ee plugins. Further more the decorations were available only in Java EE distribution of eclipse (because of the location where the problem decorator definition was). You can check for more details here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=291498 So what can you do now: You can open a separate enhancement bug for the platform if you want to see problem markers in the navigator. About the error markers on the xml I think the right component should be common validation in WTP Best regards, Dimitar (In reply to comment #14) > So what can you do now: > You can open a separate enhancement bug for the platform if you want to see > problem markers in the navigator. That would be bug 2108. As per comment 3, note that the 'Navigator' view is no longer actively worked on and we, the Platform UI team, have no plans to add new features to that view. (In reply to comment #14) > About the error markers on the xml I think the right component should be common > validation in WTP Comment 5 made reference to the same behavior on a .java file. There must be another decorator at play. (In reply to comment #15) > > That would be bug 2108. As per comment 3, note that the 'Navigator' view is no > longer actively worked on and we, the Platform UI team, have no plans to add > new features to that view. Ouch. I have relied on the Navigator view (I never use the Project Explorer for various reasons) every day for years to do Java web app development. I'm flabbergasted. Surely I'm not the only engineer who prefers it to the Project Explorer? What are my options? Do I have the option of contributing to Eclipse and maintaining that view myself? (In reply to comment #17) > (In reply to comment #15) > > > > That would be bug 2108. As per comment 3, note that the 'Navigator' view is no > > longer actively worked on and we, the Platform UI team, have no plans to add > > new features to that view. > > Ouch. I have relied on the Navigator view (I never use the Project Explorer for > various reasons) every day for years to do Java web app development. I'm > flabbergasted. > > Surely I'm not the only engineer who prefers it to the Project Explorer? > > What are my options? Try the Package Explorer. (In reply to comment #17) > (In reply to comment #15) > > > > That would be bug 2108. As per comment 3, note that the 'Navigator' view is no > > longer actively worked on and we, the Platform UI team, have no plans to add > > new features to that view. > > Ouch. I have relied on the Navigator view (I never use the Project Explorer for > various reasons) every day for years to do Java web app development. I'm > flabbergasted. > > Surely I'm not the only engineer who prefers it to the Project Explorer? > > What are my options? Do I have the option of contributing to Eclipse and > maintaining that view myself? Clearly I'm in the same boat. The suggestion I've received from folks is to simply rally the community around the feature's restoration by creating an enhancement bug report. Have your fellow engineers who have come to rely on the navigator vote for this issue. Just because it gets 1000 votes doesn't mean it will be restored, but there is a far better chance to influence the process through community response. (In reply to comment #17) > Surely I'm not the only engineer who prefers it to the Project Explorer? > > What are my options? Do I have the option of contributing to Eclipse and > maintaining that view myself? There's prefer, and there's maintainable. We walked away from the ResourceNavigator >3 years ago. As for options. 1) Use the Project Explorer, and vote for the last of the functionality that's missing (easily creating filters was one, I believe). Or contribute it, if you were considering hacking the ResourceNavigator. 2) use the Package Explorer Both the Project Explorer and Package Explorer are in the current development streams. 3) The ResourceNavigator code is still available, it's in /org.eclipse.ui.ide/src/org/eclipse/ui/views/navigator/ResourceNavigator.java. As it is, we wouldn't consider changing that in org.eclipse.ui.ide in 3.x. But, you could try and refactor it into its own bundle, org.eclipse.ui.views.navigator, and then enhance it there. See http://wiki.eclipse.org/Platform_UI/How_to_Contribute for information on getting a hold of the Platform UI git repos (they're also available from http://github.com/eclipse ). There is a large learning curve here, though, as it is API and has to maintain behaviour. PW *** Bug 362209 has been marked as a duplicate of this bug. *** |