I'm working on a new project with a full ANT build. I use eclipse to write my code, and I would like others to be able to check out the project to have a full working eclipse workspace. I do not want to have specific user settings committed though.
What files and directories should I have in source control?
(I'd rather not just go grab a plugin - I prefer more control over what goes in the repository)
None. Write a document explaining how to create an Eclipse project using a fresh checkout of the repository. Put that document in the repository as a readme, and update it as necessary. Each developer will have to create their own Eclipse project, but once they create the project, they don't have to do it ever again. It's really not that hard to do, especially if you have an existing Ant build script. I know that's not exactly answering your question, but I absolutely hate seeing IDE-specific files in a source tree.
We just put .project and .classpath in our repository, and that's sufficient to make it work "out of the box" for new developers. I'd like to have other stuff (run configurations come to mind), but haven't figured out how.
We use Subversion, so I put these files in a separate directory and defined svn:externals on that directory to point to the actual code, leaving it unpolluted by IDE-specific files.