On Oct 30, 2005, at 6:33 AM, nikolaus heger wrote:
As for best IDE:
Very easy: Try Eclipse and IDEA and use the one you like better.
Agreed.
I find that since I am already an expert in Eclipse, there is
nothing that IDEA would add that would be worth the time and money.
But I keep evaluating every new release of IDEA just in case.
I do much the same with Eclipse, for much the same reasons.
Another reason I am not switching is that I am also using SVN (per
plugin), Python (plugin) and Ruby (plugin). While the Py and Ruby
editors are nowhere near the Java tools, they are pretty
competitive with other Py and Ruby editors out there.
I just started using epic - pretty slick. I am not sure why it is
having trouble finding some of my perl modules, but in all, I am very
impressed.
The SVN support on the IDEA side is improving rapidly - I am hopeful
that I will be able to use it for my next java project.
That it's open source also gives me this warm, fuzzy feeling of
security. Eclipse will always be around.
A nice thing indeed. I have owned far too many abandoned IDES with
Just One Fatal Flaw.
Scott Ellsworth wrote:
One big IDEA win - the project files are plain old XML, so I can
generate them as needed programatically. (I maintain over 150
dependent projects - this is not a trivial thing.)
Hmm.. Eclipse .project and .classpath files are also XML. I think
they always were. I have not tried generating them programatically
though.
They are - it is easy enough to build those, but it is not easy to
build a workspace that includes them, so a user has to hand-build
their workspace the first time. This is is a great pain when there
are a lot of projects, and they change a bunch.
If the list of projects in a workspace were also XML, then I could do
everything I need.
Scott
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
