[
https://issues.apache.org/jira/browse/OPENJPA-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12744074#action_12744074
]
Michael Dick commented on OPENJPA-1245:
---------------------------------------
The locking tests are part of the core JPA functionality. I don't see them as
part of our integration with another product (ie a Bean Validation provider, or
the TCK). If we split out other long running tests it might make sense to
create an openjpa-tests module but integration didn't seem right to me.
There's really no good place to put these tests. Conceptually they belong in
openjpa-persistence-jdbc, but we don't have fine grained control of the JVM
used to run the tests (and the derby settings are per jvm).
> Move locking tests to a separate module
> ---------------------------------------
>
> Key: OPENJPA-1245
> URL: https://issues.apache.org/jira/browse/OPENJPA-1245
> Project: OpenJPA
> Issue Type: Improvement
> Components: build / infrastructure
> Reporter: Michael Dick
> Assignee: Michael Dick
> Priority: Minor
>
> Donald Woods first proposed this change but was met with some concerns [1].
> While it's not particularly pretty moving the tests would allow us to set
> different derby lock timeouts for persistence-jdbc tests which should speed
> execution.
> [1] http://markmail.org/thread/eovueydeaihpyd2c
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
