[
https://issues.jboss.org/browse/JBIDE-15189?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-15189:
---------------------------------------
So, to sum up our discussion on hipchat:
One option would be to add a jre column in the detection result window. And have a
possibility to add a new jdk on the fly. But this column wouldn't apply to runtimes
like seam or cdk.
So perhaps a better option is to create a new column called "problems" or
similar. And this column would contain a button where relevant that would open UI for
problem resolution - similar to elsewhere - where they could fix this problem.
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
Assignee: Rob Stryker
Fix For: 4.4.1.AM3
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.4.11#64026)