Re: [infinispan-dev] Infinispan target JDK?

Hi Manik, I was just wondering which target JVM you are using for Infinispan. I recall there was a discussion about this on the Core. The reason I am asking is that in Hibernate we have a infinispan cache provider module which depends obviously on infinispan core. Now I get the following error when compiling Hibernate: [INFO] ------------------------------------------------------------------------ [INFO] Building Hibernate Infinispan Integration [INFO] task-segment: [clean, install] [INFO] ------------------------------------------------------------------------ [INFO] [clean:clean {execution: default-clean}] [INFO] Deleting directory /Users/hardy/work/hibernate/core/trunk/ cache-infinispan/target [INFO] snapshot org.infinispan:infinispan-core:4.0.0-SNAPSHOT: checking for updates from central [INFO] snapshot org.infinispan:infinispan-parent:4.0.0-SNAPSHOT: checking for updates from central [INFO] [enforcer:enforce {execution: enforce-java}] [INFO] [resources:resources {execution: default-resources}] [WARNING] Using platform encoding (MacRoman actually) to copy filtered resources, i.e. build is platform dependent! [INFO] Copying 1 resource [INFO] [compiler:compile {execution: default-compile}] [INFO] Compiling 18 source files to /Users/hardy/work/hibernate/core/ trunk/cache-infinispan/target/classes [INFO] ------------------------------------------------------------------------ [ERROR] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Compilation failure /Users/hardy/work/hibernate/core/trunk/cache-infinispan/src/main/ java/org/hibernate/cache/infinispan/InfinispanRegionFactory.java: [29,-1] cannot access org.infinispan.Cache bad class file: /Users/hardy/tmp/m2/org/infinispan/infinispan-core/ 4.0.0-SNAPSHOT/infinispan-core-4.0.0-SNAPSHOT.jar(org/infinispan/ Cache.class) class file has wrong version 50.0, should be 49.0 I cannot switch to JDK 6, since parts of Hibernate require JDK 5 APIs. Are you only going to release infinispan with target VM 1.6? Or was the deploy a mistake? If so maybe you could push another snapshot. --Hardy