My memory is poor, but I seem to recall
I used to update that file, as needed.
(And, would sometimes edit it to do
subsets, etc., building up to a test, so that, for example,
one broken script wouldn't stop the
whole thing ... but, as I said, my memory is poor).
And you are the Europa-build-master
now .. you get to set the rules. :)
I'll race 'ya?
Bjorn Freeman-Benson <bjorn.freeman-benson@xxxxxxxxxxx> Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
02/04/2007 10:37 PM
Please respond to
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Re: [cross-project-issues-dev] Enabling
Features for Europa?
You didn't add feature-wtp-enabling.xml to the updateMirrorAll.xml so either
(a) I don't understand the David-o-matic software (because I would have
thought that you need to reference that file in this file), or (b) you
wanted me to add it in?
Could you clarify? Thanks,
David M Williams wrote:
Anyone still need those?
I'd assume so, at least for M4, but the long term thought is to replace
these with "the Orbit way" of doing 3rd party bundles.
Namely, to have the consuming feature actually 'include' the required 3rd
party bundle, and it would just be "pre-built" by
the orbit project. Presumably everyone in Europa would have 'included'
the exact same version, so it would not be re-downloaded
by update manager, nor would there be multiple copies on the users install.
But, we're not there yet, so for M4 I have updated the WTP provided enabling
features. Only qualifiers have changed, but there was
a tweak in the xerces manifest.mf file that is important --- just incase
anyone (else) needs them.
Our three common ones are
And, Bjorn, I did create a new "feature-wtp-enabling.xml" file
in Europa build-tools to encode where to "find" those 3 features.
cross-project-issues-dev mailing list