I agree more with Andy about sticking with Java. The more varying languages used, the more challenging it is to maintain. Once the code is part of the Apache NiFi git repo, it is now the responsibility of the committers and PMC members to maintain it.
I’d even say I am somewhat against the groovy/Spock test code that Andy mentioned. I have frequently spent hours trying to fix a Spock test that broke from something I was working on. Every committer is familiar with JUnit, but only a couple know Spock. Just using this as an example that every committer knows Java, but only a couple probably know Scala, Clojure, etc. On Sat, Feb 10, 2018 at 10:25 AM Jeff <jtsw...@gmail.com> wrote: > +1 to Joe's response. If you can develop a component in Groovy or Scala > (or Clojure!) more quickly/comfortably, or if allowing components written > in other languages would encourage people to contribute more, I'm all for > it. > > On Sat, Feb 10, 2018 at 7:42 AM Joe Witt <joe.w...@gmail.com> wrote: > > > i personally would be ok with it for an extension/processor provided it > > integrates well with the build. > > > > i would agree with andys view for core framework stuff but for > extensions i > > think we can do it like mikethomsen suggested. > > > > others? > > > > thanks > > joe > > > > On Feb 10, 2018 7:30 AM, "Mike Thomsen" <mikerthom...@gmail.com> wrote: > > > > > I'm just a community contributor, so take that FWIW, but a compromise > > might > > > be to publish the Scala code as separate maven modules to maven central > > and > > > then submit a thoroughly tested processor written in Java. As long as > you > > > have enough unit and integration tests to give strong coverage, I > > wouldn't > > > imagine anyone here would have issues reviewing it. If the tests fail > > > because of code issues in the external dependencies, the obvious answer > > is > > > to just hold the PR until the tests pass. > > > > > > On Fri, Feb 9, 2018 at 9:00 AM, Weiss, Adam < > adam.we...@perkinelmer.com> > > > wrote: > > > > > > > Devs, > > > > > > > > I have some interns starting with my team and we use Scala internally > > for > > > > our work. > > > > If I wanted to have them work to contribute some new processors, > would > > > > they have to be Java to be included with the base distribution or > could > > > > they use Scala as long as it fit within your current build and test > > > process? > > > > > > > > Thanks, > > > > -Adam > > > > > > > > > > -- Sent from Gmail Mobile
