[
https://issues.apache.org/jira/browse/NIFI-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16191853#comment-16191853
]
ASF GitHub Bot commented on NIFI-3950:
--------------------------------------
Github user bbende commented on the issue:
https://github.com/apache/nifi/pull/2140
@jvwing sorry I never responded to this... The results you got seem correct.
The part I wasn't sure about was that the `nifi-aws-nar-1.3.0.nar` has a
dependency on` nifi-standard-services-api-nar-1.3.0.nar`, so I thought you may
have to leave the whole change of dependencies around.
Looking at the code during start up, I think when loading the
`nifi-aws-nar-1.3.0.nar` we would detect that there is no 1.3.0 version of
`standard-services-api-nar` present, but there is a 1.4.0 version so just use
that, which is probably why it worked.
> 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)
