[jboss-jira] [JBoss JIRA] (JGRP-1550) 2.6.22.Final not running on 1.6 JVM
Bela Ban (JIRA)
jira-events at lists.jboss.org
Wed Dec 5 08:59:21 EST 2012
[ https://issues.jboss.org/browse/JGRP-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bela Ban updated JGRP-1550:
---------------------------
Fix Version/s: 3.3
Hmm, I'm using -source 1.5, which should also set -target 1.5 automatically...
I'll have a look. Meanwhile, build your own JAR using label JGroups_2_6_22_Final.
I changed the current build.xml on master to include -target="1.6", so that my JDK 7 based environment will create correct JARs to be used with JDK 1.6
> 2.6.22.Final not running on 1.6 JVM
> -----------------------------------
>
> Key: JGRP-1550
> URL: https://issues.jboss.org/browse/JGRP-1550
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 2.6.21
> Environment: JVM 1.6
> Reporter: MIchael Yates
> Assignee: Bela Ban
> Fix For: 3.3
>
>
> 2.6.22 has been built using JDK 7
> #A dump from a 2.6.21 class
> hexdump -n20 ./org/jgroups/MembershipListener.class
> 0000000 ca fe ba be 00 00 00 32 00 0d 07 00 0b 07 00 0c
> #A dump from a 2.6.22 class
> hexdump -n20 ./org/jgroups/MembershipListener.class
> 0000000 ca fe ba be 00 00 00 33 00 0d 07 00 0b 07 00 0c
> Note the 8th octet has changed form 32 to 33. ie from JVM6 to JVM7
> I suspect this is an oversight when 2.6.22 was built. Maybe -source and -target parameters forgotten on the build?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list