[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-3610) JBDS 2.0.0.CR1 Uses Java 6 when environment only has Java 5

[Snjezana Peco (JIRA)]

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

Snjezana Peco commented on JBIDE-3610:
--------------------------------------

This issue can be reproduced in the following way:

- start JBoss Tools in a new workspace using Java 1.5
- call the New ESB Project wizard
- enter Project Name and Target Runtime
- change JBoss ESB version (this step is important)
- finish the wizard

Your project will have the compiler compliance level 1.6 and Java facet 6.0
If you don't change the JBoss ESB version, the project will have the compiler compliance level 1.5 and Java Facet 5.0 that are correct.

The problem is that DataModelFacetCreationWizardPage.getFacetConfiguration() changes the Java Facet to the highest version (6.0) no matter of the system compliance level.
The solution is to override and fix this method in ESBProjectFirstPage.

Attached is a patch.

> JBDS 2.0.0.CR1 Uses Java 6 when environment only has Java 5
> -----------------------------------------------------------
>
>                 Key: JBIDE-3610
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-3610
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: esb
>         Environment: JBoss Developer Studio
> Version: 2.0.0.CR1
> Build id: R200812221144
> Build date: 12/22/2008 11:54
> Java 1.5.0_16
>            Reporter: Aaron Pestel
>            Assignee: John Graham
>            Priority: Minor
>             Fix For: 3.0.0.GA
>
>
> I'm quite sure the only JVM I have on my machine is Java 1.5.  If I say "which java", "java -version", "$JAVA_HOME/bin/java -version", "$JAVA_HOME/jre/bin/java -version", they are all Java 1.5.0_16.  I downloaded the new JBDS 2.0.0.CR1 from the download site and did no configuration to it, just started it by default (what configuration it may have picked up from previous JBDS versions I've run, is something I don't know, but other customers will likely have the same scenario, at least some of them).
> When I start JBDS, I've dumped the configuration from Help | About | Configuration, and it's running with a 1.5.0_16 JVM.  When I go to create a new server runtime so that I can have a SOA-P 4.3 server, the only JVM available to me is 1.5.0_16.  If I look in Eclipse at "Preferences | Java | Installed JREs", the only JRE installed is 1.5.0_16.  So, I create my SOA-P 4.3 runtime, create a simple ESB project and deploy it to the SOA-P 4.3 server.  Everything works fine until I add a custom Java action to my ESB project.  In that case, by default, it compiles the Java class with Java 1.6 (from where, I don't know, maybe a plugin that ships with Eclipse/JBDS?), and the ESB project fails to deploy on the SOA-P server with a class version mismatch exception.
> I can change my ESB project preferences to use the Java 5 facet, and everything works fine.  I was surprised that I had to change my ESB project preferences from Java 6 to Java 5 when I don't think I even have Java 1.6 installed on my machine and when I'm not even sure if SOA-P 4.3 actually works with Java 1.6.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira