There shouldn't be any problem. I have many custom processors in a NAR I
haven't rebuilt since 1.12 and we use them successfully. They're just
missing versions because we had not yet upgraded the Maven we used to
build the NAR (not exactly relevant, I know, but I thought I'd I would
point this out).
On 4/13/21 8:55 AM, nathan.engl...@bt.com wrote:
Hi Joe,
Thanks for that information.
Will there be any issue in running a Custom NAR file built against
1.9.2 on a different versioned cluster. We haven’t experienced
anything yet, but would hate to spend ages in debugging an issue that
is the result of this!
Kind Regards,
Nathan
------------------------------------------------------------------------
*From:* Joe Witt <joe.w...@gmail.com>
*Sent:* Tuesday, April 13, 2021 5:48 pm
*To:* users@nifi.apache.org
*Subject:* Re: NiFi 1.11.4 Custom Processor Development
Hello
In moving to support maven 3.8 we found only https based repos are
allowed by default. In addressing this we updated the build to move
away from bintray and another location as well.
This is now the case when you build master. You could try to cherry
pick and edit the key commits or hang tight for us to kick out a 1.14
release. No time table for that yet though.
Thanks
On Tue, Apr 13, 2021 at 7:45 AM <nathan.engl...@bt.com
<mailto:nathan.engl...@bt.com>> wrote:
Hi There,
I am in the process of upgrading the version of the
nifi-nar-bundle from 1.9.2 to 1.12.1 however I’ve hit a unexpected
issue.
We develop on an offline platform, with Maven Central Mirrored
using a Nexus Repository Manager, with all dependencies delivered
through this mechanism. Today when I have changed the version from
1.9.2 to 1.12.1 I have found that the parent (I assume for the
groovy processor) has a dependency on groovy-eclipse-batch version
2.5.4-01 which seems to be only available from a Groovy Repository
(https://dl.bintray.com/groovy/maven/
<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdl.bintray.com%2Fgroovy%2Fmaven%2F&data=04%7C01%7Cnathan.english%40bt.com%7Cedb498f9213242aee05108d8fe8b3c57%7Ca7f356889c004d5eba4129f146377ab0%7C0%7C0%7C637539221253446565%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=9T1Ii386gRcclHLZw6Dw9%2FPEal1hrqaNGDjWAgJ6Hz8%3D&reserved=0>)
and not maven central.
I also noticed that bintray will be closing shortly
(https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/
<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fjfrog.com%2Fblog%2Finto-the-sunset-bintray-jcenter-gocenter-and-chartcenter%2F&data=04%7C01%7Cnathan.english%40bt.com%7Cedb498f9213242aee05108d8fe8b3c57%7Ca7f356889c004d5eba4129f146377ab0%7C0%7C0%7C637539221253456560%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=8nphGAZUMxc0QX19bvZMrhm6JdLBGpmdxktTSjsiccs%3D&reserved=0>),
so I guess the dependency will need correcting before then?
Kind Regards,
Nathan
Nathan English
Applications Specialist - Cyber Delivery & DevOps