Github user simplesteph commented on the issue:
https://github.com/apache/nifi/pull/1135
No worries, Iâll build it on my own in my separate repos, see if people
have any usage for it, and based on adoption thinking of merging this into
the base.
What I really like though i
Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/1135
I don't think that's something we should do at this time. The NiFi build is
already long enough (10 - 20 minutes on commodity hardware depending on
multithreading, tests, and contrib-check) and I do
Github user simplesteph commented on the issue:
https://github.com/apache/nifi/pull/1135
good stuff. Quick question, what do you think of NiFi automating the build
and release of API clients in various language, vs me just maintaining it in my
own repos?
---
If your project is set u
Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/1135
I ran a full build of NiFi and everything was fine. I then used
`swagger-codegen` to build a Java client. Looks like it was successful (see
below).
+1, merging.
```
hw12203:/
Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/1135
Reviewing...
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if t
