[
https://issues.apache.org/jira/browse/ZOOKEEPER-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16984215#comment-16984215
]
Mate Szalay-Beko commented on ZOOKEEPER-3630:
---------------------------------------------
sure, no pressure :)
(anyway, I hope I can submit a PR today or tomorrow)
I am not sure if you know this already, but if you add a comment '{{retest
maven build}}' to a ZooKeeper PR, then it will kick a new build job in jenkins
and update the PR with the results.
> Autodetection of SSL library during Zookeeper C client build
> ------------------------------------------------------------
>
> Key: ZOOKEEPER-3630
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3630
> Project: ZooKeeper
> Issue Type: Improvement
> Components: c client
> Affects Versions: 3.5.6
> Reporter: Mate Szalay-Beko
> Assignee: Mate Szalay-Beko
> Priority: Major
>
> After submitting [https://github.com/apache/zookeeper/pull/1107] about SSL
> support in ZooKeeper C client, [~ztzg] shared some very good improvement
> ideas, so we will now:
> - use the {{--with-openssl}} autoconf argument in the same way as SASL is
> doing (i.e. by default we autodetect the openssl library, but with the option
> we can turn off SSL or specify a custom location for openssl lib)
> - we will add and document a custom maven parameter that will be used during
> the c-client build
> - we will also try to make the same logics during the windows build (cmake)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
