On 3.3M5, I've created a 7.1 runtime env and set the JRE to a Java 1.6 installation.
When creating a new Dynamic Web Project, the project configuration "Default JBoss 7.1 runtime configuration" insists on configuring a non-existent (in my case) 1.7 JRE by default.
The symptoms are deployable class files built at 1.7 which fail at deployment when a 1.7 JRE is not present.
This can be worked around by modifying the default configuration during project creation. After project creation, this can be worked around by changing the project Java Facet and Compiler Compliance Level.
The desired behavior is for the "Default JBoss 7.1 runtime configuration" during project creation to utilize the setting in the configured JBoss 7.1 Server runtime by default.
I don't see this.
Have you installed Java 7 support into your eclipse indigo or something ?
There should not be any usage of "non existing JRE's", only execution environments.
The runtime of your server really does not have anything to do with the target JDK of the project.
i.e. you could be targeting Java 5 on a Java 6 server.
...I've seen a few other reports on this and haven't been able to spot the problem on my side...any
chance you can take some screenshots/jing it _?
No Java 7 currently installed. I can replicate the behavior in a new workspace:
1. No JBoss runtime configured, no JBoss server defined: When creating a new Dynamic Web Project in this state, the Project Configuration defaults to "Default Configuration". The generated project selects "Use compliance from execution environment 'JavaSE-1.6' on the Java Build Path. The Java compiler setting is 1.6.
2. JBoss runtime configured, JBoss server defined. When creating a new Dynamic Web Project, I set Target runtime = 'JBoss 7.1 Runtime'. The project Configuration automatically switches to 'Default Configuration for JBoss 7.1 Runtime". The project Java Compliance setting is 1.7. 'Use compliance from execution environment on the Java Build Path' is disabled. 'Use default compliance settings' is checked.
We've tried reproducing this issue at https://issues.jboss.org/browse/JBIDE-10657 but simply cannot find a way.
do you still have a problem with this in later recent versions of JBoss Tools/Developer Studio ?