[
https://issues.apache.org/jira/browse/PHOENIX-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16488339#comment-16488339
]
tony kerz commented on PHOENIX-1567:
------------------------------------
ah, thanks for the feedback james and josh. a little further analysis clarifies:
{{org.apache.phoenix:phoenix-core:4.13.1-HBase-1.3}} in maven-central *is-not*
an uber-jar
{{phoenix-client }}*is* an uber-jar, but is obtained from distributions, and
*is-not* published to maven
i was having an issue connecting to an hdp install where i was told that some
hortonworks patches were required, so i grabbed the following from the hdp
maven-repo {{http://nexus-private.hortonworks.com/nexus/content/groups/public}}
{{org.apache.phoenix:phoenix-core:4.7.0.2.6.1.40-4}}
inexplicably, the above hdp version of {{phoenix-core}} *is* an uber-jar
similar to {{phoenix-client}} which gave me grief.
i apologize for the confusion on this thread, i will take up my specific issue
with hortonworks.
> 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
>
> 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)
