Bug 364789 - Project Explorer "Link with editor" not working with Java/Groovy files located outside the Java build path
Summary: Project Explorer "Link with editor" not working with Java/Groovy files locate...
Status: CLOSED DUPLICATE of bug 533633
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.2   Edit
Hardware: All All
: P3 normal with 2 votes (vote)
Target Milestone: 4.8 M7   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-25 02:59 EST by Mauro Molinari CLA
Modified: 2018-04-16 15:00 EDT (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mauro Molinari CLA 2011-11-25 02:59:21 EST 
Build Identifier: M20110909-1335

Consider the project attached to bug #364600.

The "Link with editor" feature of the Project Explorer does not work for file MyClass.java. This is true in either cases:
1. if you try it with "Enhanced Java Rendering for Web" on, before MyClass.java disappear (see bug #364600)
2. if you try it with "Enhanced Java Rendering for Web" off

Reproducible: Always

Steps to Reproduce:
1. import the project attached to bug #364600
2. double click on MyClass.java in the root of the project, to open the editor
3. enable "Link with editor" feature in Project Explorer
4. now click on another file or folder in the workspace, then click back in the open editor
5. the selection is not put back on MyClass.java in Project Explorer
6. try to play with the "Enhanced Java Rendering for Web" contents filter of the Project Explorer (see bug #364600) and you'll that the problem persists
7. do the same with the Package Explorer: "Link with editor" works there.
Comment 1 Mauro Molinari CLA 2012-10-30 15:52:29 EDT 
Any news on this? The problem is affecting usability with Gradle tools.
Comment 2 Mickael Istria CLA 2018-04-16 15:00:19 EDT 
Seems like bug 533633 is a dup of this one. But since bug 533633 contains more details, let's mark this one as the dup.

*** This bug has been marked as a duplicate of bug 533633 ***