TODAY:
.target files list all the IUs (feature and plugin) and the "target platform
sites" are generated from that listing via XSLT transform to p2.mirror script (uses:
maven, ant, xslt). Ant script also provides round-tripping in that the generated site is
used to update the .target files w/ the new versions of IUs.
FUTURE:
.target files list only top-level "virtual" features, which can be maintained
w/ no effort - file never changes unless the URL of the TP site changes (eg., moving from
SR0 to SR1 to SR2) or new "virtual" features need to be added (eg., new
collections of features added when a new component is added or a new dependency stack is
needed, like when we had to add git).
Target files with "virtual" features" means I would get these
'virtual' features installed - no way to avoid that ? these does not exist for
users so should not be in the tests.
And if the target files just list virtual features they are just as non-deterministic as
using features and thus rather pointless aren't they :)
/max