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 is that the documentation generated for the API
    is stellar.
    
    
    On 14 October 2016 at 11:26:08 AM, Andy LoPresto (notificati...@github.com)
    wrote:
    
    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 don't think many people
    need this functionality, much less in multiple languages, and I don't know
    how we would determine the default languages -- maybe just Java to start as
    that's what the codebase is written in?
    
    If you want to submit a PR for a custom profile that builds the API
    clients, I wouldn't object to that as long as it was disabled by default.
    Not sure what others' feelings are.
    
    —
    You are receiving this because you authored the thread.
    Reply to this email directly, view it on GitHub
    <https://github.com/apache/nifi/pull/1135#issuecomment-253677513>, or mute
    the thread
    
<https://github.com/notifications/unsubscribe-auth/AT4rabcK5wAo8dv5KKU__y0sHge8-dKGks5qzswfgaJpZM4KWfwS>
    .



---
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 the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to