From dev-return-8868-archive-asf-public=cust-asf.ponee.io@curator.apache.org Thu Feb 15 14:39:06 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 4FFB018064A for ; Thu, 15 Feb 2018 14:39:05 +0100 (CET) Received: (qmail 87216 invoked by uid 500); 15 Feb 2018 13:39:04 -0000 Mailing-List: contact dev-help@curator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@curator.apache.org Delivered-To: mailing list dev@curator.apache.org Received: (qmail 87199 invoked by uid 99); 15 Feb 2018 13:39:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Feb 2018 13:39:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id EB72D180355 for ; Thu, 15 Feb 2018 13:39:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.511 X-Spam-Level: X-Spam-Status: No, score=-109.511 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id Ckg50y9IwPkc for ; Thu, 15 Feb 2018 13:39:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 377C65F30B for ; Thu, 15 Feb 2018 13:39:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 64594E00EA for ; Thu, 15 Feb 2018 13:39:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 1FE5C21E59 for ; Thu, 15 Feb 2018 13:39:00 +0000 (UTC) Date: Thu, 15 Feb 2018 13:39:00 +0000 (UTC) From: "Simon Billingsley (JIRA)" To: dev@curator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (CURATOR-454) Curator 4.0.0 be used with Zookeeper 3.4.10 due to compile-time issues MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CURATOR-454?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D163= 65533#comment-16365533 ]=20 Simon Billingsley edited comment on CURATOR-454 at 2/15/18 1:38 PM: -------------------------------------------------------------------- Yes, I have read that and=C2=A0I am still seeing these compile-time issues. We initially had issues running curator-test until I downgraded back to 2.1= 2.0 of that (thanks to that wiki page) but this module does not use curator= -test.=C2=A0 The module uses curator-framework implicitly as we have writte= n a wrapper library around curator which depends on zookeeper/curator that = is used by this module. Here is an extract from the module pom.xml (we include the zookeeper / cura= tor libraries directly as this is a war which must be deployed): {{}} {{=C2=A0 org.apache.zookeeper}} {{=C2=A0 zookeeper}} {{=C2=A0 3.4.10}} {{=C2=A0 compile}} {{}} {{}} {{=C2=A0 org.apache.curator}} {{=C2=A0 curator-framework}} {{=C2=A0 4.0.0}} {{=C2=A0 compile}} {{=C2=A0 }} {{=C2=A0 =C2=A0 }} {{=C2=A0 =C2=A0 =C2=A0 org.apache.zookeeper}} {{=C2=A0 =C2=A0 =C2=A0 zookeeper}} {{=C2=A0 =C2=A0 }} {{=C2=A0 }} {{}} {{}} {{=C2=A0 org.apache.curator}} {{=C2=A0 curator-client}} {{=C2=A0 4.0.0}} {{=C2=A0 compile}} {{=C2=A0 }} {{=C2=A0 =C2=A0 }} {{=C2=A0 =C2=A0 =C2=A0 org.apache.zookeeper}} {{=C2=A0 =C2=A0 =C2=A0 zookeeper}} {{=C2=A0 =C2=A0 }} {{=C2=A0 }} {{}} {{}} {{=C2=A0 org.apache.curator}} {{=C2=A0 curator-x-discovery}} {{=C2=A0 4.0.0}} {{=C2=A0 compile}} {{=C2=A0 }} {{=C2=A0 =C2=A0 }} {{=C2=A0 =C2=A0 =C2=A0 org.apache.zookeeper}} {{=C2=A0 =C2=A0 =C2=A0 zookeeper}} {{=C2=A0 =C2=A0 }} {{=C2=A0 }} {{}} was (Author: sishbi): Yes, I have read that and=C2=A0I am still seeing these compile-time issues. We initially had issues running curator-test until I downgraded back to 2.1= 2.0 of that (thanks to that wiki page) but this module does not use curator= -test.=C2=A0 The module uses curator-framework implicitly as we have writte= n a wrapper library around curator which depends on zookeeper/curator that = is used by this module. Here is an extract from the module pom.xml (we include the zookeeper / cura= tor libraries directly as this is a war which must be deployed): {{ }} {{=C2=A0 org.apache.zookeeper}} {{=C2=A0 zookeeper}} {{=C2=A0 3.4.10}} {{=C2=A0 compile}} {{ }} {{ }} {{=C2=A0 org.apache.curator}} {{=C2=A0 curator-framework}} {{=C2=A0 4.0.0}} {{=C2=A0 compile}} {{=C2=A0 }} {{=C2=A0 =C2=A0 }} {{=C2=A0 =C2=A0 =C2=A0 org.apache.zookeeper}} {{=C2=A0 =C2=A0 =C2=A0 zookeeper}} {{=C2=A0 =C2=A0 }} {{=C2=A0 }} {{ }} {{ }} {{=C2=A0 org.apache.curator}} {{=C2=A0 curator-client}} {{=C2=A0 4.0.0}} {{=C2=A0 compile}} {{=C2=A0 }} {{=C2=A0 =C2=A0 }} {{=C2=A0 =C2=A0 =C2=A0 org.apache.zookeeper}} {{=C2=A0 =C2=A0 =C2=A0 zookeeper}} {{=C2=A0 =C2=A0 }} {{=C2=A0 }} {{ }} {{ }} {{=C2=A0 org.apache.curator}} {{=C2=A0 curator-x-discovery}} {{=C2=A0 4.0.0}} {{=C2=A0 compile}} {{=C2=A0 }} {{=C2=A0 =C2=A0 }} {{=C2=A0 =C2=A0 =C2=A0 org.apache.zookeeper}} {{=C2=A0 =C2=A0 =C2=A0 zookeeper}} {{=C2=A0 =C2=A0 }} {{=C2=A0 }} {{ }} > Curator 4.0.0 be used with Zookeeper 3.4.10 due to compile-time issues > ---------------------------------------------------------------------- > > Key: CURATOR-454 > URL: https://issues.apache.org/jira/browse/CURATOR-454 > Project: Apache Curator > Issue Type: Bug > Components: Framework > Affects Versions: 4.0.0 > Reporter: Simon Billingsley > Priority: Major > > I see compile issues when trying to compile a project=C2=A0with=C2=A0a li= brary that depends on apache curator 4.0.0.=C2=A0 > We are trying to upgrade to a newer version of Zookeeper (3.4.10) due to = security issues in ZK 3.4.9 and have been forced to upgrade to a newer vers= ion of curator (from 2.11.1 due to other curator issues) but we keep hittin= g compile-time issues (see below)=C2=A0which mean that we need to use ZK 3.= 5.3-beta at compile time even though we=C2=A0will=C2=A0use ZK 3.4.10 at run= time. > Here is an example of the javac verbose output (via maven): > {{[loading ZipFileIndexFileObject[/Users/sbilling/.m2/repository/org/apac= he/curator/curator-framework/4.0.0/curator-framework-4.0.0.jar(org/apache/c= urator/framework/api/transaction/CuratorOp.class)]]}} > {{[loading ZipFileIndexFileObject[/Users/sbilling/.m2/repository/org/apac= he/zookeeper/zookeeper/3.4.10/zookeeper-3.4.10.jar(org/apache/zookeeper/Op.= class)]]}} > {{[loading ZipFileIndexFileObject[/Users/sbilling/.m2/repository/org/apac= he/zookeeper/zookeeper/3.4.10/zookeeper-3.4.10.jar(org/apache/zookeeper/Op$= Create.class)]]}} > {{[loading ZipFileIndexFileObject[/Users/sbilling/.m2/repository/org/apac= he/zookeeper/zookeeper/3.4.10/zookeeper-3.4.10.jar(org/apache/zookeeper/Op$= Delete.class)]]}} > {{[loading ZipFileIndexFileObject[/Users/sbilling/.m2/repository/org/apac= he/zookeeper/zookeeper/3.4.10/zookeeper-3.4.10.jar(org/apache/zookeeper/Op$= SetData.class)]]}} > {{[loading ZipFileIndexFileObject[/Users/sbilling/.m2/repository/org/apac= he/zookeeper/zookeeper/3.4.10/zookeeper-3.4.10.jar(org/apache/zookeeper/Op$= Check.class)]]}} > {{[loading ZipFileIndexFileObject[/Users/sbilling/.m2/repository/org/apac= he/curator/curator-framework/4.0.0/curator-framework-4.0.0.jar(org/apache/c= urator/framework/api/transaction/TypeAndPath.class)]]}} > {{[loading ZipFileIndexFileObject[/Users/sbilling/.m2/repository/org/apac= he/curator/curator-framework/4.0.0/curator-framework-4.0.0.jar(org/apache/c= urator/framework/api/SyncBuilder.class)]]}} > {{[loading ZipFileIndexFileObject[/Users/sbilling/.m2/repository/org/apac= he/curator/curator-framework/4.0.0/curator-framework-4.0.0.jar(org/apache/c= urator/framework/api/RemoveWatchesBuilder.class)]]}} > {{[loading ZipFileIndexFileObject[/Users/sbilling/.m2/repository/org/apac= he/curator/curator-framework/4.0.0/curator-framework-4.0.0.jar(org/apache/c= urator/framework/api/RemoveWatchesType.class)]]}} > {{[loading ZipFileIndexFileObject[/Users/sbilling/.m2/repository/org/apac= he/curator/curator-framework/4.0.0/curator-framework-4.0.0.jar(org/apache/c= urator/framework/api/RemoveWatchesLocal.class)]]}} > {{[loading ZipFileIndexFileObject[/Users/sbilling/.m2/repository/org/apac= he/curator/curator-framework/4.0.0/curator-framework-4.0.0.jar(org/apache/c= urator/framework/api/BackgroundPathableQuietlyable.class)]]}}{{java.lang.Ru= ntimeException: com.sun.tools.javac.code.Symbol$CompletionFailure: class fi= le for org.apache.zookeeper.Watcher$WatcherType not found}} > If I look through the source code I see that RemoveWatchesType=C2=A0impor= ts and uses=C2=A0org.apache.zookeeper.Watcher$WatcherType in the 'ofType' m= ethod. > I don't understand how the backwards-compatibility is meant to work. It i= s also strange that this compile error only appears for a few of the module= s in the project, so it must depend on which classes are used by the librar= y and so which classes are loaded into the compile tree. -- This message was sent by Atlassian JIRA (v7.6.3#76005)