Eclipse 3.1 was released yesterday, and now appears to fully support Java 1.5/5.0/whatever. ;D So maybe with this and retroweaver I might just start using some of the new features…
The new CVS and Ant features look quite good as well. Now I just need to do a backup and figure out how to upgrade with the minimum of work. 
The new webstart exporter wizard for creating .jnlp manifests and signing .jars is a very useful feature. I’ve been looking for such an app and even been prepared to pay for it… ;D
Eat dust NetBeans 4.1! 
Warning: generics are so fucked in 3.1 they are unusable. I am now in an extremely untenable position 
We refactored the entire system we’re working on to use generics (they seemed to work at first) but now, 4 weeks of refactoring later, it turns out our code won’t compile.
It got so desperate I tried NetBeans 4.1. By God is it awful. And it crashed when we tried to compile anyway so that was a short lived horror.
We also tried IDEA, which crashed in the same way as NetBeans. I had high hopes for IDEA but nothing seems to even have a hope against the amazing capabilities of Eclipse.
If only generics weren’t broken 
Cas 
Princec, I’m having absolutely no problems. I use generics so frequently and almost everywhere.
I suggest you look for errors in your code.
Netbeans 4.1 release version should run very stable actually, on a common Java 1.5 system.
I can’t tell if you use Mustang etc.
With the Java 1.5 release version there shouldn’t be any problems with Netbeans. There are absolutely none with my system, which is a rare thing for applications on Winblow PCs.
I’m happy there’s Eclipse because it made Netbeans to jump from v3.X to the amazing v4.X versions.
KILER, you are a n00b extraordinaire.
Cas
I’m not the one having problems with my generics code and Eclipse 3.1.
I’m the n00b? Ha!
I just can’t believe you actually said [quote]I suggest you look for errors in your code.
[/quote]
to me, padawan.
Cas
I believe princec has been taken into the l33t speak dark side.
Kev
I’ve refactored hundreds of classes in my project with Eclipse 3.1 M3 (Obviously not the current release). None of them had problems.
You’re obviously doing something wrong or there’s a bug.
I’m more inclined to believe you’ve done something wrong than Eclipse is crap, or whatever you’re implying against Eclipse.
Whether or not it’s your code is irrelevant. I had originally said it as a joke(People must be disabling smilies).
Generics in Eclipse unusable? Oh please.
If you hate it that much then don’t use it. I’m sick of people blaming their lack of competence on an IDE.
I wouldn’t know whether or not this statement is true in your case but I do suggest that you stop putting down an IDE because you are having issues with it.
I’ve encountered very few bugs in Eclipse. I use just about every feature of Eclipse, so please stop making false statements about Eclipse.
Of course my platform is Windows, if you’re using Linux then you are partly forgiven. Although I still don’t like it when people put down an IDE because they have an issue with it.
to me, padawan.
Cas
[/quote]
Ha. I’ve encountered loads, and I only started seriously using it 6 months or so ago (maybe 9 months?).
Eclipse has plenty of bugs. fortunately, most are time-wasting, annoying, crappy stuff and don’t prevent compilation etc.
BUT eclipse uses a custom compiler setup that does barf on things that the sun javac will accept happily, and that has caused me problems in the past, where the error message from eclipse is WRONG and it refuses to compile code that I’m compiling in parallel with no problems :(.
So…you’ve been lucky so far, or just not using eclipse intensively enough ;D
EDIT: that’s equally spread across windows and linux. I’ve used Eclipse on OS X but it’s really screwed on OS X, and so painful to use I generally jump through hoops to avoid it :(. Not an uncommon problem with apps that weren’t originally developed on OS X, sadly
Blah, do you intentionally go finding bugs to screw over the hard work people have done? You seriously strike me as being a malevolent person recently. And what are the fruits of your labour? I haven’t seen any…
Go on, please do enlighten me about this bug in the eclipse compiler thats stopping you from developing…
I seriously dont like people who take other people’s work for granted and try and push their hard work into the dirt when they themselves dont have any fruits to show…
I have no idea what you are on about ??? Eclipse has serious bugs, Cas is being hurt by one, and someone starts claiming eclipse isn’t buggy and is perfect and it must be Cas’s fault. I point out that no, it’s not just Cas, eclipse is buggy, and mention a couple that have bitten me. I don’t see how that has anything to do with what you just said.
Ditto the following statement. If you want to slag me off, PM me rather than thread-jacking.
There’s plenty of them - isn’t their bugzilla open? Can’t you just search for yourself? You know, if you J-F-Googled-for-it you’d find eclipse bugs immediately (I did just now…). As a matter of principle, if people are too lazy to google, I don’t do it for them.
Gahhh look here you go: https://bugs.eclipse.org/bugs/show_bug.cgi?id=100869
and https://bugs.eclipse.org/bugs/show_bug.cgi?id=78027 which appears to have regressed.
Cas
I am using NB4.1 with mustang and it works great. They had a nasty little type bug in the last few versions of mustang but after that got addressed everything is great. I have not used any complex generics but I use this, Iterator<Map.Entry<String,ChannelList.Channel>>, quite a bit and it works just fine. Now I read that 4.2 is going to be even faster. NB is the bomb.
[quote=“GKW,post:16,topic:23934”]
Good to hear about Mustang!
The NB 4.2 (beta, quality build) I’m using right now and works OK (some well catched exceptions if you use Ctrl mouse click on class names) and indeed it’s fast. Also the improved code completion’s is lovely.
The NB devs work a lot and publish many beta versions (q-build are my favs), so you see what they do and what to except in the (very) near future.
It’s indeed the bomb.
Back to the thread…
Did I mention how lucky I am that Eclipse exists, so we finally got Netbeans 4.X in contrast to 3.x ?
I’ve only just installed it, but first impressions are good - and they’ve extended the syntax colouring substancially it seems, something that always seemed limited before. Auto-highlighting of all occurances of a variable/class name/etc. looks nice and could be very handy. 
Still jerks like hell under 1.5. But then, everything does. Grr.
I’ve managed to work around most of the generics issues using a rather verbose coding style. The trouble is, learning generics on the job as I am, I am now never sure whether something doesn’t work because I’m an idiot or whether it’s a quirk in the compiler.
Cas
I think I’ve been bitten by one of those as well. But in general Eclipse 3.1 is great, I can’t think of any issues with it off the top of my head (well there is this generics thing, but I always thought that was my fault :))… though the Subclipse plugin for Subversion has some issues with keeping certain views in a sane state.
In any case after working with Eclipse, Netbeans 4.1 is still such a huge step backwards that putting up with issues like this is still preferrable. I gave NetBeans a try again recently since I keep seeing all this raving about it and that new GUI layout thing. But NetBeans is still a huge productivity reducer,the GUI tool needs it’s own custom layout manager, and there is still no support for SpringLayout… and it’s slower… so I’m not all that impressed.
I’m not sure why Blah has issues with Eclipse on OS X. It seems to work fine for me, though perhaps a bit slower than on Windows.