[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Newsgroup Home]
|
[news.eclipse.webtools] Eclipse+WTP 3.4M7 startup trouble!?
|
- From: Frits Jalvingh <jal@xxxxxx>
- Date: Thu, 08 May 2008 13:53:22 +0200
- Newsgroups: eclipse.webtools
- Organization: EclipseCorner
- User-agent: KNode/0.10.9
I just installed Eclipse 3.4m7 and wtp 3.0 m7 by untarring the eclipse gtk
tar and unzipping the WTP files over that. This usually works without any
problem.
But now, when I start this installation, I get:
- the Eclipse splash screen
- Eclipse uses CPU for some 10 seconds, then the CPU stays idle
- The splash stays on-screen for > 10 minutes(!)
- After the 10 minutes Eclipse starts, but WTP is not installed.
The console shows:
Artifact repository out of sync.
Overwriting /home/jal/opt/e-3.4m7/plugins/org.eclipse.datatools.intro_1.0.0.200706071.jar
Artifact repository out of sync.
Overwriting /home/jal/opt/e-3.4m7/plugins/org.eclipse.datatools.doc.user_1.0.0.200706071.jar
Artifact repository out of sync.
Overwriting /home/jal/opt/e-3.4m7/plugins/org.apache.commons.discovery_0.2.0.v200706111329
Artifact repository out of sync.
Overwriting /home/jal/opt/e-3.4m7/plugins/org.eclipse.jem.beaninfo_2.0.0.v200705302225.jar
Artifact repository out of sync.
Overwriting /home/jal/opt/e-3.4m7/plugins/org.eclipse.jem.ui_2.0.0.v200705302225.jar
Artifact repository out of sync.
Overwriting /home/jal/opt/e-3.4m7/plugins/org.eclipse.jst.common.annotations.ui_1.1.2.v200706120315.jar
Artifact repository out of sync.
Overwriting /home/jal/opt/e-3.4m7/plugins/org.eclipse.wst.common.infopop_1.0.2.v200706110217.jar
Artifact repository out of sync.
Overwriting /home/jal/opt/e-3.4m7/plugins/org.eclipse.wst.validation.infopop_1.0.202.v200706110217.jar
Artifact repository out of sync.
Overwriting /home/jal/opt/e-3.4m7/plugins/org.eclipse.wst.wsi.ui.doc.user_1.0.203.v200706120315.jar
I did notice that in M6 the new update manager caused huge startup delays
also when new software was installed (about 4 minutes for the 1st startup
when new software was installed) but that continued to use CPU all that
time AND resulted in a usable installation....
Any thoughts on this?
Frits