| Building "umbrella" features that include multiple pre-built child features [message #53015] |
Wed, 01 April 2009 15:11  |
 Chris Williams
Messages: 29
Registered: July 2009 |
Junior Member |
|
|
We have a large number of features all with various dependencies between
them. For our RCP product and the main feature for Eclipse users we create
an umbrella feature which contains many children. This has generally
worked OK in the past, but ended in one feature and one RCP build being
massive and building everything from source. We're trying to move to
breaking these features out to be separate builds that get triggered to be
re-built based on their dependencies. We also now have need for multiple
"umbrella" features which contains various subsets of all these features
as children, some with more of them, some with less.
Is there any way to avoid duplicating the compilation during these
umbrella feature builds and have them "re-use" the binaries from their
children?
i.e. Feature Z is an "umbrella" that includes Features A, B, and C. We
have builds set up for A, B and C separately. We'd like the feature Z
build to just grab the built features and plugins from these children (via
P2 installs, filesystem copies of zips, whatever) and then just basically
compose them into the larger Z build results (update site, zip) without
re-compiling anything. What we have now requires that any children of Z
also get built from source in Z's build.
|
|
|
| Re: Building "umbrella" features that include multiple pre-built child features [message #53424 is a reply to message #53015] |
Thu, 02 April 2009 20:44  |
Andrew Niefer
Messages: 990
Registered: July 2009 |
Senior Member |
|
|
This simplest way to do this is to just have the umbrella build occur in
a different location from the sub features. Take the binaries that were
build for the subfeatures and use them as the input to the umbrella
build, put them in a new baseLocation, or set pluginPath to point to them.
-Andrew
Chris Williams wrote:
> We have a large number of features all with various dependencies between
> them. For our RCP product and the main feature for Eclipse users we
> create an umbrella feature which contains many children. This has
> generally worked OK in the past, but ended in one feature and one RCP
> build being massive and building everything from source. We're trying to
> move to breaking these features out to be separate builds that get
> triggered to be re-built based on their dependencies. We also now have
> need for multiple "umbrella" features which contains various subsets of
> all these features as children, some with more of them, some with less.
>
> Is there any way to avoid duplicating the compilation during these
> umbrella feature builds and have them "re-use" the binaries from their
> children?
>
> i.e. Feature Z is an "umbrella" that includes Features A, B, and C. We
> have builds set up for A, B and C separately. We'd like the feature Z
> build to just grab the built features and plugins from these children
> (via P2 installs, filesystem copies of zips, whatever) and then just
> basically compose them into the larger Z build results (update site,
> zip) without re-compiling anything. What we have now requires that any
> children of Z also get built from source in Z's build.
>
|
|
|
| Re: Building "umbrella" features that include multiple pre-built child features [message #594562 is a reply to message #53015] |
Thu, 02 April 2009 20:44 |
Andrew Niefer
Messages: 990
Registered: July 2009 |
Senior Member |
|
|
This simplest way to do this is to just have the umbrella build occur in
a different location from the sub features. Take the binaries that were
build for the subfeatures and use them as the input to the umbrella
build, put them in a new baseLocation, or set pluginPath to point to them.
-Andrew
Chris Williams wrote:
> We have a large number of features all with various dependencies between
> them. For our RCP product and the main feature for Eclipse users we
> create an umbrella feature which contains many children. This has
> generally worked OK in the past, but ended in one feature and one RCP
> build being massive and building everything from source. We're trying to
> move to breaking these features out to be separate builds that get
> triggered to be re-built based on their dependencies. We also now have
> need for multiple "umbrella" features which contains various subsets of
> all these features as children, some with more of them, some with less.
>
> Is there any way to avoid duplicating the compilation during these
> umbrella feature builds and have them "re-use" the binaries from their
> children?
>
> i.e. Feature Z is an "umbrella" that includes Features A, B, and C. We
> have builds set up for A, B and C separately. We'd like the feature Z
> build to just grab the built features and plugins from these children
> (via P2 installs, filesystem copies of zips, whatever) and then just
> basically compose them into the larger Z build results (update site,
> zip) without re-compiling anything. What we have now requires that any
> children of Z also get built from source in Z's build.
>
|
|
|
Powered by
FUDForum. Page generated in 0.03150 seconds
] 
Search
Help
Register
Login
Home
