Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <700631002.1216389271891.JavaMail.jira@brutus>
Date: Fri, 18 Jul 2008 06:54:31 -0700 (PDT)
From: "angela (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Updated: (JCR-1629) SPI: Testsuite for the SPI Interfaces
In-Reply-To: <802420974.1212043725042.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

angela updated JCR-1629:
------------------------

    Fix Version/s: 1.5
         Assignee: angela

> SPI: Testsuite for the SPI Interfaces
> -------------------------------------
>
>                 Key: JCR-1629
>                 URL: https://issues.apache.org/jira/browse/JCR-1629
>             Project: Jackrabbit
>          Issue Type: New Feature
>          Components: jackrabbit-spi
>            Reporter: angela
>            Assignee: angela
>             Fix For: 1.5
>
>         Attachments: JCR-1629.diff, JCR-1629_jcr2spi.diff, JCR-1629_spi2jcr.diff
>
>
> now that people start writing SPI implementations we should provide a test-suite that runs on the SPI directly in order to provide the developers a way to assert basic compliance of their implementation without having the JCR api in between.

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