[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-7527) Automatic runtime detection

[ https://jira.jboss.org/browse/JBIDE-7527?page=com.atlassian.jira.plugin.s... ] Snjezana Peco commented on JBIDE-7527: -------------------------------------- I have created a new feature. It is org.jboss.tools.runtime.core.feature. The feature includes two plugins: - org.jboss.tools.runtime.core - org.jboss.tools.runtime.ui The feature requires only the base Eclipse plugins : org.eclipse.ui, org.eclipse.core.runtime and org.eclipse.core.resources and can be easily used. The org.jboss.tools.runtime.core plugin includes the org.jboss.tools.runtime.core.runtimeDetectors ext. point that serves to define a runtime detector. The following is an example: <extension point="org.jboss.tools.runtime.core.runtimeDetectors"> <runtimeDetector id="org.jboss.tools.runtime.handlers.JBossASHandler" name="JBoss Server Runtime" class="org.jboss.tools.runtime.handlers.JBossASHandler" preferenceId="org.eclipse.wst.server.ui.runtime.preferencePage"/> </extension> id - a string that identifies a runtime detector. Must be unique. name - the name used in the UI class - has to extend the AbstractRuntimeDetector class preferenceId - the ID of the preference page where the runtime is (link to the UI) - optional Detectors for JBoss AS/EAP, Seam, Drools and jBPM are defined in the existing org.jboss.tools.runtime. The Runtime Tools Runtime Detection preference page is defined in the org.jboss.tools.runtime.ui plugin. In order to define some runtime detector, a developer needs only the org.jboss.tools.runtime.core plugin. The org.jboss.tools.runtime.ui plugin is necessary to show the preference page. 2) JBoss Tools Runtime Detection (ex JBoss Tools Runtimes) preference page is shown in the JBTRuntimeDetectionPreferencePage.png screenshot. Add - opens the standard directory dialog for scanning/adding runtimes. Runtimes aren't scanned (this behavior can be changed) Edit... - opens the dialog shown in the EditRuntimeDialog1.png screenshot. The user can change the path (Browse,,,) and scan/create runtimes (Refresh). Runtimes aren't scanned and created until the user presses Refresh. Remove - removes the path. Search.. - as Refresh in the "Edit runtime detection path" dialog, scans a path for runtimes (the SearchForRuntimes.png screenshot) . The Cancel button stops searching and cancels the dialog. The OK button creates a runtime. After refreshing, the "Edit runtime detection path" dialog looks like in the EditRuntimeDialog2.png screenshot. TODO : - remember entered paths, identified runtimes and disabled/enabled runtime detectors - Scan paths that have the "Every startup" button checked, when the user starts Eclipse in an old workspace. - scan all the paths when the user starts Eclipse in a new workspace. If Eclipse finds a new runtime(s), it would show a dialog that would enable the user to open the Runtime Detection preference page where he could review and create new runtimes. - add a runtime detector for JDK (and maybe for the standard WTP runtimes) - would this need to be done in a separate plugin/feature? Suggestions: 1) If some path is scanned, we could remember the path timestamp and scan again only if the timestamp is changed. The Refresh/Search... button would ignore timestamp. This would speed up the startup. 2) We could add a table of runtimes to the JBoss Tools Runtime Detection preference page as shown in the JBTRuntimeDetectionPreferencePage1.png screenshot. 3) The Edit... action (the "Edit runtime detection path" dialog) and the Search.../Refresh actions (the "Edit runtime detection path" dialog) could be combined in one action/dialog. 4) Add a checkbox to the Runtimes viewer that would inform the user if the runtime is created or not. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira