- This topic has 12 replies, 5 voices, and was last updated 16 years, 6 months ago by
.
-
Posts
-
Nipun,
Did you install MyEclipse 6.0.1 over the old installation by any chance?
Absolutely not!
The errors that you are running into are mostly related to a corrupt install.Could you please reinstall MyEclipse to a brand new location, point it to a new workspace and try setting up Matisse4MyEclipse.
Now I deinstalled the old version, downloaded a new version (MyEclipse_6.0.1GA_E3.3.1_FullStackInstaller.exe) and installed it. Now the following error appeares:
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 (6.0.1.zmyeclipse601200710) requires feature “org.eclipse.platform (3.3.0)”, or equivalent.
MyEclipse Application Server Tooling (6.0.1.zmyeclipse601200710) requires plug-in “org.eclipse.core.runtime.compatibility”.
MyEclipse Help Documentation (6.0.1.zmyeclipse601200710) requires plug-in “org.eclipse.core.runtime.compatibility”.
MyEclipse Base Platform Support (6.0.1.zmyeclipse601200710) requires plug-in “org.eclipse.core.runtime.compatibility”.
Eclipse Modeling Framework (EMF) Runtime + End-User Tools (2.3.1.v200709252135) requires feature “org.eclipse.platform (3.3.0.v20061208-Fj22sCYGm0XDWm3)”, or compatible.
Eclipse Modeling Framework (EMF) – org.eclipse.emf.common (2.3.0.v200709252135) requires plug-in “org.eclipse.core.runtime”.
Eclipse Modeling Framework (EMF) – org.eclipse.emf.common.ui (2.3.1.v200709252135) requires plug-in “org.eclipse.core.runtime”.
Eclipse Modeling Framework (EMF) – org.eclipse.emf.ecore (2.3.1.v200709252135) requires plug-in “org.eclipse.core.runtime”.
Eclipse Modeling Framework (EMF) – org.eclipse.emf.edit (2.3.1.v200709252135) requires plug-in “org.eclipse.core.runtime”.
Eclipse Modeling Framework (EMF) – org.eclipse.emf.edit.ui (2.3.1.v200709252135) requires plug-in “org.eclipse.core.runtime”.
Eclipse Modeling Framework (EMF) – org.eclipse.emf.ecore.edit (2.3.0.v200709252135) requires plug-in “org.eclipse.core.runtime”.
Eclipse Modeling Framework (EMF) – org.eclipse.emf.ecore.editor (2.3.1.v200709252135) requires plug-in “org.eclipse.core.runtime”.
Eclipse Modeling Framework (EMF) – org.eclipse.emf.codegen (2.3.1.v200709252135) requires plug-in “org.eclipse.core.runtime”.
Eclipse Modeling Framework (EMF) – org.eclipse.emf.codegen.ui (2.3.0.v200709252135) requires plug-in “org.eclipse.core.runtime”.
Eclipse Modeling Framework (EMF) – org.eclipse.emf.codegen.ecore (2.3.1.v200709252135) requires plug-in “org.eclipse.core.runtime”.
Eclipse Modeling Framework (EMF) – org.eclipse.emf.codegen.ecore.ui (2.3.0.v200709252135) requires plug-in “org.eclipse.core.runtime”.
Eclipse Modeling Framework (EMF) – org.eclipse.emf.converter (2.3.1.v200709252135) requires plug-in “org.eclipse.core.runtime”.
Eclipse Modeling Framework (EMF) – org.eclipse.emf.mapping (2.3.0.v200709252135) requires plug-in “org.eclipse.core.runtime”.
Eclipse Modeling Framework (EMF) – org.eclipse.emf.mapping.ecore (2.3.0.v200709252135) requires plug-in “org.eclipse.core.runtime”.
Eclipse Modeling Framework (EMF) – org.eclipse.emf.mapping.ui (2.3.0.v200709252135) requires plug-in “org.eclipse.core.runtime”.
Eclipse Modeling Framework (EMF) – org.eclipse.emf.mapping.ecore.editor (2.3.0.v200709252135) requires plug-in “org.eclipse.core.runtime”.
EMF Service Data Objects (SDO) – org.eclipse.emf.ecore.sdo (2.3.0.v200709252135) requires plug-in “org.eclipse.core.runtime”.
Graphical Editing Framework (3.3.1.v20070814) requires plug-in “org.eclipse.core.runtime (3.2.0)”, or compatible.
XML Schema Infoset Model (XSD) – org.eclipse.xsd (2.3.1.v200709252135) requires plug-in “org.eclipse.core.runtime”.
XML Schema Infoset Model (XSD) – org.eclipse.xsd.edit (2.3.0.v200709252135) requires plug-in “org.eclipse.core.runtime”.
Data Tools Platform SQL Development Tools (1.5.1.zmyeclipse601200710) requires plug-in “org.eclipse.ui (3.2.0)”, or compatible.
MyEclipse Tapestry / Spindle Support (6.0.1.zmyeclipse601200710) requires plug-in “org.eclipse.core.runtime.compatibility”.
MyEclipse Struts Support (6.0.1.zmyeclipse601200710) requires plug-in “org.eclipse.core.runtime.compatibility”.
MyEclipse Core Tooling (6.0.1.zmyeclipse601200710) requires plug-in “org.eclipse.core.runtime.compatibility”.
MyEclipse Database Support (6.0.1.zmyeclipse601200710) requires plug-in “org.eclipse.core.runtime.compatibility”.
MyEclipse Hibernate Support (6.0.1.zmyeclipse601200710) requires plug-in “org.eclipse.core.runtime.compatibility”.
MyEclipse JSF Support (6.0.1.zmyeclipse601200710) requires plug-in “org.eclipse.core.runtime.compatibility”.
MyEclipse JSP Design Support (6.0.1.zmyeclipse601200710) requires plug-in “org.eclipse.core.runtime.compatibility”.
MyEclipse UML Support (6.0.1.zmyeclipse601200710) requires plug-in “org.eclipse.core.runtime.compatibility”.
MyEclipse Web Development Tooling (6.0.1.zmyeclipse601200710) requires plug-in “org.eclipse.core.runtime.compatibility”.
MyEclipse Spring Framework Support (6.0.1.zmyeclipse601200710) requires plug-in “org.eclipse.core.runtime.compatibility”.
MyEclipse Web Services Support (6.0.1.zmyeclipse601200710) requires plug-in “org.eclipse.core.runtime.compatibility”.
Dali Java Persistence API (JPA) Tools (0.5.0.zmyeclipse601200710) requires plug-in “org.eclipse.core.runtime”.
JST Common Core (2.0.0.zmyeclipse601200710) requires plug-in “org.eclipse.core.resources (3.2.0)”, or compatible.
JST Server UI (2.0.1.zmyeclipse601200710) requires plug-in “org.eclipse.core.runtime (3.2.0)”, or compatible.
JST Server Core (2.0.1.zmyeclipse601200710) requires plug-in “org.eclipse.core.runtime (3.2.0)”, or compatible.
JST Server Adapters (2.0.1.zmyeclipse601200710) requires plug-in “org.eclipse.core.runtime (3.2.0)”, or compatible.
JST Web UI (2.0.1.zmyeclipse601200710) requires plug-in “org.eclipse.jdt.core (3.2.0)”, or compatible.
JST Web Core (2.0.200.zmyeclipse601200710) requires plug-in “org.eclipse.core.runtime (3.2.0)”, or compatible.
JST Enterprise UI (2.0.1.zmyeclipse601200710) requires plug-in “org.eclipse.jdt.core (3.2.0)”, or compatible.
JST Enterprise Core (2.0.1.zmyeclipse601200710) requires plug-in “org.eclipse.jdt.core (3.2.0)”, or compatible.
WTP Web Page Editor (1.0.1.zmyeclipse601200710) requires plug-in “org.eclipse.core.runtime (3.2.0)”, or compatible.
WST Common UI (2.0.1.zmyeclipse601200710) requires plug-in “org.eclipse.core.runtime (3.2.0)”, or compatible.
WST Common Core (2.0.1.zmyeclipse601200710) requires plug-in “org.eclipse.core.runtime (3.2.0)”, or compatible.
WST Server UI (2.0.1.zmyeclipse601200710) requires plug-in “org.eclipse.core.runtime (3.2.0)”, or compatible.
WST Server Core (2.0.1.zmyeclipse601200710) requires plug-in “org.eclipse.core.runtime (3.2.0)”, or compatible.
WST Server Adapters (2.0.1.zmyeclipse601200710) requires plug-in “org.eclipse.core.runtime (3.2.0)”, or compatible.
Eclipse XML Editors and Tools (2.0.1.zmyeclipse601200710) requires plug-in “org.eclipse.core.resources (3.2.0)”, or compatible.
WST XML Core (2.0.1.zmyeclipse601200710) requires plug-in “org.eclipse.osgi”.
WST Web Services UI (2.0.1.zmyeclipse601200710) requires plug-in “org.eclipse.core.runtime (3.2.0)”, or compatible.
WST Web Services Core (2.0.1.zmyeclipse601200710) requires plug-in “org.eclipse.core.runtime (3.2.0)”, or compatible.
WST Web UI (2.0.1.zmyeclipse601200710) requires plug-in “org.eclipse.ui.ide (3.2.0)”, or compatible.
WST Web Core (2.0.1.zmyeclipse601200710) requires plug-in “org.eclipse.core.runtime (3.2.0)”, or compatible.I’m getting the same or similar error and, having just entered a subscription, am absolutely unimpressed by this, therefore if that problem is not solved soon I will have no choice but to cancel my subscription and look elsewhere for a similar product.
I really have to get going with development work pretty soon!
I received this error already about a month ago during the trial and therefore I un-installed the product, downloaded the latest All In One installer only to be presented with the same problem today after activating the subscription.
Best regards
Hermann
This sounds like a workspace/cache issue to me since you are running into this after using the Full Stack installer.
Can you clean your workspace using the -clean command and check if that solves this issue.
https://www.genuitec.com/forums/topic/troubleshoot-using-the-clean-command-line-argument/Incase the problem perists, you should switch to a brand new workspace and try starting the IDE again.
Further to my precvious message, before I tried the above I un-istalled the installation, deleted the installation folder and re-installed the All in One software.
@support-nipun wrote:
This sounds like a workspace/cache issue to me since you are running into this after using the Full Stack installer.
Can you clean your workspace using the -clean command and check if that solves this issue.
https://www.genuitec.com/forums/topic/troubleshoot-using-the-clean-command-line-argument/Incase the problem perists, you should switch to a brand new workspace and try starting the IDE again.
I tried both. But without success. The workspace is not corrupt. Eclipse/Europa is starting without any problems with the same workspace — only MyEclipse fails. I think your new MyEclipse 6.0.1 image has serious problems.
Guys,
I’m not sure what else to tell you. As far as our All in One installer having “Serious issues”, we’ve had over 250k downloads of it and a lot of happy customers, if our image was corrupted, we would have our support channels *slammed* with reports from our enterprise customers and everyone else. So that is not the problem.The problems you guys are posting are picture-perfect examples of corrupted installs… you’ve said time and time again that you have used the All in One installer to install to a brand new directory, and then run MyEclipse. At that point Nipun and I both thought that the plugin cache inside the workspace could then be to blame, because the errors you are seeing:
MyEclipse Enterprise Workbench (6.0.1.zmyeclipse601200710) requires feature “org.eclipse.platform (3.3.0)”, or equivalent.
This error says MyEclipse 6.0.1 plugin, has a hard-dependency on the Eclipse 3.3.0 or equivalent (3.3.1) and cannot find it… if you are using the All in One installer, that’s all we ship in those installers, so you see my hickup trying to debug your situation given that everything that should be there, is there, but MyEclipse is still having a problem.
I have a feeling that something is going on that is making this very hard for us to trouble shoot, and instead of continuing down this path and getting more and more frustrated, I have an idea.
WE just released our new provisioning platform, Pulse (http://www.poweredbypulse.com), you download this little 2MB client and run it. From there, you can register and create development profiles that consist of platforms like Europa or MyEclipse, and can simply Run them. Pulse will handle *everything* related to upgrading, installing, etc. required for these technologies to run, removing any of the leg work normally required.
I think this may be a much faster and easier way for you guys to use MyEclipse and no longer have to worry about dependencies or reinstalls or anything like that.
Riyad,
I solved the problem by de-installing MyEclipse 6.0.1 and re-installing MyEclipse with your standard installer »MyEclipse_6.0.1GA_E3.3.1_Installer.exe«. I use Eclipse/Europa and the same workspaces as before. Two errors occurred during installation:
– If you continue with update/install, the resulting configuration will contain duplication conflicts that my cause parts of the product to be unusable. Do you want to continue?
– An exception occured while downloading feature from “http://downloads.myeclipseide.com/downloads/products/workbench/discovery-6.0/features/com.genuitec.myeclipse.matisse_6.0.1.zmyeclipse601200710.jar”. Do want to retry?
I answered both with [YES] and it works so far 🙂 However, I received the impression that the installation or the 6.0.1 image is still buggy …
All,
I had the same problem described in BestEclipse’s November 13 post — “Resulting configuration does not contain the platform.” This was on a fresh install of MyEclipse 6.0.1, installed from the ALL iin ONE installer for Windows. There were no other Eclipse versions or old workspaces on the machine, as the computer was brand new (I took it out of the box myself). I didn’t even have any projects created yet.
I tried several things, including wiping out my workspace and creating a new one, deleting JAVA_HOME, and removing all java bin directories from my path. After I found this thread, I uninstalled MyEclipse and reinstalled by installing Eclipse Classic separately and then using the MyEclipse Standalone installer. As described above, the error went away.
The inescapable conclusion is that using the All in ONE installer can lead to issues that can be avoided by installing Eclipse and MyEclipse separately. I don’t have an explanation for this, but I know that I will be avoiding the All in ONE installer in the future.
