[
https://issues.apache.org/jira/browse/PHOENIX-6377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17283042#comment-17283042
]
Istvan Toth commented on PHOENIX-6377:
--------------------------------------
We expect built the phoenix-client artifacts to have empty dependency list, as
they have everything shaded in.
The bug only manifestes in the generated artifact's dependencies.
1. Take any many maven project, (I used mvn archetype:generate
-DarchetypeGroupId=org.apache.maven.archetypes
-DarchetypeArtifactId=maven-archetype-quickstart -DarchetypeVersion=1.4 to
generate an empty one)
2. Add one of the released 5.1.0 phoenix-client-* artifacts as a dependency to
the dummy project, or mvn install Phoenix locally, and add use the SNAPSHOT
version from that (i.e. 4.16.0 or 4.16.0-SNAPSHOT)
3. run mvn dependency:tree on the dummy project.
You can probably also check the pom.xml of the installed artifact in the local
cache or maven central, but I used the above method to check.
> phoenix-client has erronous maven dependecies
> ---------------------------------------------
>
> Key: PHOENIX-6377
> URL: https://issues.apache.org/jira/browse/PHOENIX-6377
> Project: Phoenix
> Issue Type: Bug
> Components: core
> Affects Versions: 5.1.0
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Critical
>
> depending on phoenix-client brings in phoenix-core, and all of its
> dependencies.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
