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

Bug 357121

Summary:	Product IU qualifier (still) not replaced
Product:	z_Archived	Reporter:	David Pochet <dpochet>
Component:	Buckminster	Assignee:	buckminster.core-inbox <buckminster.core-inbox>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	stepper, thomas
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description David Pochet

2011-09-08 12:32:36 EDT

This can be considered as a duplicate of Bug 318318, as I observe the same behavior in a Eclipse 3.7 (Buckminster 1.4.0) environment, but I can't reopen Bug 318318

In the built update site, the product IU qualifier is not replaced (and kept to "qualifier").
As a workaround I have to "manually" replace (with an ugly ant pre-build step) qualifier in the product file...

Comment 1 Thomas Hallgren

2011-09-10 04:49:33 EDT

I would recommend that you let your product be feature based and appoint exactly one feature. That feature in turn will control the product branding (through it's branding plugin) and what other features and bundles that the product will contain. The version of that feature also becomes the version of the product.

A typical setup is that you create a feature project to reflect your product. In this feature project you also have the .product file. The .product file appoints the feature in which it resides.

Comment 2 David Pochet

2011-09-21 05:43:21 EDT

This workaround works fine, thanks.
But it has actually one drawback: I have a feature I want to integrate in several products, and I can't bury it in another feature since it contains bundles for which I have to specify start levels & auto start options in the product configuration.

It's just a matter of 3-4 bundles, so I can integrate them in all top level features I need to publish products, but it would really be a nice enhancement if this issue was fixed.

Comment 3 Thomas Hallgren

2011-09-21 07:52:55 EDT

(In reply to comment #2)
> ... it would really be a nice enhancement
> if this issue was fixed.

Patches are always welcome.