whic IDE do you use for java?

[chili5]

oh i like my IDE to include a compiler so I probably wouldn't use eclipse if it doesn't have the compiler for C++

[HAL 9000]

Well you would be out of luck most IDE don't have a true compiler of their own They package one with it from a seperate project like MinGW or CygWin and not having a independent compiler from the IDE is bad.

[G_Morgan]

oh i like my IDE to include a compiler so I probably wouldn't use eclipse if it doesn't have the compiler for C++

Well Eclipse sees a lot of use on Unix/Linux systems where the compiler tends to be part of the platform rather than a tacked on extra. Linux distros generally have properly configured shell paths so using a compiler is easy. Developing on Windows is a nightmare to set up properly.

Personally I favour Emacs + Bash (via Emacs term mode) + make + JUnit (textui test runner) for my Java development. If there was a "can't live without it" refactoring browser* then I might consider a full IDE. Netbeans is the best IDE I've seen for Java though.

*like the kind you get with Smalltalk environments.

[gaffaro]

ohh there is fantastic İDE s
i had never seen&heard BlueJ and Gel..
eclipse enough for everything :S

[hellochar]

By far, Netbeans is my favorite IDE. The debugging tools and Profiler are indispensable, and it's constantly being developed.

[tomitzel]

Eclipse

[marwex89]

GO NETBEANS! GO NETBEANS!

Ehrm.. I prefer NetBeans, not only for Java but also for C++ (and C) (and HTML)

[G_Morgan]

GO NETBEANS! GO NETBEANS!

Ehrm.. I prefer NetBeans, not only for Java but also for C++ (and C) (and HTML)

The C/C++ module is what really made Netbeans for me. It's interaction with the build system* is far superior to other IDE's that make your build extraordinarily opaque outside of hit f5. Even my most basic project would have dozens of build options and the average IDE constrains this work flow heavily.

*essentially sane defaults for your build but also the ability to add custom build rules in a structured manner that both Netbeans and myself can understand. No auto-generated 10,000 line make file for helloworld. No restriction to a grand total of 4 build rules.

[marwex89]

The C/C++ module is what really made Netbeans for me. It's interaction with the build system* is far superior to other IDE's that make your build extraordinarily opaque outside of hit f5. Even my most basic project would have dozens of build options and the average IDE constrains this work flow heavily.

*essentially sane defaults for your build but also the ability to add custom build rules in a structured manner that both Netbeans and myself can understand. No auto-generated 10,000 line make file for helloworld. No restriction to a grand total of 4 build rules.

Exactly. While we're at this thing with makefiles... I have some problems using resource scripts with NetBeans, well, with the compiler actually. (Off topic, I know) You don't have a simple answer/link to help me there, have you?

[G_Morgan]

Exactly. While we're at this thing with makefiles... I have some problems using resource scripts with NetBeans, well, with the compiler actually. (Off topic, I know) You don't have a simple answer/link to help me there, have you?

It's been a while since I've used it in detail for C/C++ (still prefer a simple command line + editor). Here's the learning trail from Sun though

C/C++ Application Learning Trail - NetBeans Tutorials, Guides and Articles

Netbeans should handle ordinary programs just fine and equivalently to VS or Eclipse. It's when you need to fiddle with compiler options and strange library set ups.