From dev-return-52397-archive-asf-public=cust-asf.ponee.io@phoenix.apache.org Sat Jun 9 01:17:05 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 D91B3180674 for ; Sat, 9 Jun 2018 01:17:04 +0200 (CEST) Received: (qmail 18351 invoked by uid 500); 8 Jun 2018 23:17:03 -0000 Mailing-List: contact dev-help@phoenix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@phoenix.apache.org Delivered-To: mailing list dev@phoenix.apache.org Received: (qmail 18337 invoked by uid 99); 8 Jun 2018 23:17:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Jun 2018 23:17:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 60BB0C02AA for ; Fri, 8 Jun 2018 23:17:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 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, 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 (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id bINj-F-NT7tA for ; Fri, 8 Jun 2018 23:17: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 B337F5F359 for ; Fri, 8 Jun 2018 23:17: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 D07EBE0E4B for ; Fri, 8 Jun 2018 23:17: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 36C992109C for ; Fri, 8 Jun 2018 23:17:00 +0000 (UTC) Date: Fri, 8 Jun 2018 23:17:00 +0000 (UTC) From: "Pedro Boado (JIRA)" To: dev@phoenix.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (PHOENIX-1567) Publish Phoenix-Client & Phoenix-Server jars into Maven Repo 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/PHOENIX-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16506685#comment-16506685 ] Pedro Boado commented on PHOENIX-1567: -------------------------------------- [~ankit@apache.org] by changing that value this coordinate gets pushed ( with classifier shaded ) . No original artiffact is published - because it is replaced - {code} org.apache.phoenix phoenix-client 4.14.0-cdh5.11.2 shaded {code} What is the idea, getting it published with or without the classifier? > Publish Phoenix-Client & Phoenix-Server jars into Maven Repo > ------------------------------------------------------------ > > Key: PHOENIX-1567 > URL: https://issues.apache.org/jira/browse/PHOENIX-1567 > Project: Phoenix > Issue Type: Bug > Affects Versions: 4.2.0 > Reporter: Jeffrey Zhong > Assignee: Ankit Singhal > Priority: Major > Attachments: PHOENIX-1567.patch > > > Phoenix doesn't publish Phoenix Client & Server jars into Maven repository. This make things quite hard for down steam projects/applications to use maven to resolve dependencies. > I tried to modify the pom.xml under phoenix-assembly while it shows the following. > {noformat} > [INFO] Installing /Users/jzhong/work/phoenix_apache/checkins/phoenix/phoenix-assembly/target/phoenix-4.3.0-SNAPSHOT-client.jar > to /Users/jzhong/.m2/repository/org/apache/phoenix/phoenix-assembly/4.3.0-SNAPSHOT/phoenix-assembly-4.3.0-SNAPSHOT-client.jar > {noformat} > Basically the jar published to maven repo will become phoenix-assembly-4.3.0-SNAPSHOT-client.jar or phoenix-assembly-4.3.0-SNAPSHOT-server.jar > The artifact id "phoenix-assembly" has to be the prefix of the names of jars. > Therefore, the possible solutions are: > 1) rename current client & server jar to phoenix-assembly-clinet/server.jar to match the jars published to maven repo. > 2) rename phoenix-assembly to something more meaningful and rename our client & server jars accordingly > 3) split phoenix-assembly and move the corresponding artifacts into phoenix-client & phoenix-server folders. Phoenix-assembly will only create tar ball files. > [~giacomotaylor], [~apurtell] or other maven experts: Any suggestion on this? Thanks. -- This message was sent by Atlassian JIRA (v7.6.3#76005)