Github user lresende commented on the issue:
https://github.com/apache/spark/pull/14981
Spark kinesis has dependency on the kinesis client which is category-x
<dependency>
<groupId>com.amazonaws</groupId>
<artifactId>amazon-kinesis-client</artifactId>
<version>${aws.kinesis.client.version}</version>
</dependency>
Thus I would say we should also avoid to automatically publish it in a
release and require a user to understand the license and build it themselves,
at least this was my interpretation around what was discussed in
https://issues.apache.org/jira/browse/LEGAL-198 and also at
http://www.apache.org/legal/resolved.html#optional.
Based on this, excluding the profile from published-profiles avoid
publishing both during a Spark release, but should not affect any of the other
build pieces for now.
Thoughts ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
