Return-Path: X-Original-To: apmail-incubator-accumulo-user-archive@minotaur.apache.org Delivered-To: apmail-incubator-accumulo-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 84FB09597 for ; Mon, 19 Mar 2012 18:43:01 +0000 (UTC) Received: (qmail 80449 invoked by uid 500); 19 Mar 2012 18:43:01 -0000 Delivered-To: apmail-incubator-accumulo-user-archive@incubator.apache.org Received: (qmail 80425 invoked by uid 500); 19 Mar 2012 18:43:01 -0000 Mailing-List: contact accumulo-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: accumulo-user@incubator.apache.org Delivered-To: mailing list accumulo-user@incubator.apache.org Received: (qmail 80416 invoked by uid 99); 19 Mar 2012 18:43:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Mar 2012 18:43:01 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [206.112.75.238] (HELO iron-u-a-out.osis.gov) (206.112.75.238) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Mar 2012 18:42:54 +0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApsFAKlWZ0+sEAbx/2dsb2JhbABCtkSBD4IJAQEBAwESAmoLCwQHDS4iEwUdGQgah2OdAgqdLI1agyIElWiQKIMC X-IronPort-AV: E=Sophos;i="4.73,612,1325480400"; d="scan'208";a="8761466" Received: from ghost-a.center.osis.gov (HELO mail-vx0-f175.google.com) ([172.16.6.241]) by iron-u-a-in.osis.gov with ESMTP/TLS/RC4-SHA; 19 Mar 2012 14:40:52 -0400 Received: by vcbfl13 with SMTP id fl13so7442531vcb.6 for ; Mon, 19 Mar 2012 11:42:30 -0700 (PDT) Received: by 10.220.149.79 with SMTP id s15mr5169628vcv.60.1332182550501; Mon, 19 Mar 2012 11:42:30 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.148.199 with HTTP; Mon, 19 Mar 2012 11:42:09 -0700 (PDT) In-Reply-To: <1182537943.225136.1332179907451.JavaMail.root@linzimmb04o.imo.intelink.gov> References: <199737055.224777.1332176326567.JavaMail.root@linzimmb04o.imo.intelink.gov> <1182537943.225136.1332179907451.JavaMail.root@linzimmb04o.imo.intelink.gov> From: John Vines Date: Mon, 19 Mar 2012 14:42:09 -0400 Message-ID: Subject: Re: Maven Artifacts for 1.3.5 missing? To: accumulo-user@incubator.apache.org Content-Type: multipart/alternative; boundary=f46d043894adb2d9b404bb9ceba1 X-Virus-Checked: Checked by ClamAV on apache.org --f46d043894adb2d9b404bb9ceba1 Content-Type: text/plain; charset=ISO-8859-1 We're attempting to release 1.4.0, so I would consider it stable for use. The thrift APIs have not changed much, if at all. But we maintain at least one version of backwards compatibility for the client api, so you should easily be able to get 1.3.x code to work against 1.4.0. John On Mon, Mar 19, 2012 at 1:58 PM, Robert Vesse wrote: > Is the 1.4.0 branch considered stable enough for use? And is it the API > compatible between 1.3.5 and 1.4.0 or do both the database and the client > need to be on the exact same version for communication to work correctly? > > Rob > > On Mar 19, 2012, at 10:06 AM, John Vines wrote: > > I believe we don't have them distributed because our poms do not include > adequate licensing info for us to publicly release them. 1.4.0 should be > released when we release it though. > > John > > On Mon, Mar 19, 2012 at 12:58 PM, Robert Vesse wrote: > >> Is there a reason why Maven artifacts for 1.3.5 are not available in the >> Apache repositories? >> >> Which Maven repositories (if any) are they available in? >> >> Rob >> > > > --f46d043894adb2d9b404bb9ceba1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable We're attempting to release 1.4.0, so I would consider it stable for us= e. The thrift APIs have not changed much, if at all. But we maintain at lea= st one version of backwards compatibility for the client api, so you should= easily be able to get 1.3.x code to work against 1.4.0.

John

On Mon, Mar 19, 2012 at 1:58 PM,= Robert Vesse <= rvesse@yarcdata.com> wrote:
Is the 1.4.0 branch considered stable enough for use? =A0And is it the= API compatible between 1.3.5 and 1.4.0 or do both the database and the cli= ent need to be on the exact same version for communication to work correctl= y?

Rob

On Mar 19, 2012, at 10:06 AM, John Vines wrote:

I believe we don't have them distributed beca= use our poms do not include adequate licensing info for us to publicly rele= ase them. 1.4.0 should be released when we release it though.

John

On Mon, Mar 19, 2012 at 12:58 PM, Robert Vesse <= span dir=3D"ltr"> <rvesse@yarcdat= a.com> wrote:
Is there a reason why Maven artifacts for 1.3.5 are not available in the Ap= ache repositories?

Which Maven repositories (if any) are they available in?

Rob



--f46d043894adb2d9b404bb9ceba1--