Projects with poor .gitignore coverage cause problems in ~/.voom-repos/

[abrooks]

Some projects don't sufficiently exclude build side effects (such as artifacts landing in target/) in their .gitignore files. When this happens in projects in ~/.voom-repos/, it prevents being able to automatically build voom versioned artifacts for the given project until the user clears the offending state (such as via a git checkout . in the ~/.voom-repos/ project directory).

Likely, since voom owns the ~/.voom-repos/ subdirectories, we should force a git-clean before checking out new versions which will fix this problem.

[abrooks]

A work around, particularly for badly behaved 3rd party projects might be to allow git ignore patterns to be specified in the voom metadata.