accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2726) Maintain binary backwards compat for non-deprecated API components for 1.5 -> 1.6
Date Fri, 25 Apr 2014 17:17:19 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13981266#comment-13981266
] 

ASF subversion and git services commented on ACCUMULO-2726:
-----------------------------------------------------------

Commit f4454a06567c1fd4ff8b9a374d633a42c23a8a80 in accumulo's branch refs/heads/1.6.0-SNAPSHOT
from [~busbey]
[ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=f4454a0 ]

ACCUMULO-2726 Adds back missing methods for binary backwards compat with non-Deprecated methods
from 1.5.0. Marks things that we're for sure removing with @Deprecated; mostly things that
shouldn't have been in public to begin with.


> 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.0
>
>         Attachments: ACCUMULO-2726.1.patch.txt, ACCUMULO-2726.2.patch.txt, ACCUMULO-2726.3.patch.txt
>
>
> 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)

Mime
View raw message