[
https://issues.apache.org/jira/browse/ZOOKEEPER-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mate Szalay-Beko updated ZOOKEEPER-3630:
----------------------------------------
Description:
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, and fail only if we
the user explicitly requested the SSL support)
- we will add and document a custom maven parameter that will allow the user
to explicitly set the openssl library path, or to skip SSL support entirely
- we will also try to make the same logics during the windows build (cmake)
was:
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, and fail only if we the
user explicitly requested the SSL support)
- we will add and document a custom maven parameter that will allow the user to
explicitly set the openssl library path, or to skip SSL support entirely
- we will also try to make the same logics during the windows build (cmake)
> 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, and fail only if we
> the user explicitly requested the SSL support)
> - we will add and document a custom maven parameter that will allow the user
> to explicitly set the openssl library path, or to skip SSL support entirely
> - 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)
