![]() But, be warned, NetBeans feels good if and only if you are using Windows platform. While SWT is nice GUI, its load time takes considerably a long period of time compared to NetBeans Swing. Plugins in NetBeans is so easy to install, but yea, it is not as many as Eclipse's.įeeling clunky while using Eclipse also led me to move to NetBeans. I had so many problem with Eclipse plugins, ranging from different versions of Eclipse itself to the multiple plugins prerequisite for a plugin. If you are starting fresh, go with NetBeans.įrom my own experience, while Eclipse provides you with tons of plugins, that is not always guaranteed to meet your expectation. It doesn't have this project management nightmare. On the other hand, NetBeans works as expected. I get tired to recreate them with each fresh checkout. I work on half dozen fresh checkouts in a span of 6 months. You can create configurations in Eclipse, but you can't save them as part of your project file (i.e it won't go into your source control). Everyone in the team can use them without a big learning curve. And they let you save those things as part of your project file. Many IDES let you have different configurations to run your code (Release, Debug, Release with JDK 1.5 etc). I bet Eclipse project management was designed by guys who never used an IDE. ![]() If you had to jump through these many hoops, the IDE basically failed. Rather we came up with an Ant build file and launch it from inside Eclipse. We ended up not using its default project management stuff (i.e. We have 20 step instruction sheet for someone to go through each time they start a fresh checkout from source control. 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.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |