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

ASF GitHub Bot commented on NIFI-3950:
--------------------------------------

Github user jvwing commented on the issue:

    https://github.com/apache/nifi/pull/2140
  
    @christophercurrie, thanks again for the work on this infrastructure 
project. 
    
    I merged these commits to master, except for the last commit "Limit NOTICE 
to AWS SDK" for nifi-aws-service-api-nar.  I lied about not needed all those 
dependency notices.  After checking with Maven, I understand  HttpComponents, 
Joda Time, etc. are transitive dependencies of the AWS SDK, and we need them 
even for the interfaces.  I apologize for the confusion about that, and thank 
you for adding it as a separate commit.
    
    I'll follow up with some text for the NiFi 1.5.0 migration notes.


> Separate AWS ControllerService API
> ----------------------------------
>
>                 Key: NIFI-3950
>                 URL: https://issues.apache.org/jira/browse/NIFI-3950
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: James Wing
>            Priority: Minor
>
> The nifi-aws-bundle currently contains the interface for the 
> AWSCredentialsProviderService as well as the service implementation, and 
> dependent abstract classes and processor classes.
> This results in the following warning logged as NiFi loads:
> {quote}
> org.apache.nifi.nar.ExtensionManager Component 
> org.apache.nifi.processors.aws.s3.PutS3Object is bundled with its referenced 
> Controller Service APIs 
> org.apache.nifi.processors.aws.credentials.provider.service.AWSCredentialsProviderService.
>  The service APIs should not be bundled with component implementations that 
> reference it.
> {quote}
> Some [discussion of this issue and potential solutions occurred on the dev 
> list|http://apache-nifi.1125220.n5.nabble.com/Duplicated-processors-when-using-nifi-processors-dependency-td17038.html].
> We also need a migration plan in addition to the new structure.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to