Finalizing the code clean-up/ formatting settings (XML-document for Eclipse import)

[Christopher Keil]

USE CASE: WHAT DO YOU WANT TO DO?

Ensure a clean, formatted code base using agreed upon settings

STEPS TO REPRODUCE AN ISSUE (OR TRIGGER A NEW FEATURE)

n/a

CURRENT BEHAVIOR

No cleaning/ formatting is run before pushing a PR

EXPECTED BEHAVIOR

Devs run formatting & style clean-up using agrred upon settings (via importing an XML document to Eclipse) before pushing a PR.

DEVELOPERS ONLY SECTION SUGGESTED CHANGE (Pseudocode optional)

Propose and discuss changes in this issue thread.

FILES AFFECTED (where the changes will be implemented) - developers only

princeton_bioinf_eclipse_cleanup_profile.xml, princeton_bioinf_eclipse_codetemplate_profile.xml, princeton_bioinf_eclipse_formatter_profile.xml

LEVEL OF EFFORT - developers only

minor

COMMENTS

[Robert Leach]

Just to be explicit, I have proposed that the order of operations here be:

1. Edit the existing xml file (by importing the existing XML files into Eclipse and editing the settings using Eclipse)
2. Replace the current XML files in the repository & submit PR with the changes
3. Go through the review process and eventually merge the PR
4. Apply the automated formatting settings in a single commit to the entire repository & submit PR
5. Everyone pulls the changes

[Christopher Keil]

Sounds excellent to me.

[Christopher Keil]

Was resolved with pull request #68

[Robert Leach]

Removing milestone: Coding Convention Adherence (automated comment)