Bug 489418 - Cannot find navigator content extension (using triggerPoints) for object "<null>"
Summary: Cannot find navigator content extension (using triggerPoints) for object "<nu...
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 4.5.2   Edit
Hardware: PC Linux
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-11 05:33 EST by Kevin Hagel CLA
Modified: 2019-10-09 15:30 EDT (History)
3 users (show)

See Also:


Attachments
Project explorer is distorted (5.81 KB, image/png)
2016-09-30 14:20 EDT, Vasili Gulevich CLA
no flags Details
Session log illustrating the problem (6.04 KB, text/plain)
2016-09-30 14:23 EDT, Vasili Gulevich CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Hagel CLA 2016-03-11 05:33:47 EST
in the latest mars:

eclipse.buildId=4.5.2.M20160212-1500
java.version=1.8.0_74
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments:  -product org.eclipse.epp.package.rcp.product
Command-line arguments:  -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.rcp.product

Ubuntu 14.04


Create a simple java project.  Add a text file, textFile.txt or whatever to the src/ directory.

Go to the Project Explorer.  In the Customize View turn off the filtering of Java Output Folders

You should be seeing the bin/ folder in the Project Explorer

Turn on Project > Build Automatically
invoke Project > Clean

in the bin folder you will not see textFile.txt, in fact you will see an empty position under the bin folder where this file should be.
Nothing is written to the logs.



We are developing a custom plugin that uses common navigator.  When launching a child eclipse instance we see this in the parent console


Cannot find navigator content extension (using triggerPoints) for object "<null>" parent path: "F/test1/bin".  Check that you have an expression for this object in a navigatorContent triggerPoints or enablement.

Creating a java project in the child instance sees the same message for its output folder.


The cleaned folder is not closed/collapsed when cleaned as it was in Luna, instead Mars tries to keep it open.

Refreshing the folder fixes the issue, the missing file shows up and the empty (null) location disappears.

Collapsing the folder fixes the issue.
Comment 1 Vasili Gulevich CLA 2016-09-30 14:20:08 EDT
Created attachment 264517 [details]
Project explorer is distorted

This can be reproduced easier.

1. Download a vanilla Neon or Oxygen for Committers.
2. Launch in a fresh workspace
3. Close Java perspective
4. Open Resources perspective (to avoid JDT interference)
5. Create a following  workspace structure:
-------------------------
Project (General project, no natures)
  folder1
    file1.txt (empty file)
  folder2
-------------------------
6. Move file1.txt from folder1 to folder2 via drag and drop
7. MOve file2.txt from folder2 to folder1 via drag and drop
8. Repeat 6-7 a few times (usually two times are enough)

Expected:
Original workspace hierarchy is shown

Actual:
An extra empty row is added to the tree:
-------------------------
Project
  folder1
    
    file1.txt
  folder2
-------------------------
Comment 2 Vasili Gulevich CLA 2016-09-30 14:23:25 EDT
Created attachment 264518 [details]
Session log illustrating the problem

Attached is a session log which also reveals UI freeze involving a set of progress dialogs (performing resource move). This freeze may be unrelated to the bug.

There is no stack trace provided for "Cannot find navigator content extension" error.
Comment 3 Eclipse Genie CLA 2019-10-09 15:30:53 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.