[jbosstools-issues] [JBoss JIRA] (JBIDE-12583) Unify two download-runtime models in o.j.t.runtime.as.handler plugin

[Rob Stryker (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-12583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718132#comment-12718132 ] 

Rob Stryker commented on JBIDE-12583:
-------------------------------------

This will be fixed by deleting the o.j.t.runtime.as.handler plugin and features in charge of runtime detection, and moving the 3 relevant classes into o.j.i.eclipse.as.core plugin. This will also help simplify the growing number of plugins
                
> Unify two download-runtime models in o.j.t.runtime.as.handler plugin
> --------------------------------------------------------------------
>
>                 Key: JBIDE-12583
>                 URL: https://issues.jboss.org/browse/JBIDE-12583
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: JBossAS/Servers, runtime detection
>    Affects Versions: 4.0.0.Alpha2
>            Reporter: Rob Stryker
>            Assignee: Rob Stryker
>             Fix For: 4.0.x
>
>         Attachments: JBIDE-12583.astools.png, JBIDE-12583.runtime.png
>
>
> ASTools has an integration plugin for astools vs runtime. With runtime now living at the bottom of the stack, this plugin may no longer be useful. 
> The runtime wizard dialog cannot load any runtime.ui dialogs because there is no dependency between as.ui and runtime.ui. To add a dependency here would basically make o.j.t.runtime.as.handler to be useless. All the code there could easily be pushed into astools' other plugins. 
> This isn't a huge priority, but it is a little silly to have two models doing exactly the same thing. 

--
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