[jira] Commented: (OPENJPA-1942) Correct jUnits failures when native SchemaFactory is the default
[ https://issues.apache.org/jira/browse/OPENJPA-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12995938#comment-12995938 ] Mark Struberg commented on OPENJPA-1942: Jeremy, please consider that changing those settings might also lead to different bytecode being generated in the maven process-classes (here process-test-classes) phase. I already had some really weird bugs which I couldn't reproduce because the enhancer.xml ant script uses different settings than the unit tests... Correct jUnits failures when native SchemaFactory is the default Key: OPENJPA-1942 URL: https://issues.apache.org/jira/browse/OPENJPA-1942 Project: OpenJPA Issue Type: Sub-task Affects Versions: 2.1.1, 2.2.0 Reporter: Jeremy Bauer I switched the JDBCConfiguration to use openjpa.jdbc.SchemaFactory=native(ForeignKeys=true) as the default setting, ran a build, and found that many jUnits are failing. There are many failures in the o-p-j module, but they look to be caused by 3 or 4 main problems. This task is to identify the issues and: a) correct any jUnit related problems under this sub-task b) open sub-tasks for failures caused by code bugs -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (OPENJPA-1942) Correct jUnits failures when native SchemaFactory is the default
[ https://issues.apache.org/jira/browse/OPENJPA-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12996092#comment-12996092 ] Michael Dick commented on OPENJPA-1942: --- I agree that we should look out for it, but the SchemaFactory setting should not effect bytecode generation. The detached state manager is one of the few (I hope) configuration settings that affects the PCEnhancer. Correct jUnits failures when native SchemaFactory is the default Key: OPENJPA-1942 URL: https://issues.apache.org/jira/browse/OPENJPA-1942 Project: OpenJPA Issue Type: Sub-task Affects Versions: 2.1.1, 2.2.0 Reporter: Jeremy Bauer I switched the JDBCConfiguration to use openjpa.jdbc.SchemaFactory=native(ForeignKeys=true) as the default setting, ran a build, and found that many jUnits are failing. There are many failures in the o-p-j module, but they look to be caused by 3 or 4 main problems. This task is to identify the issues and: a) correct any jUnit related problems under this sub-task b) open sub-tasks for failures caused by code bugs -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
