OK thanks for the clarification. Optional is good, but I think we should turn the option 'on' by default if possible. I think the use case for a design env without a runtime environment is valid, but limited.

I'm not sure what you mean by 'option', but to clarify a bit more, the main motivation behind the 2 features revolves around ensuring the project remains useable by itself, meaning outside of bundled distribution options such as within JBT or JBDS. Nothing else Barry discussed is a motivating factor, but rather side-effects of moving in this direction. Thus, there would be one feature in our update site for designer that does not include any runtime capability, and another feature that adds runtime to the base feature. The core feature would, by definition, but more limited than both together, but still usable just to model. In the future, we could get the runtime feature to not depend upon the design-time feature, potentially allowing for a more lightweight installation by testers and the like that only care about runtime and not the modeling aspects. So, not sure if the idea of turning on an option applies.