You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Kristian Waagan (JIRA)" <ji...@apache.org> on 2011/06/01 12:03:47 UTC

[jira] [Closed] (DERBY-5253) Engine code references org.apache.derby.shared.common.sanity.SanityManager

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

Kristian Waagan closed DERBY-5253.
----------------------------------

          Resolution: Fixed
       Fix Version/s: 10.9.0.0
    Issue & fix info:   (was: [Patch Available])

Committed patch 1a to trunk with revision 1130077.
Closing issue.

> 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: 10.9.0.0
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>            Priority: Minor
>             Fix For: 10.9.0.0
>
>         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