[
https://issues.apache.org/jira/browse/PHOENIX-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15658153#comment-15658153
]
Randy Gelhausen edited comment on PHOENIX-1567 at 11/11/16 8:56 PM:
--------------------------------------------------------------------
+1 for revisiting this decision.
Apache NiFi and Apache Zeppelin allow users to supply arbitrary JDBC jars.
Without published artifacts for shaded jars, the end-user needs to:
1. Hit phoenix.apache.org -> Downloads -> Select a mirror -> Download and
uncompress a tarball
2. Determine whether they'll be using the queryserver
3. Pick the right jar from the litany of extremely similarly named jars
4. Manually copy that jar into NiFi or Zeppelin's local resource directories
It's a lot of work to ask a user to do instead of supplying:
org.apache.phoenix:phoenix-thin-client:4.8.0-HBase-1.1 (or phoenix-thick).
was (Author: randerzander):
+1 for revisiting this decision.
Apache NiFi and Apache Zeppelin allow users to supply arbitrary JDBC jars.
Without published artifacts for shaded jars, the end-user needs to:
1. Hit phoenix.apache.org -> Downloads -> Select a mirror -> Download and
uncompress a tarball
2. Determine whether they'll be using the queryserver
3. Pick the right jar from the litany of extremely similarly named jars
4. Manually copy that jar into NiFi or Zeppelin's local resource directories
It's a lot of work to ask a user to do instead of supplying:
org.apache.phoenix:phoenix-queryserver-client:4.8.0-HBase-1.1 (or phoenix-core).
> 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
>
> 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
(v6.3.4#6332)
