[
https://issues.jboss.org/browse/JBIDE-18700?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-18700:
-------------------------------------
We have a few options here, but not really ;) We're basically stuck and have to wait
for new API =P
Our current API only has a minimum execution environment. If we move this up to java7 for
eap6.x, then unfortunately java6 will no longer appear as an option to users for any
eap6.x server. This obviously isn't acceptable. We should ideally have a minimim
execenv, a maximum, and a default, for each server/runtime type.
The second problem is that AbstractJREComposite unfortunately fills its data during its
constructor, rather than fit in with the workflow of the other widgets like
RuntimeHomeComposite which are created first, and filled after the runtime working copy
has been created. That should be an easy fix, though, and may open the possibility that
we could ensure different default / min / max execenv depending on the inner details of a
given server home.
But, since we're lacking that api, and currently only have minimums, I think we're
pretty stuck here until API addition has occurred.
EAP 6.x Configuration doesn't select Java 7 by default
------------------------------------------------------
Key: JBIDE-18700
URL:
https://issues.jboss.org/browse/JBIDE-18700
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.2.0.Final
Reporter: Fred Bricon
Assignee: Rob Stryker
- Create a new EAP 6.3 server
- Create a new Dynamic Web Project
- Select the EAP runtime
=> An error is shown : "Dynamic Web Module 3.1 requires Java 1.7 or newer."
!http://content.screencast.com/users/fbricon/folders/Jing/media/ee20c272-5761-40ab-8fe8-1004533501c7/00000025.png!
The EAP 6 Default Configuration should have the Java 1.7 Facet set by default.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)