Eclipse 3.0 M9

Anyone else got it yet?
There seems to be a bug in refactoring of class names since it sometimes just changes the class name and doesn’t update the references even though ‘Update references’ is ticked.
Am I the only one having this problem?

edit: otherwise seems like a nice update, finally eclipse has the code folding feature too (I especially like that the imports of all classes are automatically folded)
There’s an early access 1.5 support too (haven’t tested it though).

Ewwww… that’s a pretty major refactoring problem, seeing as I use that operation quite frequently :confused:

Cas :slight_smile:

Mmm. Another one (appeared after a session of refactoring)…

Internal compiler error
java.lang.NullPointerException

  at org.eclipse.jdt.internal.compiler.lookup.SourceTypeBinding.resolveTypesFor(SourceTypeBinding.java:803)

  at org.eclipse.jdt.internal.compiler.lookup.SourceTypeBinding.methods(SourceTypeBinding.java:696)


And that brings other problems (eg. can’t save anything or use copy&paste etc)… Never had any problems with earlier milestones, guess I’ll go back to M8.
Or maybe i’ll test if IDEA’s as good as people say.

Get those errors sent to eclipse.org or they’ll take longer over fixing them!

Cas :slight_smile:

Please get into the habit of filing bug reports. The number of bugs that I find reported in forums that are not found in bug tracking software is staggering. Developers don’t always have time to scour the forums looking for bug reports.

I have written up a quick blurb on this that will hopefully drive the point home:

http://www.realityinteractive.com/rgrzywinski/archives/000046.html

I must say that bug reporting for eclipse DOES work - I have submitted 3 bugs at Saturday evening and 2 of them were fixed before Sunday evening, other one at Monday. It looks like some people love this software in addition to working on it.

It would help immensely if Eclipse sent its logfile to eclipse.org automatically when it encounters a problem.

Cas :slight_smile:

BTW M9 is RC0 apaprently so features are frozen

and 1.5 support is not planned for 3.0 release (it’ll be a separate plug-in)

[quote]I must say that bug reporting for eclipse DOES work - I have submitted 3 bugs at Saturday evening and 2 of them were fixed before Sunday evening, other one at Monday. It looks like some people love this software in addition to working on it.
[/quote]
Really? My experience is quite the opposite. I have one bug outstanding that was assigned to a developer the morning I reported it, but hasn’t been touched since - it’s been five weeks now, with no visible progress.

Then again, I’ve got four bugs open on Maven from October 2003, with no updates past November. I think they’ve all been deferred to post-1.0, but I really can’t be sure. :-/

@vrm sorry I’m being dense here RCO?

Dan.

Release Candidate Zero

[quote]Please get into the habit of filing bug reports.
[/quote]
Yeah you’re right. But i’m just usually so lazy and/or think that someone else has already reported the bug, that I won’t bother. But I’ll try to manage to do it this time, after all eclipse is probably the finest free tool I’ve ever ran into.

Useful fact from Alien Flux experience: no-one reports bugs unless it is done automatically for them without their consent or knowledge.

Cas :slight_smile:

I notice that theres a release marked as 3.0 RC1 as well as M9, has anyone tried it yet? I’ve got to reinstall Eclipse and I’m wondering what version to stick on. M9 sounds a tad too problematic, so I might try the latest or go back to M8…

[quote]Useful fact from Alien Flux experience: no-one reports bugs unless it is done automatically for them without their consent or knowledge.

Cas :slight_smile:
[/quote]
Corollary: even fewer people report bugs when you’re anally retentive and force them to:

  • create a username and password
  • give you their email address
  • wait for a confirmation email
  • reply to that email
  • login to the system.

If someone finds a bug they are PISSED OFF and NOT HAPPY with your software. Forcing them to jump through hoops to help YOU is not a good idea.

This is why all those public bugzillas are SUCH a bad idea. Login-secured bug systems are for teams, not the public.

FYI I have given up on several bugs in OO because they made it so much bloody hassle to report them. Some I reported then was asked for more details but it was such a hassle to dig out the username and password I originally used to try and reply that I just gave up.

Corollary 2: When you tell an open-source programmer that this is the way real people behave, like it or not, most of them bite your head off telling you that “well I’m not paid, you know” or “if you want my help you have to jump through these hoops” or “it’s really easy, come on - anyone can do it”. Very few respond with “Oh, bummer. Yeah, I see that though it’s illogical that’s how life is and I have to work with it rather than just ignore it and try and live in the perfect world inside my head” (although occasionally a few do).

FYI before anyone flames me I have contributed a lot of bugs to some opensource software. E.g. mozilla, where it automatically gathered the version of your app so you didn’t hve to work it out :). Also I’ve offered stuff back - like recently doing a big redesign of the bugzilla bug-query page (the worst piece of HTML in the history of mankind EVER!) although time constraints mean all I’ve achieved is to send them a screenshot of how it could be done much better (and hope someday to have enough time to finish the job off for them).