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

Bug 322239

Summary:	Error - 7 icon(s) not replaced in ....
Product:	z_Archived	Reporter:	Flavio Donze <flavio.donze>
Component:	Buckminster	Assignee:	buckminster.core-inbox <buckminster.core-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	aniefer, peter.kullmann, yanamon
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Flavio Donze

2010-08-10 10:33:52 EDT

Build Identifier: Build id: I20100608-0911

I'm using Buckminster to automate my builds. I get the following error:

Error - 7 icon(s) not replaced in C:\WINDOWS\TEMP\p2.brandingIron705967665982685683\launcher.exe using C:\Programme\Hudson\workspace\jobs\scodi.client.integration\workspace\source\scodi-rcp\features\ch.scodi.client.feature\ch.scodi.scodi4p\icons\scodi.ico

The path is put together wrong "features\ch.scodi.client.feature" is the location of the feature where the product file is located.
"ch.scodi.scodi4p\icons\scodi.ico" is the branding plug-in and the path defined in the product file.
The build somehow uses the wrong base path.

Using the export wizard in the eclipse IDE the launcher icon is made correctly.

Reproducible: Always

Comment 1 yanamon

2010-10-05 16:50:15 EDT

I am seeing this problem as well and it appears to be a a problem with how org.eclipse.equinox.internal.p2.publisher.eclipse.ProductFile attempts to resolve files within a buckminster workspace.  In the addIcon method it is attempting to resolve paths that are not absolute by concatenating the workspace directory and the relative path together.  Even if the plugins has been resolved to the workspace directory the icon path will not be found because buckminster does not put plugins in the root workspace directory.  After that fails it just concatenates the relative path with the plugin that defined the product which also doesn't work.

Comment 2 Flavio Donze

2012-11-20 10:51:51 EST

This issue seems to be fixed in the current buckminster version:
Eclipse 4.2.1
org.eclipse.buckminster.core_1.3.0.v20120910-1329