[Brian Bezanson]

What operating system and version are you running?
Windows 2000 Professional
What Eclipse version and build id are you using? (Help > About Eclipse Platform)
Eclipse Platform
Version: 2.1.3
Build id: 200403101828
– Was Eclipse freshly installed for MyEclipse?
Yes, though some other extensions were added first. To see about clearing the problem described below, I installed a clean copy of eclipse and myeclipse in new directories and encountered the same problem.
– If not, was it upgraded to its current version using the update manager?
No
– Are any other external plugins installed?
Yes
– How many plugins in the <eclipse>/plugins directory are like org.eclipse.pde.*

What MyEclipse version are you using? (Help > About Eclipse Platform > Features)
2.7.1
What JDK version are you using to run Eclipse? (java -version)
1.4.2_04
What JDK version are you using to launch your application server?
Same
What steps did you take that resulted in the issue?
Run Eclipse Updater and it wants to repair core 2.1.3 files.
What application server are you using?
JBoss 3.2.4RC1

Here is one of my issues:

1) Clean install of Eclipse 2.1.3
– Check for Updates, none to install
2) Install MYEclipse 2.7.1
– Check for Updates, wants to repair:
– Eclipse Java Development Tools 2.1.3
– Eclipse Platform 2.1.3
– Eclipse Platform (Windows) 2.1.3
– Eclipse Project SDK (Windows) 2.1.3

Why does this happen?
Any ideas if this issue is a result from some other area?

[Riyad Kalla]

This is actually a harmless side effect with limitations of the Update Manager in Eclipse 2.x. IIRC the ‘update’ is actually only a few 100k and even if you apply it, it still appears and nothing changes.

We appologize for the confusion, this should not occur in the Eclipse 3.0 releases (but lets wait for everything to go stable first 😉

[Author]

Posts