Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <1172713957.1241423850395.JavaMail.jira@brutus>
Date: Mon, 4 May 2009 00:57:30 -0700 (PDT)
From: =?utf-8?Q?Michael_D=C3=BCrig_=28JIRA=29?= <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Commented: (JCR-2096) Move jcr2spi tests to spi2jcr
In-Reply-To: <943536374.1241422890289.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/JCR-2096?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D127055=
14#action_12705514 ]=20

Michael D=C3=BCrig commented on JCR-2096:
------------------------------------

AFAIR the current approach was chosen such that the jcr2spi tests can be re=
-used for other SPI implementations.

> Move jcr2spi tests to spi2jcr
> -----------------------------
>
>                 Key: JCR-2096
>                 URL: https://issues.apache.org/jira/browse/JCR-2096
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-jcr2spi, jackrabbit-spi2jcr, test
>            Reporter: Jukka Zitting
>
> Currently we have a number of test cases included in the jcr2spi componen=
t, but they aren't being run in there (surefire plugin is disabled). Instea=
d, the tests are packaged into a -tests jar that is then used in the spi2jc=
r component to run them.
> The downside of this setup are 1) extra complexity and 2) the fact that a=
 -Dmaven.test.skip=3Dtrue build will not work with a clean Maven repository=
 as the jcr2spi -tests jar is not being built for spi2jcr.
> How about if we simply moved the tests to the spi2jcr component where the=
y are being used?

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