Problem: the Team menu no longer has selections for "commit", "update", etc.
Solution: Eclipse has forgotten your project was in SVN. Go to the Team menu, and select "Share Project". Select "SVN" in the next dialog, and Eclipse will tell you it thinks the project was already shared. Tell Eclipse that yes, in fact it was, and you should get all the menu items you need back.
Problem: Eclipse hangs with the progress bar partly across in the middle of commits.
Solution: This means some process did not release a SVN lock. Somebody probably started a commit, but didn't actually finish the process, or aborted it uncleanly. To verify this is actually the problem, try doing a SVN commit from the command line. That should either work, or give you a message telling you what the problem is.
If the problem actually is a lock, figure out if you (or a teammate!) have a commit that's waiting for you to finish a commit message before it completes. If so, finish the commit message and complete the commit. If not, make sure nobody but you is going to mess with your repository for the next few minutes, navigate to your svnroot (~/cse331/svnroot/ on IWS for the psets), and delete any files you find in subdirectories of there that start with '#'. This isn't the most elegant solution, but it's much better than not being able to commit at all.
Problem:Ant refuses to run at all, saying something about 'cd'.
Solution: This error comes from running the wrong version of
java or ant.
Make sure your $PATH (or equivlant), $JAVA_HOME (or
equivlant), $ANT_HOME (or equivalent), and all other pointers
to "The current versions of Ant and Java" are set up to point to Java
1.6 and Ant 1.8. On Linux, setting those environment variables
should be sufficient. On OS X 10.4, this
link gives a shell script that should set it up for you (the
process involves changing a symlink in the System folder).
Problem:ant test says it can't find the JUnit task.
Solution: To sucessfully run JUnit, Ant needs to know about two files: junit.jar, and ant-junit.jar. Ant first looks in $ANT_HOME/lib, then in the classpath defined in build.xml. The problem is, these two files both need to be in the same one of these places. If one is in $ANT_HOME/lib and the other is on the classpath, Ant will get confused and not be able to run the test target.