What it means is that you can't put those files in your source control. If you care to see this folder, you will find many files that read like org.eclipse.* etc. classpath file) dependencies are saved in user's workspace folder. The problem with eclipse is that a project (i.e. Once it builds, you would check them into your source control. Usually you want to have individual projects and be able to establish dependencies among them. Everything has to be below the project root folder.

Eclipse won't let you include source code that is outside the project root folder. We have a big project (around 600K lines of code) organized in many folders. From java editor point of view, both have excellent context sensitive help and the usual goodies.Įclipse sucks when it comes to setting up projects that other team members can open and use. So, if you don't know a bunch of keystrokes that already tie you to an editor, the up and coming is Netbeans-don't pass it up because of a bunch of Eclipse votes.īetter yet, get good with both-it can't hurt and makes me a lot more comfortable when a company requires one or another. This thing is pretty damn cool, but few people seem to even know it exists. Mylyn (it's been renamed, it used to be called Mylar).

Netbeans has more languages supported and more all-around support-so it's growing faster.Ĭurrently I use Eclipse-I've used both (and IntelliJ and TextMate and Notepad.) and I can tell you that Eclipse has exactly one feature over netbeans.

This is because it was better and more people use it-and it's just human nature to feel what you are using is the best and everyone should use it.īecause it was better does not mean it's better now.

Now Netbeans has caught up (perhaps surpassed) and has a lot of momentum. Eclipse used to be a good deal quicker because they didn't use Swing. Just to be sure you give them fair consideration, Eclipse and Netbeans have gone back and forth for a while.

Developing for mac os java