- This topic has 17 replies, 3 voices, and was last updated 17 years, 4 months ago by
.
-
Posts
-
Again and again and again…
I installed MyEclipseIde new and found that with the 2. update, it did not find some core objects. I was told in this forum after some posts, I should re-install the system. What i did. And it worked. First update ok. Second did not work. So I re-installed again. With the same up and down.
So, here I am again: It was now the third update (I believe). This is the error message:
Current configuration contains errors that are not corrected by the requested operation and more errors would be introduced. See details for more information. ----- Current configuration problems ----- Resulting configuration does not contain the platform. ----- Configuration problems after the operation ----- MyEclipse Enterprise Workbench (5.5.1) requires plug-in "org.eclipse.core.runtime.compatibility". MyEclipse Application Server Tooling (5.5.0) requires plug-in "org.eclipse.core.runtime.compatibility". MyEclipse Help Documentation (5.5.0) requires plug-in "org.eclipse.core.runtime.compatibility". MyEclipse Base Platform Support (5.5.0) requires plug-in "org.eclipse.core.runtime.compatibility". Eclipse Modeling Framework (EMF) Runtime + End-User Tools (2.2.2.v200702131851) requires plug-in "org.eclipse.core.resources (3.1.0)", or compatible. Graphical Editing Framework (3.2.2.v20070208) requires plug-in "org.eclipse.platform (3.2.0)", or compatible. Java EMF Model (1.2.3.v20070130_R----6zXJK-L2U8VZ) requires feature "org.eclipse.jdt (3.1.0)", or compatible. MyEclipse Tapestry / Spindle Support (5.5.0) requires plug-in "org.eclipse.core.runtime.compatibility". MyEclipse Struts Support (5.5.0) requires plug-in "org.eclipse.core.runtime.compatibility". MyEclipse Core Tooling (5.5.1) requires plug-in "org.eclipse.core.runtime.compatibility". MyEclipse Database Support (5.5.0) requires plug-in "org.eclipse.core.runtime.compatibility". MyEclipse Hibernate Support (5.5.0) requires plug-in "org.eclipse.core.runtime.compatibility". MyEclipse JSF Support (5.5.0) requires plug-in "org.eclipse.core.runtime.compatibility". MyEclipse JSP Design Support (5.5.0) requires plug-in "org.eclipse.core.runtime.compatibility". MyEclipse UML Support (5.5.0) requires plug-in "org.eclipse.core.runtime.compatibility". MyEclipse Web Development Tooling (5.5.1) requires plug-in "org.eclipse.core.runtime.compatibility". MyEclipse Spring Framework Support (5.5.0) requires plug-in "org.eclipse.core.runtime.compatibility". MyEclipse Web Services Support (5.5.0) requires plug-in "org.eclipse.core.runtime.compatibility". JavaServer Faces Tooling (1.0.0.zmyeclipse55020070514) requires plug-in "org.eclipse.ui". JST Common Core (1.5.3.zmyeclipse55020070514) requires feature "org.eclipse.platform (3.2.0)", or equivalent. JST Enterprise Core (1.5.4.zmyeclipse55020070514) requires feature "org.eclipse.platform (3.2.0)", or equivalent. JST Enterprise UI (1.5.4.zmyeclipse55020070514) requires feature "org.eclipse.platform (3.2.0)", or equivalent. JST Server Core (1.5.4.zmyeclipse55020070514) requires feature "org.eclipse.platform (3.2.0)", or equivalent. JST Web Core (1.5.4.zmyeclipse55020070514) requires feature "org.eclipse.platform (3.2.0)", or equivalent. WST Server Core (1.5.4.zmyeclipse55020070514) requires feature "org.eclipse.rcp (3.2.0)", or equivalent. WST Web Core (1.5.3.zmyeclipse55020070514) requires feature "org.eclipse.platform (3.2.0)", or equivalent. WST Web Services Core (1.5.4.zmyeclipse55020070514) requires feature "org.eclipse.platform (3.2.0)", or equivalent. WST XML Core (1.5.4.zmyeclipse55020070514) requires feature "org.eclipse.rcp (3.2.0)", or equivalent. Dali Java Persistence API (JPA) Tools (0.5.0.zmyeclipse55020070514) requires feature "org.eclipse.jdt (3.1.0)", or later version. Matisse4MyEclipse Swing UI Designer (5.5.0) requires plug-in "org.eclipse.ui".What can I do?? Don’t tell me again to re-install MyEclipseIde. I did not do more than just installing MyEclipse and then allowed the automatic updates. And this event again was an automated update.
Klaus
Klaus,
Can you recap for me what your installation looked like (for example “I installed version X, the updated to version Y then Z, now this”).It’s important because between certain releases there *is* no direct upgrade path and a new installation is required. For example, you cannot upgrade from MyEclipse 4.x to 5.x.
And in some cases you cannot upgrade between MyEclipse 5.1 to 5.5.
The unfortunately reality for us is that API breaks *are* introduced into the platform when they are not suppose to, so even though certain releases like 3.2.0 and 3.2.2 are suppose to be compatible, they aren’t. So from time to time we may require a clean install with a new release even though it “doesn’t seem necessary”.
The error messages you are getting about broken dependencies and such are indicative of a corrupted install, there’s no way around that, but I’d like to understand how you keep getting to these corrupt installs… I’m wondering if you are performing an incompatible set of actions each time and the product isn’t properly protecting you from doing them.
Also if you have ever installed a new version of MyEclipse ontop of an existing one, that would immediately explain why the install is corrupt. You can never run the installer and simply uncompress it ontop of an existing install. Again though, there is no way for new users to know this and unfortunately the installers don’t stop you from doing this (which I have filed as a bug, because they should).
So I’m trying to see where we can improve our support to keep users from bad installs occuring.
Riyad,
thank you very much for your kind, friendly and long reply.
As I said: This behaviour occurred to me with several installations. I am a bit confused that this is something which I encountered only.
Now, I never install a new MyEclipse in the same directory. I just grab the installer for Windows and install it without any special adjustments. Normally, I leave the old installation as it is and install in a fresh directory. I keep the old istallation, until I am really sure that the new one works to my satisfaction. The old installation remains intact (except of the not-updatable-problem). Usually, the new installation works and when the first update comes, I have no probs to install it. As I was told in my previous posts, that I should “-clean” start, I have build this parameter in my shortcut.
At present, I run version 5.5.1 GA
The only plug-in I need to have is the Salesforce plugin. But that does not remove core files, it just adds some jars.When my Installation finds a new update at startup, it pops up the box, and I do everything to get it installed. No special adjustments or handlings.
What else do you need to know?
ThanksKlaus
I just grab the installer for Windows and install it without any special adjustments. Normally, I leave the old installation as it is and install in a fresh directory. I keep the old istallation, until I am really sure that the new one works to my satisfaction.
That is exactly the right thing to do. I’m assuming you mean you are using the All-in-One installer each time which installs JRE/Eclipse/MyEclipse all at once, right?
At present, I run version 5.5.1 GA
The only plug-in I need to have is the Salesforce plugin. But that does not remove core files, it just adds some jars.When my Installation finds a new update at startup, it pops up the box, and I do everything to get it installed. No special adjustments or handlings.
That all sounds totally normal… given what you have outlined I have no idea things would go south for you.
Looking back at your first post, I see a core eclipse compatability plugin missing that a lot of Myeclipse requires… that made me think that you may be installing Eclipse yourself and then using the MyEclipse Plug-in installer (as opposed to the all in one installer)… is that possible? If so, that could explain what is going on…
I would also point out that it’s possible, given the size of MyEclipse, for it to partially install and some portions of it to work while others won’t work due to incomplete plugin requirements. So it *could* be possible that your install out of the gates was in bad shape, but you didn’t notice cause you weren’t using the functionality that was broken…
Let me know if any of that sounds possible…
Riyad,
it is wise that you take all possibilities into account. But honestly – I allways take the idiots (:-) way and the plain installer. As my only aim is, to have a working environment as save as possible, I do not play around. And this all happened at least 3 times.
And – as I am sometimes at your end of the helpdesk, and I see how difficult it is to answer questions like mine – I will again install the entire invironment and will observe that nothing special happens.
But I will come back to you, if the problem arises after that all again.
But thank you for your kind cooperative up to now.
Klaus
Klaus,
I’m sorry we weren’t able to pin-point any issue out of the gate. I appreciate your patience and yes please keep me posted… if the install sours again we can try and nit-pick it apart and see if we can figure out what is going on (looking at things like installed plugins, any plugin-dependency warnings, new workspace behaviors, etc.)A) I started the newly installed MyEclipse and get NullPointerExceptions for:
– Initializing Java Tooling
– Automatic Update SearchB) Start the environment again and get the NullPointer Exception for Automatic Update Search only
In both occasions, I got update offers
C) Starting the third time, I go no exceptions
D) Searching for updates manually did not give a result
That is strange somehow.
Klaus
Klaus,
Can you got to the MyEclipse menu, click Installation Summary and Installation Details and paste it here for me?Yes, before I do that (next post):
When I started the program to get this Installation Summary, I was offered the update of
– MyEclipse EnterpriseWorkbench 5.9.100
– Mantisse4MyEclipse Swing UI Designer 5.9.100I accepted and it aborted with:
Current configuration contains errors that are not corrected by the requested operation and more errors would be introduced. See details for more information. ----- Current configuration problems ----- Resulting configuration does not contain the platform. ----- Configuration problems after the operation ----- MyEclipse Enterprise Workbench (5.9.100) requires plug-in "org.eclipse.core.runtime.compatibility". MyEclipse Application Server Tooling (5.9.100) requires plug-in "org.eclipse.core.runtime.compatibility". MyEclipse Help Documentation (5.9.100) requires plug-in "org.eclipse.core.runtime.compatibility". MyEclipse Base Platform Support (5.9.100) requires plug-in "org.eclipse.core.runtime.compatibility". Eclipse Modeling Framework (EMF) Runtime + End-User Tools (2.3.0.v200706262000) requires feature "org.eclipse.platform (3.3.0.v20061208-Fj22sCYGm0XDWm3)", or compatible. Eclipse Modeling Framework (EMF) - org.eclipse.emf.common (2.3.0.v200706262000) requires plug-in "org.eclipse.core.runtime". Eclipse Modeling Framework (EMF) - org.eclipse.emf.common.ui (2.3.0.v200706262000) requires plug-in "org.eclipse.core.runtime". Eclipse Modeling Framework (EMF) - org.eclipse.emf.ecore (2.3.0.v200706262000) requires plug-in "org.eclipse.core.runtime". Eclipse Modeling Framework (EMF) - org.eclipse.emf.edit (2.3.0.v200706262000) requires plug-in "org.eclipse.core.runtime". Eclipse Modeling Framework (EMF) - org.eclipse.emf.edit.ui (2.3.0.v200706262000) requires plug-in "org.eclipse.core.runtime". Eclipse Modeling Framework (EMF) - org.eclipse.emf.ecore.edit (2.3.0.v200706262000) requires plug-in "org.eclipse.core.runtime". Eclipse Modeling Framework (EMF) - org.eclipse.emf.ecore.editor (2.3.0.v200706262000) requires plug-in "org.eclipse.core.runtime". Eclipse Modeling Framework (EMF) - org.eclipse.emf.codegen (2.3.0.v200706262000) requires plug-in "org.eclipse.core.runtime". Eclipse Modeling Framework (EMF) - org.eclipse.emf.codegen.ui (2.3.0.v200706262000) requires plug-in "org.eclipse.core.runtime". Eclipse Modeling Framework (EMF) - org.eclipse.emf.codegen.ecore (2.3.0.v200706262000) requires plug-in "org.eclipse.core.runtime". Eclipse Modeling Framework (EMF) - org.eclipse.emf.codegen.ecore.ui (2.3.0.v200706262000) requires plug-in "org.eclipse.core.runtime". Eclipse Modeling Framework (EMF) - org.eclipse.emf.converter (2.3.0.v200706262000) requires plug-in "org.eclipse.core.runtime". Eclipse Modeling Framework (EMF) - org.eclipse.emf.mapping (2.3.0.v200706262000) requires plug-in "org.eclipse.core.runtime". Eclipse Modeling Framework (EMF) - org.eclipse.emf.mapping.ecore (2.3.0.v200706262000) requires plug-in "org.eclipse.core.runtime". Eclipse Modeling Framework (EMF) - org.eclipse.emf.mapping.ui (2.3.0.v200706262000) requires plug-in "org.eclipse.core.runtime". Eclipse Modeling Framework (EMF) - org.eclipse.emf.mapping.ecore.editor (2.3.0.v200706262000) requires plug-in "org.eclipse.core.runtime". EMF Service Data Objects (SDO) - org.eclipse.emf.ecore.sdo (2.3.0.v200706262000) requires plug-in "org.eclipse.core.runtime". Graphical Editing Framework (3.3.0.v20070620) requires plug-in "org.eclipse.platform (3.2.0)", or compatible. XML Schema Infoset Model (XSD) - org.eclipse.xsd (2.3.0.v200706262000) requires plug-in "org.eclipse.core.runtime". XML Schema Infoset Model (XSD) - org.eclipse.xsd.edit (2.3.0.v200706262000) requires plug-in "org.eclipse.core.runtime". MyEclipse Tapestry / Spindle Support (5.9.100) requires plug-in "org.eclipse.core.runtime.compatibility". MyEclipse Struts Support (5.9.100) requires plug-in "org.eclipse.core.runtime.compatibility". MyEclipse Core Tooling (5.9.100) requires plug-in "org.eclipse.core.runtime.compatibility". MyEclipse Database Support (5.9.100) requires plug-in "org.eclipse.core.runtime.compatibility". MyEclipse Hibernate Support (5.9.100) requires plug-in "org.eclipse.core.runtime.compatibility". MyEclipse JSF Support (5.9.100) requires plug-in "org.eclipse.core.runtime.compatibility". MyEclipse JSP Design Support (5.9.100) requires plug-in "org.eclipse.core.runtime.compatibility". MyEclipse UML Support (5.9.100) requires plug-in "org.eclipse.core.runtime.compatibility". MyEclipse Web Development Tooling (5.9.100) requires plug-in "org.eclipse.core.runtime.compatibility". MyEclipse Spring Framework Support (5.9.100) requires plug-in "org.eclipse.core.runtime.compatibility". MyEclipse Web Services Support (5.9.100) requires plug-in "org.eclipse.core.runtime.compatibility". Dali Java Persistence API (JPA) Tools (0.5.0.zmyeclipse5910020070629) requires plug-in "org.eclipse.core.runtime". JST Common Core (2.0.0.zmyeclipse5910020070629) requires plug-in "org.eclipse.core.resources (3.2.0)", or compatible. JST Server UI (2.0.0.zmyeclipse5910020070629) requires plug-in "org.eclipse.core.runtime (3.2.0)", or compatible. JST Server Core (2.0.0.zmyeclipse5910020070629) requires plug-in "org.eclipse.core.runtime (3.2.0)", or compatible. JST Server Adapters (2.0.0.zmyeclipse5910020070629) requires plug-in "org.eclipse.core.runtime (3.2.0)", or compatible. JST Web UI (2.0.0.zmyeclipse5910020070629) requires plug-in "org.eclipse.jdt.core (3.2.0)", or compatible. JST Web Core (2.0.0.zmyeclipse5910020070629) requires plug-in "org.eclipse.core.runtime (3.2.0)", or compatible. JST Enterprise UI (2.0.0.zmyeclipse5910020070629) requires plug-in "org.eclipse.jdt.core (3.2.0)", or compatible. JST Enterprise Core (2.0.0.zmyeclipse5910020070629) requires plug-in "org.eclipse.jdt.core (3.2.0)", or compatible. WTP Web Page Editor (1.0.0.zmyeclipse5910020070629) requires plug-in "org.eclipse.core.runtime (3.2.0)", or compatible. WST Common UI (2.0.0.zmyeclipse5910020070629) requires plug-in "org.eclipse.core.runtime (3.2.0)", or compatible. WST Common Core (2.0.0.zmyeclipse5910020070629) requires plug-in "org.eclipse.core.runtime (3.2.0)", or compatible. WST Server UI (2.0.0.zmyeclipse5910020070629) requires plug-in "org.eclipse.core.runtime (3.2.0)", or compatible. WST Server Core (2.0.0.zmyeclipse5910020070629) requires plug-in "org.eclipse.core.runtime (3.2.0)", or compatible. WST Server Adapters (2.0.0.zmyeclipse5910020070629) requires plug-in "org.eclipse.core.runtime (3.2.0)", or compatible. Eclipse XML Editors and Tools (2.0.0.zmyeclipse5910020070629) requires plug-in "org.eclipse.core.resources (3.2.0)", or compatible. WST XML Core (2.0.0.zmyeclipse5910020070629) requires plug-in "org.eclipse.osgi". WST Web Services UI (2.0.0.zmyeclipse5910020070629) requires plug-in "org.eclipse.core.runtime (3.2.0)", or compatible. WST Web Services Core (2.0.0.zmyeclipse5910020070629) requires plug-in "org.eclipse.core.runtime (3.2.0)", or compatible. WST Web UI (2.0.0.zmyeclipse5910020070629) requires plug-in "org.eclipse.ui.ide (3.2.0)", or compatible. WST Web Core (2.0.0.zmyeclipse5910020070629) requires plug-in "org.eclipse.core.runtime (3.2.0)", or compatible. Matisse4MyEclipse Swing UI Designer (5.9.100) requires plug-in "org.eclipse.ui".This is what I had before…
Ok, and here as promised:
*** Date: Thursday, July 26, 2007 9:53:52 PM CEST ** System properties: OS=WindowsXP OS version=5.1 Java version=1.5.0_11 *** MyEclipse details: MyEclipse Enterprise Workbench Version: 6.0.0 M1 Build id: 20070629-6.0.0-M1 *** Eclipse details: MyEclipse Enterprise Workbench Version: 6.0.0 M1 Build id: 20070629-6.0.0-M1 Eclipse Platform Version: 3.3.0.v20070612-_19UEkLEzwsdF9jSqQ-G Build id: I20070625-1500 Eclipse RCP Version: 3.3.0.v20070607-8y8eE8NEbsN3X_fjWS8HPNG Build id: I20070625-1500 Eclipse Java Development Tools Version: 3.3.0.v20070606-0010-7o7jCHEFpPoqQYvnXqejeR Build id: I20070625-1500 Eclipse Plug-in Development Environment Version: 3.3.0.v20070607-7N7M-DUUEF6Ez0H46IcCC Build id: I20070625-1500 Eclipse Project SDK Version: 3.3.0.v20070607-7M7J-BIolz-OcxWxvWAPSfLPqevO Build id: I20070625-1500 Eclipse Graphical Editing Framework Version: 3.3.0.v20070620 Build id: 20070620-1021 Eclipse startup command=-os win32 -ws win32 -arch x86 -showsplash -launcher C:\Programme\MyEclipse-6.0M1\eclipse\eclipse.exe -name Eclipse --launcher.library C:\Programme\MyEclipse-6.0M1\eclipse\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.0.v20070523\eclipse_1017a.dll -startup C:\Programme\MyEclipse-6.0M1\eclipse\plugins\org.eclipse.equinox.launcher_1.0.0.v20070606.jar -exitdata 173c_f0 -vm C:\Programme\MyEclipse-6.0M1\jre\bin\javaw.exeI hope, you can find out what is wrong here.
Cheers
KlausOk, and here as promised:
*** Date: Thursday, July 26, 2007 9:53:52 PM CEST ** System properties: OS=WindowsXP OS version=5.1 Java version=1.5.0_11 *** MyEclipse details: MyEclipse Enterprise Workbench Version: 6.0.0 M1 Build id: 20070629-6.0.0-M1 *** Eclipse details: MyEclipse Enterprise Workbench Version: 6.0.0 M1 Build id: 20070629-6.0.0-M1 Eclipse Platform Version: 3.3.0.v20070612-_19UEkLEzwsdF9jSqQ-G Build id: I20070625-1500 Eclipse RCP Version: 3.3.0.v20070607-8y8eE8NEbsN3X_fjWS8HPNG Build id: I20070625-1500 Eclipse Java Development Tools Version: 3.3.0.v20070606-0010-7o7jCHEFpPoqQYvnXqejeR Build id: I20070625-1500 Eclipse Plug-in Development Environment Version: 3.3.0.v20070607-7N7M-DUUEF6Ez0H46IcCC Build id: I20070625-1500 Eclipse Project SDK Version: 3.3.0.v20070607-7M7J-BIolz-OcxWxvWAPSfLPqevO Build id: I20070625-1500 Eclipse Graphical Editing Framework Version: 3.3.0.v20070620 Build id: 20070620-1021 Eclipse startup command=-os win32 -ws win32 -arch x86 -showsplash -launcher C:\Programme\MyEclipse-6.0M1\eclipse\eclipse.exe -name Eclipse --launcher.library C:\Programme\MyEclipse-6.0M1\eclipse\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.0.v20070523\eclipse_1017a.dll -startup C:\Programme\MyEclipse-6.0M1\eclipse\plugins\org.eclipse.equinox.launcher_1.0.0.v20070606.jar -exitdata 173c_f0 -vm C:\Programme\MyEclipse-6.0M1\jre\bin\javaw.exeI hope, you can find out what is wrong here.
Cheers
KlausKlaus,
It looks like you used the 6.0M1 (Milestone 1 == Beta 1) installer and not the 5.5 All in One installer which is our latest stable release. So getting prompted for the M4M install is expected (since it’s an additional feature) but I have no idea why you were prompted to install 5.9.100 which is the version you are already running… so that seems very fishy to me.I wonder if something is wrong with your workspace. Can you try loading up MyEclipse and going to File > Switch Workspace and creating a new workspace somewhere and see if the behavior improves? From there we can import your old settings and projects into the new workspace if necesary.
Yes Riyad,
I created a new Workspace by renaming the existing workspace directories and then letting MyEclipse create a new one.
Fine. Then I tried the manual search for updates, which would not find anything for me. Then, I configured Exclipse to automatically search for updates anytime I run the program. It immediately ran the search and brought: nothing.
Then, I restarted the program and got the old crab again.– I was offered Mantisse4MyEclipse 5.9.100 and MyEclipse Enterprise Workbench 5.9.100
– underneath that it stated that the automatic search caused a nullPointerExceptionAll of this is the same as in my old workspace.
Do you think, I can now go back to my old workspace?
Klaus
PS: I was not aware that Milestone1 in the name is equal to the common Alpha1. So, do you think, I should go to 5.5? But I have my problems in the same form and shape since 5.0 at least or even before taht.
Do you think, I can now go back to my old workspace?
Yes it seems a new workspace didn’t help… this is so frustrating (certainly more so for you, but I’m really frustrated that I’ve been unable to get you a working install…)
PS: I was not aware that Milestone1 in the name is equal to the common Alpha1. So, do you think, I should go to 5.5? But I have my problems in the same form and shape since 5.0 at least or even before taht.
Milestones are more like Betas, and Milestone 1 has actually prooved to be quite stable, so if you wanted to stay with it, it should be alright. We will be making a 6.0 GA release here in 2 weeks or so, so not too much longer until our next release.
Hi Riyad,
does that mean translated that all the specialists in your company have no clue what I could do? I have to live with it? Reinstall the entire program any time there is a new update available? With all the plugins I might have at that time?
I have a standard computer, a standard WinXP with all updates and servicepacks. I cannot see a problem at my end. There must be a bug in the installer.
Sorry, I did not have the situation before that the support of a solid company leaves its customer like that.
Klaus
