Goal is to make JBT/JBDS more modular and user friendly via dynamic features loading when they are really used. Not to have current state when unused features are present and loaded and some extra features needs to be installed via update site manually.

Expected state could look like:

• Present menu items for all provided actions (like New <any-type-of> Project)
• if selected for the first time, feature will be downloaded (if needed), installed and loaded without any special user interaction
• wizard (or any other action) will continue after that in situation

I see several related issues:
1. Seamless feature loading (currently after feature installation eclipse restart is usually needed which is not very usable for this)
2. Architecture (it could be quite challenging to implement dummy plug-in with some extensions like menus triggering feature post-loading)
3. Installation speed (currently all p2 operation are quite slow so I'm not sure if it is feasible)

Note: take this feature request as an early proposal. I guess many people would appreciate this kind of architecture and JBT/JBDS would become more agile for the future. Everyone developer requires only specific set of IDE features. This is how they could be satisfied.