[QFJ-327] Compiling the source under jdk 1.5.x; inconvertible types Created: 05/Aug/08 Updated: 08/Sep/08 Resolved: 08/Sep/08 |
|
Status: | Closed |
Project: | QuickFIX/J |
Component/s: | Build |
Affects Version/s: | 1.3.1 |
Fix Version/s: | None |
Type: | Other | Priority: | Default |
Reporter: | Thomas Hügel | Assignee: | Unassigned |
Resolution: | Fixed | Votes: | 0 |
Labels: | None |
Description |
Just tried to compile the source with "ant jar" under jdk 1.5.x because the new release 1.3.2 seems to be compiled wiht a newer version ("Bad version number in .class File"). I got the following: BUILD FAILED -------------------------------------------------------- Do you have any suggestions how to solve the problem ?. Thanks |
Comments |
Comment by Steve Bate [ 06/Aug/08 ] |
Are you using the newest version of JDK 1.5? There are some generics-related bugs in early versions of the compiler. There are special JDK1.4 binary packages if that's what you need. The source must be compiled with Java 5+. |
Comment by Toli Kuznets [ 07/Aug/08 ] |
Thomas, It compiles for me with java version "1.5.0_13" if i remember correctly, you need to have Java version higher than 1.5.0_06 - there was a bug in compilation of generics in _06 so you need to get a compiler higher than that. Here's the output of my java -version call: |
Comment by Thomas Hügel [ 07/Aug/08 ] |
Thanks for the response. I tried with 1.5.0_06 then with 1.5.0_07 - failed; then I downloaded the last 1.5 sdk Version "1.5.0_16". This one was able to compile the source. |
Comment by Christoph John [ 25/Aug/08 ] |
Hi, I am not even trying to compile the source but when I start my process which uses QuickFIX/J 1.3.2 then I also get: Exception in thread "main" java.lang.UnsupportedClassVersionError: Bad version number in .class file I have JDK 1.5.0_16. When using JDK1.6.0_07 the error does not occur. Any thoughts? |
Comment by Steve Bate [ 25/Aug/08 ] |
It's possible the code was accidentally compiled with Java 6 instead of Java 5. I'll check into it. Thanks for the report. I'm surprised no one else has reported this issue. |