You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Vincent Poon (JIRA)" <ji...@apache.org> on 2018/11/30 02:42:00 UTC

[jira] [Resolved] (PHOENIX-1567) Publish Phoenix-Client & Phoenix-Server jars into Maven Repo

     [ https://issues.apache.org/jira/browse/PHOENIX-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vincent Poon resolved PHOENIX-1567.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 4.14.1

After applying PHOENIX-4781, I was able to publish the client and server jars for 4.14.1 here:
https://repository.apache.org/content/repositories/releases/org/apache/phoenix/phoenix-client/

Marking this resolved.

> 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
>             Fix For: 4.14.1
>
>         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)