Tis true, there are a couple of Collection methods they changed the behavior of, something like when an object is both a List and Stack, if you push then get (e.g.) it doesn't work the same. Since the scripting processors are still labelled Experimental (who might support custom scripts anyway?) I now tend to think we could move up to the latest 2.x version of Groovy, with a goal of Groovy 3.x for NiFi 2.0 (both the scripting NAR and the Groovy NAR), or whenever we bump to JDK >8. I was hesitant because the changes touched fundamental Java collections, but I am fine with upgrading the version if the community agrees. Thoughts?
Regards, Matt On Sat, May 25, 2019 at 7:52 PM Andy LoPresto <alopresto.apa...@gmail.com> wrote: > > Matt Burgess can answer with more detail but I do believe there are breaking > changes with collection interaction in 2.5.x. > > Andy LoPresto > alopre...@apache.org > alopresto.apa...@gmail.com > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > > On May 25, 2019, at 15:12, Mike Thomsen <mikerthom...@gmail.com> wrote: > > Groovy 3.0 apparently has hit beta 1 recently and 2.5.7 is the latest stable > build of 2.X. Are there any known compatibility reasons that would prevent us > from upgrading to 2.5.X in 1.10? This is directed as much at users as the > developers. > > Ideally, I'd like to upgrade to the latest 2.5.X in 1.10 and add a profile > build that lets people start trying out 3.X with a heavy "YMMV" warning. > > Thanks, > > Mike
