Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <889566444.1243417966094.JavaMail.jira@brutus>
Date: Wed, 27 May 2009 02:52:46 -0700 (PDT)
From: "angela (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Commented: (JCR-2122) Use ValueConstraint from spi-commons
 in core
In-Reply-To: <1531333401.1243416405783.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-2122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713500#action_12713500 ] 

angela commented on JCR-2122:
-----------------------------

this is already covered by another issue: merge nodetype stuff....  i guess we can resolve this as duplicate.

the reason why it wasn't possible up to now where incompatibilities in signature (yes i tried it!)... 
since now InternalValue implements QValue this should be feasible.
but i discussed with stefan, that i wait with any kind of nodetype work until he completed the ri in core... in order not to get too much conflicts.


> Use ValueConstraint from spi-commons in core
> --------------------------------------------
>
>                 Key: JCR-2122
>                 URL: https://issues.apache.org/jira/browse/JCR-2122
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core, jackrabbit-spi-commons
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>            Priority: Minor
>
> There is quite a lot of duplication between the ValueConstraint classes in core and spi-commons. It would be better to maintain just a single copy of this functionality, so I'd like to change jackrabbit-core to use the classes from spi-commons as much as possible.

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