[GitHub] incubator-nifi pull request: NIFI-463

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[GitHub] incubator-nifi pull request: NIFI-463

JPercivall
GitHub user danbress opened a pull request:

    https://github.com/apache/incubator-nifi/pull/46

    NIFI-463

    When a component references a ControllerService API, the documentation generator will attempt to find implementations of that ControllerService API and provide a link to them in the html documentation

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/danbress/incubator-nifi NIFI-463

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-nifi/pull/46.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #46
   
----
commit 766ce5542148ad5eeaae62230b65797afa471234
Author: danbress <[hidden email]>
Date:   2015-03-24T14:54:32Z

    NIFI-463 adding links to controller service implementations

commit 75cad35661f019eb0212bed705798a9092c2dfb0
Author: danbress <[hidden email]>
Date:   2015-03-24T18:50:21Z

    NIFI-463 cleaning up code

----


---
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 [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|

[GitHub] incubator-nifi pull request: NIFI-463

JPercivall
Github user asfgit closed the pull request at:

    https://github.com/apache/incubator-nifi/pull/46


---
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 [hidden email] or file a JIRA ticket
with INFRA.
---