Well I wanted to return to the group and report that I jumped the gun, and that I have now achieved a successful build of the master branch 1.9.0-SNAPSHOT. I put myself back on the master branch and continued to dig going this time to the development quickstart ( http://nifi.apache.org/quickstart.html). I found there that you have to run the following command:
mvn -T C2.0 clean install -Pinclude-grpc I was just running 'mvn clean compile' and I think the module nifi-toolkit-tls must have some kind of dependency that requires the "include-grpc" flag. Because that was where my dependency errors were coming from. I have not verified this though. It could also be that there are areas of the build that don't respond the same way to the targets I passed in vs. the targets in the command that were successful. I still have some investigation to do to be sure I understand this completely. I'm going to keep reading but I still have the same questions about contributions as before. With Jira I'm noticing there are some stories that say "in progress" or "patch available" but none of them have an assignee. Is the transition between these states driven by automation or are people manually updating the stories in Jira? Thanks, Ryan On Wed, Jan 23, 2019 at 5:56 PM Ryan Withers <[email protected]> wrote: > To whom it may concern, > > So my goal is to begin making contributions to the nifi product. Right > now I'm just trying to build the product from source and having some > difficulty. > > I've listed out the branches associated with the following repository (git > clone https://git-wip-us.apache.org/repos/asf/nifi.git) > > I don't see any support branches related to 1.8.0 and it seems like the > master branch has already been bumped to 1.9.0. I recognize that if I > want to contribute a change it likely has to be done against 1.9.0 rather > than 1.8.0 but I've been having build issues against 1.9.0. However, I did > have a successful build against support/nifi-1.7.x. > > Once I have the appropriate version of the source compiling I plan to pick > an issue from your jira instance which I've been reading through. Then > perform a modification and walk through the pull request process. With > Jira I'm noticing there are some stories that say "in progress" or "patch > available" but none of them have an assignee. Is the transition between > these states driven by automation or are people manually updating the > stories in Jira? > > Thanks in advance, > > Ryan > > -- > Ryan Withers > Senior Software Developer / Analyst > > http://www.linkedin.com/in/ryanwithers > > -- Ryan Withers Senior Software Developer / Analyst http://www.linkedin.com/in/ryanwithers
