[
https://issues.jboss.org/browse/JBIDE-8623?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen resolved JBIDE-8623.
----------------------------------------
Resolution: Out of Date
Thank you for reporting this issue but this issue have been resolved as out-of-date since
it has not had any updates for the last 2+ years (730 days).
If you believe this issue is still relevant and important then please reopen the issue or
create a new one mentioning/linking this jira for background information.
Thank you!
Dynamic feature loading
-----------------------
Key: JBIDE-8623
URL:
https://issues.jboss.org/browse/JBIDE-8623
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: common/jst/core
Affects Versions: 3.2.0.Final
Reporter: Jiri Peterka
Fix For: LATER
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira