Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 273974 - No splash screen after exporting simple mail
Summary: No splash screen after exporting simple mail
Status: CLOSED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.5   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-28 01:47 EDT by Ian Bull CLA
Modified: 2019-08-02 02:48 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ian Bull CLA 2009-04-28 01:47:47 EDT 
When I create, export and launch the simple mail application, no splash screen is displayed.  I don't know if this is a publisher or PDE Buid problem.
Comment 1 Andrew Niefer CLA 2009-04-28 11:28:11 EDT 
Ian I just did this and I saw a splash screen.

Note that on the splash tab of the product file, you need to set the plugin containing the splash.bmp.  This is not set by default when creating the .product file.  (I wonder if it should be, I created the .product with "Use an existing product")

You should expect to see a 
osgi.splashPath=platform\:/base/plugins/splash

in the config.ini
Comment 2 Ian Bull CLA 2009-04-28 11:41:07 EDT 
Two points:
1. I think this is a regression. You didn't have to specify this before.
2. It works fine if you just launch from the UI.  I wonder how PDE UI is finding it?
Comment 3 Andrew Niefer CLA 2009-04-28 11:51:37 EDT 
Sending to PDE/UI.  Launching the product from the workspace does show the splash even if the plug-in isn't specified on the splash tab.
Comment 4 Eclipse Genie CLA 2019-08-02 02:48:29 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.