Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 355894 - [documentation] Expand build id in product configurations
Summary: [documentation] Expand build id in product configurations
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Buckminster (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: buckminster.core-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 355892
Blocks:
  Show dependency tree
 
Reported: 2011-08-25 16:07 EDT by Thomas Hallgren CLA
Modified: 2019-02-25 14:40 EST (History)
0 users

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 Thomas Hallgren CLA 2011-08-25 16:07:40 EDT 
The documentation for the site.p2 action should mention the build.id expansion.

+++ This bug was initially created as a clone of Bug #355892 +++

It is very common to include a build id in a product configuration file. Example:

 <configurations>
   <property name="eclipse.buildId" value="@qualifier@" />
 </configurations>

The idea is to expand this build id before it is fed to the publisher so that the IU that corresponds to the product gets a touchpoint instruction similar to:

 <instruction key='configure'>
  setProgramProperty(propName:eclipse.buildId,propValue:S201108251123);
 </instruction>

Buckminster should perform this expansion automatically when during the site.p2 action when it has a build.id property set.