phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-1567) Publish Phoenix-Client & Phoenix-Server jars into Maven Repo
Date Fri, 25 May 2018 21:34:00 GMT

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

Hudson commented on PHOENIX-1567:
---------------------------------

SUCCESS: Integrated in Jenkins build Phoenix-4.x-HBase-0.98 #1906 (See [https://builds.apache.org/job/Phoenix-4.x-HBase-0.98/1906/])
PHOENIX-1567 Publish Phoenix-Client & Phoenix-Server jars into Maven (ankitsinghal59:
rev 137ed5ee0545b92f5f67d95edbeb38662d98e914)
* (edit) phoenix-server/pom.xml
* (edit) phoenix-client/pom.xml


> 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
>            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)

Mime
View raw message