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

Bug 232395

Summary: Linux Eclipse Executable Not Honoring -name Parameter When Taskbar Stacks Windows
Product: [Eclipse Project] Equinox Reporter: Raji Akella <raji>
Component: FrameworkAssignee: equinox.framework-inbox <equinox.framework-inbox>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: aniefer, jdmiles, wjohnnie
Version: 3.4   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

Description Raji Akella CLA 2008-05-15 15:39:46 EDT
Build ID: 3.4M6

Steps To Reproduce:
The problem described can be recreated with standalone Eclipse on Linux. This is not specific to Eclipse 3.4, it can be reproduced on 3.3 as well. This also is not specific to launching using the Java Invocation APIs. This behavior has been seen on RedHat 4, RedHat 5, and SLED 10.

1. Install Eclipse
2. Launch Eclipse passing in the -name argument, such as -name WRJ
3. Change Eclipse to open perspectives in new windows:
For Eclipse, select Windows-->Preferences then click on General, then click on Perspectives and change the setting from "In the same window" to "In a new window"
4. Now open up as many perspectives as you can until the taskbar stacks the icons (HINT: open up multiple terminals, and firefoxs in addition if you're running at a very large screen resolution)
5. We can see the -name argument does not take affect, and the text of the stacked entries is that of the executable (in this case "eclipse" but if you rename "eclipse" to "notes2" or any other text it will be that text)

According to the Eclipse 3.3 documentation (http://help.eclipse.org/help33/index.jsp?topic=/org.eclipse.platform.doc.isv/reference/misc/runtime-options.html):
-name <string> NEW 
The name to be displayed in task bar item when the application starts up. When not set, the name is the name of the executable. 


More information:
Comment 1 Andrew Niefer CLA 2008-11-18 16:04:30 EST
This should work if the vm is started in-process instead of being forked in a separate process.  x86_64 and ppc still fork by default because some older vms have a habit of crashing when we try JNI.



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