[ 
https://issues.apache.org/jira/browse/NIFI-5242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16492178#comment-16492178
 ] 

ASF subversion and git services commented on NIFI-5242:
-------------------------------------------------------

Commit 65beec39bb94e1a3af8654bdc2741892526b8193 in nifi's branch 
refs/heads/master from [~ca9mbu]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=65beec3 ]

NIFI-5242: Exclude JTS dependency from Elasticsearch client

This closes #2741

Signed-off-by: Mike Thomsen <[email protected]>


> Elasticsearch REST API client has LGPL dependency which must be removed
> -----------------------------------------------------------------------
>
>                 Key: NIFI-5242
>                 URL: https://issues.apache.org/jira/browse/NIFI-5242
>             Project: Apache NiFi
>          Issue Type: Bug
>            Reporter: Matt Burgess
>            Assignee: Matt Burgess
>            Priority: Major
>             Fix For: 1.7.0
>
>
> NIFI-4325 introduced a processor that made use of the Elasticsearch 5.x REST 
> API client (which replaced the older native transport client). However they 
> neglected to make the JTS dependency optional, as it is LGPL-licensed, and 
> thus it is included as a transitive dependency in NiFi, which is a violation 
> of the Apache Software Foundation guidelines.
> As it was apparently intended to be an optional dependency (see 
> [https://github.com/elastic/elasticsearch/issues/28899)], we should be able 
> to exclude it from the NiFi Maven build, but we'll need to run regression 
> tests to make sure nothing gets broken as a result.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to