[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-1647) New Seam wizard creates org.eclipse.jdt.core.prefs file with Java 6 enabled
[ http://jira.jboss.com/jira/browse/JBIDE-1647?page=comments#action_12396098 ]
Denis Golovin commented on JBIDE-1647:
--------------------------------------
That's right. If you have Java 6 installed and start Eclipse it has Java 6 configured
in Java/Installed JRE preferences and 6.0 compliance level in Java/Compiler.
1) This file generated by WEB facet installer delegate
2) That is related to Dafault Configuration for JBoss 4.2 Runtime.
3) This is odd, it is possible if you have both Java 5/6 installed in Java/Installed JRE
and Java 5 is default.
New Seam wizard creates org.eclipse.jdt.core.prefs file with Java 6
enabled
---------------------------------------------------------------------------
Key: JBIDE-1647
URL: http://jira.jboss.com/jira/browse/JBIDE-1647
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 2.0.0.GA
Reporter: Max Andersen
Assigned To: Denis Golovin
Priority: Critical
Fix For: 2.0.1
I got a Bad version in class file error today when deploying a freshly created seam and
noticed that the War project (not the test project) had Java 6 enabled for the compiler
(see screenshot)
1) Why are we actually generating this file ?
2) Why is it Java 6 that is chosen ? (on second run it was actually Java 5 so it is
non-deterministic)
3) If it is needed, why only on the war project and not the test projet ? (note: i
ahven't tested Ear)
I've seen a couple of questions on Bad Version in Class in the forum so I guess this
is not new behavior.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira