[jbosstools-issues] [JBoss JIRA] (JBIDE-15189) Check compatible JRE/JDK when adding server via runtime detection

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-15189:
-------------------------------------

This is a significant issue for usability, but unfortunately it will require real investigation into the runtime detection API, whether its appropriate to throw an exception, or what level of interaction the user should have in the process. As of now, I don't think the runtime detection API is set up for interactive procedures. The most I could do is throw an exception, but I'd need to make sure the runtimes framework wouldn't blow up if I did. 

I'll be leaving this targeted to 4.2.x for now =/ 

> Check compatible JRE/JDK when adding server via runtime detection
> -----------------------------------------------------------------
>
>                 Key: JBIDE-15189
>                 URL: https://issues.jboss.org/browse/JBIDE-15189
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: runtime-detection
>    Affects Versions: 4.1.0.CR1
>            Reporter: Radim Hopp
>             Fix For: 4.1.x, 4.2.x
>
>
> Now, people are not allowed to create runtime when no compatible java is configured in eclipse (JBIDE-14858).
> But when adding server and runtime via runtime detection, server and runtime are added even though no compatible java is configured.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)