[firebadger]

I am using Eclipse 3.1, MyEclipse 4M2 on Windows with Java 1.4.2_05. I think the only additional plugin I am currently using is the Visual Editor.

Quite often I get an error dialog flashing up (most common when I compile a Java file working in the Java editor but also at other times) saying this…

An internal error occurred during: “Decoration Calculation”.

The corresponding entry in the log is as follows…

!ENTRY org.eclipse.core.runtime 4 2 2005-08-09 14:55:00.199
!MESSAGE An internal error occurred during: “Decoration Calculation”.
!STACK 0
java.lang.StackOverflowError

Its beginning to drive me nuts although I do find I can continue working it doesn’t exactly fill me with confidence.

I would be grateful if you could tell me if this is a known issue and what I can do about it.

Thanks!

[Riyad Kalla]

This has never been reported before, why are you assuming this is a MyEclipse issue and not an install or VE issue? Are there details you aren’t including here that maybe help us figure out what is going on?

I’d like your Eclipse BuildID (Help > About) as well as your MyEclipse Build ID (Window > Preferences > MyEclipse).

[firebadger]

I’m making no assumptions about the source of the problem.

My build details…
Version: 3.1.0
Build id: I20050627-1435

I’ve also got the JADEclipse plugin installed but that’s the only additional plugin I’ve added that I can think of apart from the VE.

Given that this appears not to be a widespread issue, I’m going to do is start again with a completely clean build and hopefully the problem will dissappear.

Regards,
Alan

[firebadger]

I made a fresh install of Eclipse 3.1 and MyEclipse but the problem has reoccured.

Eclipse:
Version: 3.1.0
Build id: I20050627-1435

MyEclipse:
Version: 3.9.210
Build id: 20050627-4.0-Milestone-2

java.vm.version=1.4.2_05-b04

The only think i did subsequent to the fresh install was import a couple of projects and install the VE (and the related versions of the GEF and EMF plugins) using the update manager. I have done a bit of searching around and have not come accross anybody having a similar problem.

I have also just tried disabling the VE and the GEF and EMF packages but the problem still persists.

[Riyad Kalla]

Alan,
Since you said “import a couple of projects” I am assuming you creataed a new workspace (which is good, I was going to ask you to do this).

MyEclipse already ships EMF and GEF, so if you are using updated builds that VE requires, I’m not surprised if this would give you errors. I’m sorry to ask, but would it be possible to do a new fresh install of *just* Eclipse and MyEclipse (and a new workspace) and see if the problem persists or goes away?

[firebadger]

Are you saying that the up to date releases of the GEF and EMF are likely to cause problems?

I’ll try what you suggest and let you know.

Just out of curiosity, are there plans to test the release of MyEclipse 4.0 against the VE?

Thanks,
Alan

[Scott Anderson]

Are you saying that the up to date releases of the GEF and EMF are likely to cause problems?

Actually, yes. Although the Eclipse team doesn’t like to admit it, API’s do change during the milestoning process. We’ll ship the final releases in 4.0GA. We’ve already done the code ports internally, but getting the new versions into 4.0M3 would’ve been too disruptive to the development team, so we shipped milestiones of draw2d and gef that were about 3 weeks older than the final versions that are available now.

Just out of curiosity, are there plans to test the release of MyEclipse 4.0 against the VE?

Actually, compatibility with VE is one of the primary drivers on shipping the final versions of the libs, so you should be fine in 4.0GA, privided that VE is updated to use the final versions of the libraries as well. Sorry for the delay on that, but it just couldn’t be helped if we were to meet our delivery commitments.

[firebadger]

Thanks for the info. I think I’ll just live with the problem until 4.0 GA. The only thing I find surprising is the fact that I seem to be the only one who has experieced these issues.

[firebadger]

I’ve been trying to get to the bottom of this and I have established that this is not a MyEclipse issue. I have a fresh install of Eclipse 3.1 that exhibits this problem. I can only assume that it is something to do with the configuration of the project I am using which was originally developed in 3.0.

So thanks for your help and sorry for troubling you.

[Scott Anderson]

Yep, that looks like an Eclipse 3.0 to 3.1 upgrade issue. If it’s localized to the proejct, I’d try a new workspace and then copying and importing the problem project into it. Sometimes it’s the workspace that goes bad, not the project itself.

[David Orriss Jr]

@support-scott wrote:

Actually, compatibility with VE is one of the primary drivers on shipping the final versions of the libs, so you should be fine in 4.0GA, privided that VE is updated to use the final versions of the libraries as well. Sorry for the delay on that, but it just couldn’t be helped if we were to meet our delivery commitments.

I’m looking forward to this in 4.0GA. I just found that M3 and VE don’t work together. There’s no errors, you just never see the VE-related editors or “example” classes.

[Author]

Posts