Since issue 26338 has been implemented, anyone can provide a dynamic content of system file system. Such content
overrides defaults provided by modules, but can be overriden by user changes. However to solve issue 162780 I need to
provide content that is behind the module layers - a kind of fallback.
Created attachment 85837 [details]
[JG01] The connection to issue #162780, and hence the motivation for this issue, is not explained at all. It would seem
that the straightforward fix of issue #162780 would be for ergonomics to consider a "feature" installed only if all kit
modules in the cluster are enabled, rather than at least one.
[JG02] You forgot to fix ExternalUtil.MainFS.computeDelegates.
Created attachment 85866 [details]
Full patch (including ergonomics change) and fix for JG02
Re. JG01: That is probably more for discussion in the issue 162780, but shortly: Yes, I need to change the logic
according to your suggestion (e.g. installed only when all modules installed), but also I need to make sure that if a
single module provides a template, then it takes precedence over the ergonomics definition. I tried various tricks,
but providing "fallback" layer is the only one that is not hack. Works nicely and contains even less dynamics (e.g.
all ergonomics layers always on) than the 6.7 system.
BTW I would suggest the new test code be added to ExternalUtilTest so that C-F6 from ExternalUtil.java will check
validity of code in that class.
I'll integrate tomorrow (probably without addressing BTW).
Integrated into 'main-golden', will be available in build *200908130201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
User: Jaroslav Tulach <firstname.lastname@example.org>
Log: #169892: Dynamic 'fallback' content of system file system