[
https://issues.apache.org/jira/browse/PHOENIX-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15232931#comment-15232931
]
Enis Soztutar commented on PHOENIX-2535:
----------------------------------------
bq. Once the dust settles here, it would be great to re-evaluate publishing
client jars to maven central. It's a real PITA to tell folks doing maven dev to
drop a jar into their resources manually.
Yes, we are going the maven module route rather than the assembly, so that the
jars will end up in maven repo. 4.8 RM should especially check whether the
publish is going through. We can do a a SNAPSHOT publish in the mean time just
to check.
bq. I hate to be the bearer of bad news, but these are most likely not meeting
ASF licensing requirements. For every bundled jar that Phoenix ships in a
shaded jar, we're going to have to
HBase's shaded modules do the right stuff I think. We can just copy from there.
> Create shaded clients (thin + thick)
> -------------------------------------
>
> Key: PHOENIX-2535
> URL: https://issues.apache.org/jira/browse/PHOENIX-2535
> Project: Phoenix
> Issue Type: Bug
> Reporter: Enis Soztutar
> Assignee: Sergey Soldatov
> Fix For: 4.8.0
>
> Attachments: PHOENIX-2535-1.patch, PHOENIX-2535-2.patch,
> PHOENIX-2535-3.patch, PHOENIX-2535-4.patch, PHOENIX-2535-5.patch
>
>
> Having shaded client artifacts helps greatly in minimizing the dependency
> conflicts at the run time. We are seeing more of Phoenix JDBC client being
> used in Storm topologies and other settings where guava versions become a
> problem.
> I think we can do a parallel artifact for the thick client with shaded
> dependencies and also using shaded hbase. For thin client, maybe shading
> should be the default since it is new?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
