I may have something to test that ;) I’ll let you know, else my pr will
get the ‘why are you updating the sdk version’ comment.
On March 16, 2018 at 15:57:21, Bryan Bende (bbe...@gmail.com) wrote:
This should be better going forward once the 1.6.0 release is out.
https://issues.apache.org/jir
This should be better going forward once the 1.6.0 release is out.
https://issues.apache.org/jira/browse/NIFI-4936
On Fri, Mar 16, 2018 at 3:49 PM, Otto Fowler wrote:
> This is also a problem for new AWS processors, say if you use a newer aws
> java sdk core in a dependency but also have to depe
This is also a problem for new AWS processors, say if you use a newer aws
java sdk core in a dependency but also have to depend on the nifi-aws-nar.
On March 2, 2018 at 13:40:21, Bryan Bende (bbe...@gmail.com) wrote:
Doug,
I think the only solution is what you proposed about fixing the
nifi-gcp
i suspect we can eliminate the dependency management section
altogether at this point in the parent pom.
On Fri, Mar 2, 2018 at 1:40 PM, Bryan Bende wrote:
> Doug,
>
> I think the only solution is what you proposed about fixing the
> nifi-gcp-bundle...
>
> Basically, if a NAR needs a different ve
Doug,
I think the only solution is what you proposed about fixing the
nifi-gcp-bundle...
Basically, if a NAR needs a different version of a dependency that is
already declared in the root pom's dependencyManagement, then the
bundle's pom needs it own dependencyManagement to force it back to the
s
Hi all,
I'm encountering a JAR version dependency issue when developing a custom
Processor that uses the GCPCredentialsService in Nifi 1.5.0.
1) The nifi-gcp-bundle distributed with Nifi 1.5.0 (which contains
GCPCredentialsService) is packaged with dependencies on:
- com.google.cloud:google-c