I've noticed that when changing branches tests would start failing in
eclipse despite them working when run from the command line.

I tried these series of steps:
ant clean
ant clean-eclipse
ant eclipse
Refresh eclipse project

but that didn't always work, because sometimes some .jar files would be in
stuck in the lib directories which would mess up the classpath, for
whatever reason that doesn't affect the command line, but it messes with
the build path in eclipse.


*The Solution(s):*
*The ant way:*
ant clean-jars

run this in addition to the other cleaning tasks above as well as ant
eclipse task

*The git way:*

git clean -fdX

git clean -- set directory back to pristine state of the git branch you are
on (i.e. delete all files which are not committed on your working tree)

-f -- force clean to run

-d -- also delete directories

-X -- this is very useful. It tells git clean to ONLY remove files which
are explicitly ignored in .gitignore and nothing else. Now all of your
patch files you have sitting in your top level directory will not be
deleted and neither will the extra .java class you just added.

-n -- dry run and print the files/directories which will be zapped.

another useful git command:

git ls-files --others

will print all untracked files in your working directory including things
which are in your .gitignore

Reply via email to