[jboss-jira] [JBoss JIRA] Commented: (JBRULES-596) When a rule project is set to use jdk5 in properties -> java compiler, it can cause "unsupportered major.minor version" error

Tue Jul 24 12:03:47 EDT 2007

    [ http://jira.jboss.com/jira/browse/JBRULES-596?page=comments#action_12369915 ] 

Kris Verlaenen commented on JBRULES-596:
----------------------------------------

The unsupported major.minor version is probably caused by trying to execute java code with an old jre that has been compiled with a newer jre (in this case trying to execute jdk5 code using a jdk1.4).  When changing the jdk settings to a lower jdk version, you should ALWAYS allow eclipse to do a FULL rebuild of your project.  Otherwise it is possible that code compiled using the newer jdk version cannot be run by the older jdk.  This does not seem to be a Drools-related problem.  I am uncapable of reproducing the error when always doing a full rebuild after downgrading the jdk version.

> When a rule project is set to use jdk5 in properties -> java compiler, it can cause "unsupportered major.minor version" error
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBRULES-596
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-596
>             Project: JBoss Rules
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>    Affects Versions: 3.0.5
>         Environment: windows XP, eclipse 3.2.1, jdk 1.5.0
>            Reporter: peter lin
>         Assigned To: Kris Verlaenen
>            Priority: Minor
>             Fix For:  4.0.0.GA
>
>
> If a person's Eclipse is set to use jdk5 as the default, it can cause the plugin to not work. The error in the problems summary in eclipse says "unsupported major.minor version". The solution is to set the rule project to use jdk1.4.
> right click on the project
> select properties
> select java compiler
> change setting to jdk1.4
> another potential workaround is to set eclipse to use jdk1.4 as the default.

-- 
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