Mailing-List: contact commits-help@empire-db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: empire-db-dev@empire-db.apache.org
Date: Mon, 4 Feb 2013 14:12:14 +0000 (UTC)
From: =?utf-8?Q?Rainer_D=C3=B6bele_=28JIRA=29?=
 <empire-db-dev@incubator.apache.org>
To: empire-db-commits@incubator.apache.org
Message-ID: <JIRA.12446421.1264246539003.239454.1359987134032@arcas>
In-Reply-To: <JIRA.12446421.1264246539003@arcas>
References: <JIRA.12446421.1264246539003@arcas>
Subject: [jira] [Closed] (EMPIREDB-72) Change various private modifiers to
 protected to allow interception
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/EMPIREDB-72?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rainer D=C3=B6bele closed EMPIREDB-72.
---------------------------------


Cleanup of unclosed issues.
               =20
> Change various private modifiers to protected to allow interception
> -------------------------------------------------------------------
>
>                 Key: EMPIREDB-72
>                 URL: https://issues.apache.org/jira/browse/EMPIREDB-72
>             Project: Empire-DB
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: empire-db-2.0.6-incubating
>            Reporter: Rainer D=C3=B6bele
>            Assignee: Rainer D=C3=B6bele
>            Priority: Minor
>             Fix For: empire-db-2.0.6-incubating
>
>
> Many functions in DBCommand and the dataabase drivers are private but sho=
uld be protected.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira