Lem me contribute to the "religious" discussion a bit. Would it be a good idea if we apply for an Open Source License from IntellijIdea? Here's the link:
I don't have any strings attached to JetBrains, but I used to use Idea a lot and liked it very much, so I decided to share that with you.
----- Original Message ----
From: Brian Burch <brian@PingToo.com>
To: sipComm developers <email@example.com>
Sent: Monday, September 8, 2008 4:19:24 PM
Subject: Re: [sip-comm-dev] nbproject/ide-targets.xml
Emil Ivov wrote:
I am currently trying out eclipse actually and I am surprised to find
out that they've made quite some progress since the last time I used it.
Although I worked with eclipse for a long time, I never liked two
fundamental design issues:
1. it is not a "pure java" application.
2. the ant build.xml is not used by the ide to "understand" the application.
Netbeans 4 avoided these limitations more than 4 years ago, but since
then I have found that my more complex requirements are handled in a
less satisfactory way, even though netbeans version 6 has been around
nearly a year.
1. it is very difficult to integrate a complex project into netbeans
because the ide insists on having project classpath information defined
in its own file, rather than using build.xml. Of course, eclipse is just
as bad and that means WE have to synchronise THREE different classpath
lists (see footnote).
2. debugging multi-thread applications is clumsy with netbeans. By
default, a breakpoint will stop all threads at once and stepping will
leap inexplicably between threads. Even when breakpoints are explicitly
changed to stop a single thread, switching threads is not intuitively
simple and it is easy to ruin a carefully established session. In my
memory, eclipse seemed to be much easier to use in this situation.
Many of the other differences have disappeared... e.g. netbeans now
compiles source files on-the-fly when they are opened or changed, but
eclipse always did it. Eclipse needs a separate directory tree to
compile into, while netbeans pretends to use the project directory (I
suspect it compiles to temporary files).
The main point is that an ide is "personal infrastructure". Very few of
us can cope with two ide's and we invest a lot of time and effort
becoming competent with just one. When you stand back a little way, it
is very similar to the windows-linux issue. It is just a pity that we
don't have everyone working together on a single (superior to both)
platform. Dream on...
footnote: while I have your attention, Emil... you never let me have
your thoughts on whether it was feasible to externalise our classpath
data into a single list that could be propagated (either manually or via
an ant target) into the various places and formats required by our
development tools. Any thoughts?
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com