The include must be in the first line, else you may expect some issues.
Some autoformat tools could sort the includes alphabetically and could
break the test.

- Fixed some style issues.

Started to flesh out rubocop settings for this project. Added rakefile tasks to do so. Updated first script to make it compliant.

Starting to enforce our coding style. The first step is that we’ve pulled in Rubocop to check out Ruby syntax. There is likely a bit of customization to do yet AND there is definitely that backlog of todo’s that we just told it to ignore.

This resolves #219. When generating a new module, if all the files to
generate already exist then it fails as before. If some of the files
already exist, then the files that need to be created are created. Any
existing files are not changed.

Also added a bunch of tests for this feature via rspec. Run them from
the test folder with `rake spec`.

- configurable case.
- better passing of includes and boilerplate information
- test only pattern
- optional naming conventions for case

refactor generate_module so that it can be called as a class from within Ceedling (much like the test runner generator)

git-svn-id: http://unity.svn.sourceforge.net/svnroot/unity/trunk@109 e7d17a6e-8845-0410-bbbc-c8efb4fdad7e

- restored makefiles to working condition
- updated files to include copyright notice
- fixed bug in string array comparisons
- ignored tests no longer run teardown
- tests failing for uncaught cexceptions now get exception id reported

git-svn-id: http://unity.svn.sourceforge.net/svnroot/unity/trunk@70 e7d17a6e-8845-0410-bbbc-c8efb4fdad7e

git-svn-id: http://unity.svn.sourceforge.net/svnroot/unity/trunk@50 e7d17a6e-8845-0410-bbbc-c8efb4fdad7e