You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Donald Woods (JIRA)" <ji...@apache.org> on 2010/01/20 21:53:54 UTC
[jira] Resolved: (OPENJPA-1374) Enable junits to be executed
against an in-memory Derby 10.5.3.0 db
[ https://issues.apache.org/jira/browse/OPENJPA-1374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods resolved OPENJPA-1374.
-----------------------------------
Resolution: Fixed
Moved common Derby profiles to the parent POM.
Added new Derby props in o-p-j which knocked 2 mins off build time (12:24 down to 10:10 on Mac.)
Added a test-derbymem profile to parent POM to use Derby 10.5.3.0 as in-memory DB, which reduced o-p-j build time by 5 mins (12:24 down to :7:33 on Mac.)
> Enable junits to be executed against an in-memory Derby 10.5.3.0 db
> -------------------------------------------------------------------
>
> Key: OPENJPA-1374
> URL: https://issues.apache.org/jira/browse/OPENJPA-1374
> Project: OpenJPA
> Issue Type: Improvement
> Components: build / infrastructure
> Affects Versions: 2.0.0-M3
> Reporter: Donald Woods
> Assignee: Donald Woods
> Priority: Minor
> Fix For: 2.0.0
>
>
> Create a test profile that will enable the easy usage of an In-Memory Derby 10.5.3.0 DB for unit tests.
> http://wiki.apache.org/db-derby/InMemoryBackEndPrimer
> Initial testing on my Mac shows a 50% reduction in time to run the o-p-j bucket compared to the current test-derby profile....
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.