[
https://issues.apache.org/jira/browse/KUDU-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16442599#comment-16442599
]
Grant Henke commented on KUDU-2186:
-----------------------------------
This occurs in Gradle because dependent modules consume the shaded jar, the
same as if they were not a part of the project. Where in Maven shading is only
done during packaging so the actual generated artifacts are not used.
The return type of ProtobufHelper.hostAndPortFromPB is
com.google.common.net.HostAndPort, but because we shade and relocate Guava
(expecting it's use to be internal only) it get's relocated to
org.apache.kudu.shaded.com.google.common.net.HostAndPort.
The issue is the test classpath is different at compile time than runtime
somehow. I have some idea what might be going on and will look to fix this.
> Gradle shading of kudu-client test JAR is broken
> ------------------------------------------------
>
> Key: KUDU-2186
> URL: https://issues.apache.org/jira/browse/KUDU-2186
> Project: Kudu
> Issue Type: Bug
> Components: java
> Affects Versions: 1.5.0
> Reporter: Adar Dembo
> Assignee: Grant Henke
> Priority: Major
>
> I don't understand the details, but I know that if MiniKuduCluster calls a
> kudu-client ProtobufHelper method, the kudu-client-tools tests fail to run in
> Gradle. This isn't an issue with Maven.
> I've worked around this by duplicating the one ProtobufHelper method used by
> MiniKuduCluster into that class.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
