I am wondering why we have boot features in trunk. In particular I think there is an inconsistency around the management feature which is in the minimal boot feature list and whose jars are in the minimal server assembly. On the other hand the ssh full boot feature doesn't have all its jars in the full server.
If a boot feature doesn't already have all its jars in the server, won't this require internet access on initial startup? If all the jars for a boot feature are already installed in the server, why call it a boot feature, why not just start it with the rest of the jars? For this question I may be biased by looking at the packaging based assemblies where the startup.properties is constructed from the features that are installed into the server, so it is at least as east to configure the assembly to just include the jars as to configure a boot feature. Am I missing something? thanks david jencks
