[jbosstools-issues] [JBoss JIRA] (JBIDE-17829) Server adapter chooses wrong runtime for launches and validation is inconsistent

Martin Malina (JIRA) issues at jboss.org
Mon Jul 14 05:02:29 EDT 2014


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

Martin Malina commented on JBIDE-17829:
---------------------------------------

I have verified in JBDS 8.0.0.Beta3 B178 that the validation use case now works as expected:
1. Have workspace with only java 1.6
2. Add Wildfly 8.1 - the runtime page will tell me that I have no jre for the 1.7 exec env. When I choose 1.8, the warning will change to say I have no jre for the 1.8 exec env
3. Add java 1.7 and choose it for Wildfly - warning/error disappears and I am able to finish the dialog
4. Start server - starts with the right java (1.7)
5. Check Launch config - has the right java in classpath

> Server adapter chooses wrong runtime for launches and validation is inconsistent
> --------------------------------------------------------------------------------
>
>                 Key: JBIDE-17829
>                 URL: https://issues.jboss.org/browse/JBIDE-17829
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.2.0.Beta3
>            Reporter: Max Rydahl Andersen
>            Assignee: Max Rydahl Andersen
>            Priority: Blocker
>              Labels: respin-b
>             Fix For: 4.2.0.Beta3
>
>
> I have only Java 6 JDK in eclipse.
> Create server 
> Wildfly 8 (download and install runtime now works sanely- yay!)
> gets error saying "No valid JRE's found for execution environment "JavaSE-1.8" even though I have "JavaSE-1.7" selected.
> and when I change to 1.8 it says it can't find one for 1.7...something is weird.
> Then I add Java 7, choose Java 7 and save.
> When opening launch configuration it has Java SE 6 as the JRE system library for bootstrap entries.
> So something is *really* wrong.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)


More information about the jbosstools-issues mailing list