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

Bug 350367

Summary:	[Model] It's impossible to override the Eclipse project name in IDE using IWorkbenchAdapter
Product:	[Eclipse Project] Platform	Reporter:	Hemant Singh <Hemant.Singh>
Component:	IDE	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P5	CC:	pwebster, remy.suen
Version:	3.5.1
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:	stalebug

Description Hemant Singh

2011-06-26 01:21:15 EDT

Build Identifier: 20110218-0911

We want to provide custom IWorkbenchAdapter for the IProject, so that we have ability to show custom project name, depending on various other project attributes. We can easily do this for one view like Project Explorer by providing my own navigatorContent which provides label for IProject, but there are many other places like clean projects dialog(org.eclipse.ui.internal.ide.dialogs.CleanDialog) which uses WorkbenchLabelProvider to find the label of project, so to change the project name in complete IDE, I have to provide my own IWorkbenchAdapter for IProject, but since platform already declares one workbench adapter for project (org.eclipse.ui.internal.ide.model.WorkbenchProject), and if the user declares it's own custom IWorkbenchAdapter, the platform essentially ignores it and always used it's own adapter (WorkbenchProject).
This is not acceptable in our case, as we can't use the actual Eclipse project name, but we have to use the custom name, depending on various other attributes.
 
PS: There is no issue in customizing the project icon, as we can specify the icon with the custom project nature, which is fairly honored by WorkbenchProject.


Reproducible: Always

Steps to Reproduce:
API issue.

Comment 1 Lars Vogel

2019-11-14 03:37:03 EST

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.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.