Uh oh!
There was an error while loading. Please reload this page.
Phoenix 6377 - #1136
Conversation
dbwong
commented
Feb 10, 2021
Probably not entirely related to this but why do we need sqlline as a runtime dependency in the client? |
stoty
commented
Feb 10, 2021
We are traditionally including sqlline in phoenix-client for the sqlline.py client. I wouldn't be against unbundling it, in fact, I have already done that for the thin client. |
Lets unbundle in another jira (is there one already?) as it is not really a runtime dependency for the client. One thing we might want to consider is an import dependency so we can share a single pom across all of these client flavours. Any thoughts? EDIT: I guess it is not clear from the JIRA or here why we are pushing the dependency down. |
stoty
commented
Feb 10, 2021
I don't really get what you mean. We are already have most common setting in the parent pom. Can you add a little more detail ?
It is not clear to me either :( Not the first and not the last maven bug (or undocumented/unexplained behaviour) that we see. |
stoty
commented
Feb 10, 2021
💔 -1 overall
This message was automatically generated. |
dbwong
commented
Feb 10, 2021
I was referring to an approach like this https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Importing_Dependencies. But I was trying to understand why the client parent couldn't just be that other pom. |
stoty
commented
Feb 10, 2021
OK, now I understand what you mean. However, If you can make it work, then by all means open another ticket or an alternative PR with that solution. |
dbwong
commented
Feb 10, 2021
+1 I think i'd prefer to fix whatever is wrong with the shading to the approach I mentioned anyway. |
stoty
commented
Feb 10, 2021
💔 -1 overall
This message was automatically generated. |
No description provided.