[PHOENIX-1567] Publish Phoenix-Client & Phoenix-Server jars into Maven Repo

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.2.0
• Fix Version/s: 4.14.1
• Assignee: Ankit Singhal
• Reporter: Jeffrey Zhong
• Created: 30/Dec/14 23:15
• Updated: 29/Jul/19 03:36
• Resolved: 30/Nov/18 02:41

Description

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.

[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

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.

Issue Links

• is related to: PHOENIX-4781 Phoenix client project's jar naming convention causes maven-deploy-plugin to fail
• relates to: PHOENIX-4741 Shade disruptor dependency