[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5693?page=c... ] Hardy Ferentschik commented on HHH-5693: ---------------------------------------- Re-enabled the test, but currently there are still three tests in {{PackagedEntityManagerTest}} failing. These tests are _testDefaultPar_, _testDefaultParForPersistence_1_0_ and _testExplodedPar_. The error only occurs on Mac (at least I think so) and the problem is that the compiled package-info.class files used by {{PackagedEntityManagerTest}} "loose" the {{@NamedQuery}} information when they are getting compiled. This might be related to another Mac "hack" we had to introduce. For some reason recursive compiling via the annotation processor does not seems to work on Mac if the option _-s <dir>_ is passed to the processor. On other system annotation processing (metamodel generation) can happen during the main compilation. For now we introduced to compilations. One to just create the metamodel (_-proc:only_) and one for compiling the test sources without annotation processing (_-proc:none_). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5693?page=c... ] Hardy Ferentschik commented on HHH-5693: ---------------------------------------- When using the "two compilations" trick: {code} procTargetDirName = buildDirName + "/generated-src/jpamodelgen" procTargetDir = dir( procTargetDirName ) // in theory it metamodel generation and compilation should be possible in a single compilation, // but this fails on Mac. Hence, to separate compilations. One to generate the meta model classes // and one to compile everything task generateMetaModel(type: Compile) { classpath = compileTestJava.classpath source = compileTestJava.source destinationDir = compileTestJava.destinationDir configure( options ) { compilerArgs = ["-proc:only", "-s", "$procTargetDir.dir.absolutePath"] } } generateMetaModel.dependsOn procTargetDir compileTestJava { configure( options ) { compilerArgs = [ "-proc:none", "-s", "$procTargetDir.dir.absolutePath" ] } source += files(procTargetDir.dir) } compileTestJava.dependsOn generateMetaModel {code} the {{package-info.class}} are using the named query information contained in them. I am unable to determine why. For this reason I am reverting back to a single compilation approach, but without the _-s_ option. This means that the generated meta model classes are generated in _target/classes/test_, but since these are only test classes it is acceptable. As a nice side effect the entitymanager build file becomes much simpler, because it relies on more defaults. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira