[ https://issues.jboss.org/browse/JBIDE-11387?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-11387. --------------------------------- Fix Version/s: 3.3.0.Beta3 (was: 3.3.0.Beta2) Resolution: Done Committing to trunk. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11387?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-11387. --------------------------------- Resolution: Done Up until now I've simply been responding to users demanding that a specific JDK is 'selectable' in certain situations. So in that regard, you're right. However I guess it is possible that I've gone too far into allowing too much, things that don't make sense. The goal here is that things work in the proper way. If you can find a combination that doesn't make sense, or leads to errors deploying, definitely open a new bug for them. For example, if you make a web app, and use eap4.3, and some java7 language constructs, and the webapp cannot run when launched with a java7 jdk, then that's a bug. This gets messy, though, because while jboss 7 may support java7, if you choose to run with jdk 6 and the java7 feature fails to run, that's not a bug. That's a user error. But again, if you can get a default situation that a user might run into that causes a failure, definitely open a bug for it and we can re-evaluate whether the current behavior makes sense or not. It would seem to me that maybe eap4.3 supporting java7 might not make sense, so if you can demonstrate that in a bug, that'd be great. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11387?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-11387: --------------------------------------- OK, thanks, that's what I needed to know. I don't think it's really such an issue if users CAN select java 1.7 with eap 4.3 runtime. They should know what they're doing and since they won't be running their eap 4.3 with java 1.7 they will know they shouldn't use it in their project either. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira