Bug 212467 - Sort plugins across feature boundaries
Summary: Sort plugins across feature boundaries
Status: RESOLVED FIXED
Alias: None
Product: PDE
Classification: Eclipse Project
Component: Build (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 enhancement with 1 vote (vote)
Target Milestone: 3.5 M3   Edit
Assignee: pde-build-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 208011 238177
  Show dependency tree
 
Reported: 2007-12-10 17:14 EST by Andrew Niefer CLA
Modified: 2008-10-06 17:48 EDT (History)
3 users (show)

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 2007-12-10 17:14:43 EST 
The compile order for a set of plugins is based on pre-requisite order determined by the resolver.  This is done only for plugins within a given feature.  Features are compiled in the order they are included.

More advanced build features (cycles, incremental building) will require that all plugins are sorted regardless of feature boundaries.

Doing this would require that the patterns calling children build scripts that currently live in the generated feature build script would need to move into a separate "orchestration" script.
Comment 1 Andrew Niefer CLA 2008-10-06 17:48:03 EDT 
This has been released for the I20081007

Set "flattenDependencies" to turn this on.  A script "compile.*.xml" will be generated in the buildDirectory.  genericTargets.xml/processElement will compile via the targets processViaFeature or processFlat depending on the flattenDependencies property.  processFlat is compilation as before by delegating through the features.

Other targets (notably gather.bin.parts) still delegate through the feature.