Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0D34911A33 for ; Wed, 23 Apr 2014 22:18:23 +0000 (UTC) Received: (qmail 88269 invoked by uid 500); 23 Apr 2014 22:18:20 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 88197 invoked by uid 500); 23 Apr 2014 22:18:19 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 88045 invoked by uid 99); 23 Apr 2014 22:18:18 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Apr 2014 22:18:18 +0000 Date: Wed, 23 Apr 2014 22:18:18 +0000 (UTC) From: "Sean Busbey (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (ACCUMULO-2726) Maintain binary backwards compat for non-deprecated API components for 1.5 -> 1.6 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated ACCUMULO-2726: ---------------------------------- Description: a JAPI compliane scan comparing 1.5.0 to 1.6.0-SNAPSHOT showed several incompatibilities in classes that probably never should have been in the public API * client.admin.SecurityOperationsImpl * client.admin.TableOperationsImpl * client.admin.InstanceOparationsImpl * client.mock.MockShell * client.mock.MockTabletLocator These changes are due to refactorings outside of the public API leaking into classes within the client that handle implementation. Since we're likely to break compatibility in the release after 1.6.0, try not to do it this time. Make sure to deprecate all these things, just in case there's a 1.7.0 was: a JAPI compliane scan comparing 1.5.0 to 1.6.0-SNAPSHOT showed several incompatibilities in classes that probably never should have been in the public API * client.admin.SecurityOperationsImpl * client.admin.TableOperationsImpl * client.admin.InstanceOparationsImpl * client.mock.MockShell * client.mock.MockTabletLocator These changes are due to refactorings outside of the public API leaking into classes within the client that handle implementation. For the next major release (i.e. 1.6.0) fix them to not be in the public API and include an apology in the release notes. We should also include other classes with names that end in Impl and other internal components of the Mock implementation. Affects Version/s: (was: 1.5.0) (was: 1.4.0) 1.6.0 Fix Version/s: (was: 1.6.0) 1.6.1 Labels: (was: incompatible) Summary: Maintain binary backwards compat for non-deprecated API components for 1.5 -> 1.6 (was: Move implementation details out of public api) > Maintain binary backwards compat for non-deprecated API components for 1.5 -> 1.6 > --------------------------------------------------------------------------------- > > Key: ACCUMULO-2726 > URL: https://issues.apache.org/jira/browse/ACCUMULO-2726 > Project: Accumulo > Issue Type: Task > Components: client > Affects Versions: 1.6.0 > Reporter: Sean Busbey > Assignee: Sean Busbey > Priority: Critical > Fix For: 1.6.1 > > > a JAPI compliane scan comparing 1.5.0 to 1.6.0-SNAPSHOT showed several incompatibilities in classes that probably never should have been in the public API > * client.admin.SecurityOperationsImpl > * client.admin.TableOperationsImpl > * client.admin.InstanceOparationsImpl > * client.mock.MockShell > * client.mock.MockTabletLocator > These changes are due to refactorings outside of the public API leaking into classes within the client that handle implementation. > Since we're likely to break compatibility in the release after 1.6.0, try not to do it this time. Make sure to deprecate all these things, just in case there's a 1.7.0 -- This message was sent by Atlassian JIRA (v6.2#6252)