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

Bug 314569

Summary:	unbranded 'Hello RCP' app does not run outside eclipse
Product:	[Eclipse Project] PDE	Reporter:	Ankur Sharma <ankur_sharma>
Component:	UI	Assignee:	PDE-UI-Inbox <pde-ui-inbox>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	P3	CC:	ankur_sharma, darin.eclipse
Version:	3.6
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Ankur Sharma

2010-05-26 16:27:44 EDT

1. Create a plug-in project using Hello RCP template. Do not select 'Add branding' checkbox.
2. Run the app and verify the RCP window appears. (This step is just to create the run config)
3. Create a Product Definition for this app in the same plug-in.
4. Create a new Product using Product Definition section on Overview page.
5. Export the app using this product definition.

Run the app from outside Eclipse. It throws Exceptions which can be found in log files in the configuration folder.

The app runs fine if the branding was selected during project creation.

Comment 1 Ankur Sharma

2010-05-26 17:02:55 EDT

If this bug is correct, then RCP cheatsheet will need rework too.

Comment 2 Darin Wright

2010-05-26 22:38:01 EDT

If you created the product definition from the existing launch configuration, you are probably seeing bug 278598. On the "Launching" tab, check your Program arguments... if they include variables like ${os}, this will not work. 

I was able to define a product and had the exported product launch with no errors once I corrected the program arguments.

Comment 3 Darin Wright

2010-05-26 22:39:26 EDT

(In reply to comment #2)
> . On the "Launching" tab, check your Program
> arguments

i.e the product definition Launching tab.

Comment 4 Ankur Sharma

2010-05-27 15:42:45 EDT

you are right. will try to fix it for 3.6.1 now. Not updating the RCP CS for it.

Comment 5 Darin Wright

2010-05-27 15:45:27 EDT

Thanks, marking as dup.

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