I think the creation of the IDE profiles is an important one to minimize impedance as much as possible in getting contributions.
We should have profiles available that work out of the box as much as possible for Eclipse, Netbeans, and IntelliJ. If someone wants to start tackling this, please feel free to create the associated ticket(s). Otherwise, I'll look into doing so this evening. On Tue, Apr 28, 2015 at 8:05 AM, Joe Witt <[email protected]> wrote: > Not that I am aware of. Netbeans defaults I believe work well. Will > defer to others for eclipse ideas. > > On Tue, Apr 28, 2015 at 8:29 AM, Dan Bress <[email protected]> > wrote: > > Has anyone created eclipse/netbeans formatting rules that we can use so > that "control-shift-f" and "alt-shift-f" format code that adheres to the > checkstyle rules? > > > > Dan Bress > > Software Engineer > > ONYX Consulting Services > > > > ________________________________________ > > From: Joe Witt <[email protected]> > > Sent: Tuesday, April 28, 2015 1:50 AM > > To: [email protected] > > Subject: NIFI-271 / refactored parent / checkstyle / rat / findbugs > > > > Hello All, > > > > I believe NIFI-271 [1] is now resolved. In it we: > > > > 1) completed the parent DRY refactoring identified by Benson a while ago > > > > 2) introduced checkstyle which is always running now. Refactored code > > and cleaned up 10s of thousands of violations. This should help with > > whitespace and other consistency issues that made reviews tougher. > > Might be some IDE lessons learned folks need to share. > > > > 3) cleaned up RAT logic and pushed special cases to their specific > > modules. I'd like RAT to always run but we had to keep it in a > > profile because it made build times way too long on some platforms. > > If you want to run this just add '-Pcheck-licenses' when building. > > > > 4) Introduced a profile for convenient execution of findbugs. Just > > add '-Pfindbugs' when building. There are many outstanding issues so > > it can't be made mandatory yet but we should work in that direction. > > We can add exclusions/filters for violations we disagree with in a > > module specific manner. > > > > So to get up to date on the latest goodness: > > > > git checkout develop > > git pull > > git clean -ffd > > cd nifi-parent > > mvn clean install > > cd ../nifi-nar-maven-plugin > > mvn clean install > > cd ../nifi > > mvn -T C1 clean install > > > > Please advise if you run into any trouble. > > > > [1] https://issues.apache.org/jira/browse/NIFI-271 > > > > Thanks > > Joe >
