jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Klimetschek (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-1419) Add test for database auto-reconnection (1.3 branch, JCR-1400)
Date Tue, 26 Feb 2008 11:15:51 GMT

     [ https://issues.apache.org/jira/browse/JCR-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Alexander Klimetschek updated JCR-1419:

    Attachment: jackrabbit-core.test-for-1400.patch

Patch that tests with an external derby server. This server is started as a Java process with
the derby, derbynet and derbyclient libraries in network server mode. Therefore I added derbynet
and derbyclient as test dependencies to the jackrabbit-core POM as well as specified their
versions in the root POM's dependencyManagement section.

Test failed before backporting JCR-940 and works fine after it.

Makes use of JCR-1412 for configuring jackrabbit without a repository.xml.

This test (o.a.j.core.persistence.DatabaseConnectionFailureTest) currently does not work with
"mvn test", only inside Eclipse. Therefore I disabled it in o.a.j.core.persistence.TestAll.
The problem is that the external derby server needs a classpath with derbynet and derbyclient,
which does not work with the way the maven-surefire-plugin sets the classpath. I am waiting
for some help from the maven users mailing list:


> Add test for database auto-reconnection (1.3 branch, JCR-1400)
> --------------------------------------------------------------
>                 Key: JCR-1419
>                 URL: https://issues.apache.org/jira/browse/JCR-1419
>             Project: Jackrabbit
>          Issue Type: Test
>          Components: jackrabbit-core, test
>            Reporter: Alexander Klimetschek
>             Fix For: 1.3.4
>         Attachments: jackrabbit-core.test-for-1400.patch
> Create a unit test for the database auto-reconnect feature in the 1.3 branch (JCR-1400).
> A test for the original feature JCR-940 in the trunk/1.4 needs a separate issue.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message