Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 334271 - importtargetdefinition doesn't complete in time when running from a .script file
Summary: importtargetdefinition doesn't complete in time when running from a .script file
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Buckminster (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: buckminster.core-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-13 10:50 EST by Stef bolton CLA
Modified: 2019-02-25 14:41 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stef bolton CLA 2011-01-13 10:50:02 EST
Build Identifier: 20100917-0705

Running the following commands on the commandline works: -

    buckminster -data buckminster.workspace importtargetdefinition -A feature.target
    buckminster -data buckminster.workspace import feature.cquery

However, having them run from a script file causes the message "Resetting target platform Buckminster Default TP" to be output and our build then fails.

This appears to be a timing issue where the target definition hasn't finished materialising before the cquery is materialised.

I can work around this, by importing the target definition twice - this seems to give it enough time to resolve before the cquery is materialised.


Reproducible: Always

Steps to Reproduce:
1. As detailed above. Run a .script file with an importtargetdefinition command immediately followed by an import command - causes the error.
2. Run the two commands manually and the tp import works correctly.
Comment 1 Stef bolton CLA 2011-01-14 04:00:47 EST
I should mention this wasn't occurring until a fourth installation site was added to the feature.target file.