Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 313625 - Product export with custom config using bundles.info loses start levels
Summary: Product export with custom config using bundles.info loses start levels
Status: RESOLVED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: Build (show other bugs)
Version: 3.6   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: pde-build-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-19 16:34 EDT by Andrew Niefer CLA
Modified: 2018-12-03 09:06 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 Andrew Niefer CLA 2010-05-19 16:34:11 EDT 
If a .product file uses a custom config.ini which uses the simpleconfigurator, then most of the start level information is in a bundles.info file.

The bundles.info file can be provided relative to the config.ini.

However, PDE/Build will copies the .product file to a temporary location to perform version replacements without contaminating the workspace .product file.  In this case, if a custom config.ini is used and specified with a relative path, then we also copy that config.ini to the temp location.  However, we do not copy any accompanying bundles.info, so we will lose this information.

If an absolute path is used to specify the config.ini location, then this extra copying is not necessary and we don't lose the information.
Comment 1 Lars Vogel CLA 2018-12-03 09:06:05 EST 
Currently we are not actively enhancing PDE build anymore. Therefore, I close this bug as WONTFIX. 

Please reopen, if you plan to provide a fix.