[
https://issues.apache.org/jira/browse/NIFI-640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14565728#comment-14565728
]
Matt Gilman commented on NIFI-640:
----------------------------------
[~danbress] Awesome. I spent some time last evening trying to get the automated
stuff working solely from the nifi-site side of things. Meaning I didn't try to
make any changes to the nifi build/release for this effort. While doing this I
was also trying to incorporate a suggestion from [~tkurc] to base the generated
documentation off of a specific branch/tag.
In my approach I was cloning the branch specified by the user (develop if
blank) and then building the release. My intent was to run the application and
then grab the generated documentation from NiFi using wget (this is how I
manually grab the documentation to throw on the website).
{code}wget -prk http://localhost:8080/nifi-docs/documentation{code}
Unfortunately, I got a little hung up on running the application because the
path of the execute (in nifi-assembly/target) contains the version numbers and
would change with successive releases. It was getting late so this is where I
stopped. I not entirely thrilled with this solution but it was the best I could
some up with. If we keep pressing in this direction I sure we can get it
figured out. However, it may be good for others like yourself to chime in and
maybe go at it from another angle.
I will move the work I'm doing into a branch so you can check it out and see
what I was up to. Thanks again.
> Add component documentation to website
> --------------------------------------
>
> Key: NIFI-640
> URL: https://issues.apache.org/jira/browse/NIFI-640
> Project: Apache NiFi
> Issue Type: Bug
> Components: Documentation & Website
> Reporter: Matt Gilman
> Assignee: Matt Gilman
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
