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

Bug 344559

Summary:	Support for Java 6 splash screen
Product:	[Eclipse Project] Equinox	Reporter:	Giddi Ohm <giddi_o>
Component:	Launcher	Assignee:	Project Inbox <equinox.launcher-inbox>
Status:	REOPENED ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	andreas.buchen, daniel_megert, digga1404, marcus, peter, prakash, pwebster
Version:	3.7
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Giddi Ohm

2011-05-03 08:24:03 EDT

Build Identifier: I20110127-2034

Java 6 splash screens in exported Eclipse product are never displayed. The reason for using Java splash screen is that they support PNGs, the Eclipse RCP does not.

Adding -splash:splash.png to WM Arguments in the feature product file and removing the splash.bmp file solves the problem, but only when my application is started from the Eclipse IDE.

When the application is exported the splash screen is never shown even though the splash.png is in the exported folder and the .ini file contains the WM argument.

I think it is just a matter of the launcher not inserting the WM arguments at the correct place, because I managed to get it working from command line:

This works:
java -splash:splash.png -jar plugins\org.eclipse.equinox.launcher_*.jar

This doesn't work:
java -jar plugins\org.eclipse.equinox.launcher_*.jar -splash:splash.png

Reproducible: Always

Steps to Reproduce:
1. Replace splash.bmp with splash.png
2. Add -splash:splash.png to the product's WM arguments
3. Run the application from the Eclipse IDE (this works)
4. Export the product and run the exported .exe file (this doesn't work, no splash is visible)

Comment 1 Dani Megert

2017-12-21 10:25:16 EST

Java 6 is no longer supported. If you see this using Java 8 and 4.7.2, please reopen.

Comment 2 Andreas Buchen

2021-10-31 18:09:02 EDT

I can confirm that the problem persists with Java 11: The splash is shown when started from PDE tooling, but not when building a product ans using the native executable.

Reading through bug 114567, I understand the decision is not to use the Java native splash screen as it cannot replace the existing functionality in a compatible manner (mainly because it does not support the bmp image file format).

However, I think it should not *prevent* applications to use the native splash screen if they wish to do so. One major advantage I see is the support for high-DPI splash screen images.

I do not know how the native executable starts the Java VM, but if it is just a matter of ordering the arguments, then maybe it is worth to enable the Java native splash screen?