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

Bug 327054

Summary:	[target] Running Platform target should be read only
Product:	[Eclipse Project] PDE	Reporter:	Jeff McAffer <jeffmcaffer>
Component:	UI	Assignee:	PDE-UI-Inbox <pde-ui-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	curtis.windatt.public
Version:	3.6
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:	stalebug

Description Jeff McAffer

2010-10-05 21:16:42 EDT

Somehow my target platform created from the "Default" (Default target for the running platform) option went astray.  I was running Eclipse on MacOSX, Cocoa, x86_64 but when I went and looked at the target platform it was setup as Mac, Carbon, x86.  This of course caused quite a bit of trouble especially on Snow Leopard with the whole 32/64 bit thing.  In any event, I can't say how this happened.  Perhaps I was using different IDEs on the same workspace at different times...

Regardless, it would be interesting to make the "Running Platform" target immutable and effectively "symbolic". If you set the target to the running platform and then use that same workspace on a different IDE, you would get that new IDE as the target setup.

Users wanting to tweak the Running Platform target would clone the Running one using the "Copy" option in the Add workflow and tweak to their heart's content.

Comment 1 Curtis Windatt

2010-10-07 16:03:52 EDT

Having read-only configs was suggested sometime in 3.5, but it was dropped in favour of being able to quickly edit the default target.  The icon will change if the default target is not actually the default, but we do not edit the name.

Comment 2 Jeff McAffer

2010-10-08 09:24:19 EDT

the icon change might be too subtle.  I've never noticed any different icons.  Perhaps the name of the target could also be changed to have <> or [] or something around it if the name is still Running Platform.

Question, if I am on Mac, Carbon, x86 and create a default target and then restart that workspace using Mac, Cocoa, x86_64, does that target that I created change to be the new platform?  Does its icon change?  The problem case is if the answer to both is "no".

Comment 3 Curtis Windatt

2010-10-08 10:45:43 EDT

(In reply to comment #2)
> the icon change might be too subtle.  I've never noticed any different icons. 
> Perhaps the name of the target could also be changed to have <> or [] or
> something around it if the name is still Running Platform.
> 
> Question, if I am on Mac, Carbon, x86 and create a default target and then
> restart that workspace using Mac, Cocoa, x86_64, does that target that I
> created change to be the new platform?  Does its icon change?  The problem case
> is if the answer to both is "no".

The icon should change as it would no longer match the default. Pressing restore defaults would create a new 'running platform' target with the correct values. However, the target won't change between the builds.

I'm making an assumption here that the target platform changes between the two installs.  If the target is the same: $eclipse_home for a location, same args, etc. then the behaviour may differ.

Comment 4 Jeff McAffer

2010-10-08 13:09:01 EDT

I'll see if I can test the scenario. 

In any event, it would be great if the name of the target would change if it was no longer really the Running Platform.

Comment 5 Eclipse Webmaster

2019-09-06 16:10:12 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.

Comment 6 Julian Honnen

2019-09-09 02:46:36 EDT

Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.