| Summary: | "Link with Editor" functionality not working with hierarchical project presentation | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Nicolas Peifer <peifer> | ||||||
| Component: | UI | Assignee: | Platform-UI-Inbox <Platform-UI-Inbox> | ||||||
| Status: | RESOLVED MOVED | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | alexander.isaak, arjan.tijms, dct, elecharny, kenneth, Lars.Vogel, mauromol, psuzzi | ||||||
| Version: | 4.7.2 | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
|
Description
Nicolas Peifer
Created attachment 272579 [details]
cannot reproduce the issue
System information:
Eclipse SDK
Version: Photon (4.8)
Build id: I20180206-2000
OS: Mac OS X, v.10.13.2, x86_64 / cocoa
Could you please provide specific steps to reproduce the issue?
I had the same Problem. Setup in Project explorer: - One working set, with one Maven-Project and one MavenModule with two Files. - Project presentation=hierarchical - Projects closed with "Collapse all" - "Link with Editor" is activated Screenshot attached. Link With Editor will work again once the Maven project is expand. Spring Tool Suite Version: 3.9.4.RELEASE Build Id: 201804120921 Platform: Eclipse Oxygen.3a (4.7.3a) Created attachment 274102 [details]
WorkingSet with MavenModule Link wirh Editor Bug
Still a problem in 2019-12_M1 Status with "Link with Editor" enabled with Java projects: Project Presentation Top Level Elements Note ---------------------------------------------- Flat Projects Works but very slow >5seconds Hierachical Projects Works but very slow >5seconds Flat Working Sets Work as expected Hierachical Working Sets Not working at all, no effect in view Info to comment 4. In my workspace I have 25 working sets with in total 415 projects Re-test with eclipse-SDK-I20200124-1800-win32-x86_64 I see no problem with slow updates anymore. However "Link With Editor" using Project Presentation="Hierarchical" and Top Level Elements="Working Sets" still does not work at all. I also have the same problem, very annoying. Seemingly the code that should focus the project explorer is just not aware of working sets. Since the Payara Tools plug-in does a similar focusing in the project explorer I'll try to experiment a little with the code there. I am having this issue in 4.20. It happens if all projects are collapsed (after clicking on the Collapse All button). Once the projects are explored then "Link with Editor" starts working fine. Same problem here with RCP 2023-03. It was not working either for 2022-06. Typically, if I 'explode' the project to show all the Java files (which is basically impossible with 24 projects, hundreds of modules and tens of thousands directories...), I *can* link with editor, but if the projects or directories are collapsed, then 'link with editor does not work anymore. That was working at some point in the past 2 or 3 years ago?), the 'double arrow' was opening the project and directories to highlight the file in the editor, it's not the case anymore. This is a major issue, it makes Eclipse IDE almost irrelevant when working with many projects and a lot of files (I'm using it for Apache Directory Server,n which has 50 modules and hundreds of packages for thousands of files, plus Apache MINA in 3 versions, plus 10 other projects in a professional env) (In reply to elecharny from comment #9) > Same problem here with RCP 2023-03. It was not working either for 2022-06. > > Typically, if I 'explode' the project to show all the Java files (which is > basically impossible with 24 projects, hundreds of modules and tens of > thousands directories...), I *can* link with editor, but if the projects or > directories are collapsed, then 'link with editor does not work anymore. > > That was working at some point in the past 2 or 3 years ago?), the 'double > arrow' was opening the project and directories to highlight the file in the > editor, it's not the case anymore. > > This is a major issue, it makes Eclipse IDE almost irrelevant when working > with many projects and a lot of files (I'm using it for Apache Directory > Server,n which has 50 modules and hundreds of packages for thousands of > files, plus Apache MINA in 3 versions, plus 10 other projects in a > professional env) Please report to https://github.com/eclipse-platform/eclipse.platform.ui/issues, Bugzilla is not used anymore. (In reply to Lars Vogel from comment #10) > Please report to > https://github.com/eclipse-platform/eclipse.platform.ui/issues, Bugzilla is > not used anymore. So are all open bugs in Bugzilla being trashed? No migration, no closing at all...? Well, reported to GH, *but*: https://wiki.eclipse.org/Bug_Reporting_FAQ At some point, get the facts together! Someone who is looking for the way to report bugs will be directed to BugZilla on the official Eclipse web site... (In reply to elecharny from comment #12) > Well, reported to GH, *but*: https://wiki.eclipse.org/Bug_Reporting_FAQ > > At some point, get the facts together! Someone who is looking for the way to > report bugs will be directed to BugZilla on the official Eclipse web site... I updated https://wiki.eclipse.org/Bug_Reporting_FAQ |