Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <861215595.1243418805639.JavaMail.jira@brutus>
Date: Wed, 27 May 2009 03:06:45 -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=12713507#action_12713507 ] 

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

yes... but the problem is not fixed by moving the classes. the problem was located in spi2jcr QPropertyDefinition as well...
i was looking at it... but now have a conflict.... hm....

in general: if the hudson builds for spi-related stuff fail, i will take a look at it (unless i'm off). why don't you let me know, when you
want to fix it? it's only 10 meters, isn't it?

> 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.