So, after all that it appears Toivo had it right! I tried not building it first and directly importing the maven project in to Eclipse, and Eclipse is now properly recognizing the different facets of the various modules. Huzzah!
Thanks everyone for your patience, and Toivo for the simple suggestion. That part should probably go in the developer’s quickstart guide under “For users of Eclipse…”. ☺ Kristin Clemens -----Original Message----- From: Toivo Adams [mailto:[email protected]] Sent: Sunday, May 31, 2015 7:15 AM To: [email protected]<mailto:[email protected]> Subject: Re: Best dev environment setup for front-end work? I use Eclipse and have done some Nifi development using Eclipse also. Eclipse is wonderful tool but Maven and Git integration feels like little bit unfinished. But this is no way related to NiFi. I usually check out NiFi source using command line Git (and not Eclipse Egit). After that I import NiFi stuff using Eclipse import... This way Eclipse builds correct Maven projects structure under Eclipse. NiFi development can be done using Eclipse and I am not sure switching to other IDE will help. NiFi projects structure is at first little bit complicated, but perfectly usable. Maybe this help you to create your own project: https://issues.apache.org/jira/browse/NIFI-272 Once you have your project structure created, you can add your code and dependencies to web jars under nifi-donothing-processors I personally have created new NiFi project structure (for my own NiFi processors) manually - works also, but more typing. Is “web-app” any way related to war files and possibly some container – Tomcat? Hope this helps, Toivo -- View this message in context: http://apache-nifi-incubating-developer-list.39713.n7.nabble.com/Best-dev-environment-setup-for-front-end-work-tp1665p1668.html Sent from the Apache NiFi (incubating) Developer List mailing list archive at Nabble.com.
