You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to a bug in Tycho, the launcher does not include a splash screen if the
name of the containing plug-in contains dots. The recommended workaround is to
build a p2 repository instead of an application.
Original issue reported on code.google.com by peer.tor...@gmail.com on 27 Sep 2011 at 6:08
The text was updated successfully, but these errors were encountered:
Quoting the e-mail conversation on this topic:
There is apparently a bug in Tycho that causes the name of the splash file to
get corrupted in the generated config.ini if the name of the plug-in that holds
the splash file contains dots (see
http://www.eclipse.org/forums/index.php/m/662311/):
If the splash.bmp is located in plug-in
org.socialmusicdiscovery.yggdrasil.foundation, the generated config.ini file
holds the text
osgi.splashPath=platform\:/base/plugins/org
when it should be
osgi.splashPath=platform\:/base/plugins/org.socialmusicdiscovery.yggdrasil.foundation
The effect is that yggdrasil currently launches without a splash screen. The
problem is easily verified by manually editing
...\yggdrasil\org.socialmusicdiscovery.yggdrasil-product\target\win32.win32.x86\
eclipse\configuration\config.ini (or whatever target platform you built).
I did try to check-in the config.ini and change the product spec to use the
existing file rather than generate a new, but this had no effect. Since the bug
still doesn't seem to be fixed, we will probably have to redo this project and
let Tycho build the product as "eclipse-repository" unless we can find some
other workaround (I am not very eager to rename the project again and use an
unqualified name, plug-ins benefit from qualified names just as Java classes
do).
Original comment by peer.tor...@gmail.com on 27 Sep 2011 at 6:11
Original issue reported on code.google.com by
peer.tor...@gmail.com
on 27 Sep 2011 at 6:08The text was updated successfully, but these errors were encountered: