db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5253) Engine code references org.apache.derby.shared.common.sanity.SanityManager
Date Sun, 12 Jun 2011 04:33:52 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13048227#comment-13048227

Dag H. Wanvik commented on DERBY-5253:

Would it be a good idea to make a small Wiki write-up on current state/ best practices when
it comes to the use of shared code? It's not obvious..

> Engine code references org.apache.derby.shared.common.sanity.SanityManager
> --------------------------------------------------------------------------
>                 Key: DERBY-5253
>                 URL: https://issues.apache.org/jira/browse/DERBY-5253
>             Project: Derby
>          Issue Type: Bug
>          Components: Miscellaneous
>    Affects Versions:
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>            Priority: Minor
>             Fix For:
>         Attachments: derby-5253-1a-engine_imports.diff
> Derby engine code is importing org.apache.derby.shared.common.sanity.SanityManager, causing
sealing violations. See DERBY-4669 why this fix is inadequate.
> Even though this won't fix the/all problems, using shared.common.sanity.SanityManager
on the client and iapi.services.sanity.SanityManager in the engine code is a simple rule to
follow. Violations are also easily addressed.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message