Ajuda Instalação Eclipse 3.0M9

Pessoal,

Ao tentar executar o eclipse a mensagem abaixo é gerada no log.

!SESSION Mai 25, 2004 08:19:50.545 ---------------------------------------------

eclipse.buildId=I200405211200

java.version=1.3.1_01

java.vendor=Sun Microsystems Inc.

BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=pt_BR

!ENTRY org.eclipse.osgi Mai 25, 2004 08:19:50.560

!MESSAGE Error registering XML parser services.

!STACK 0

java.lang.ClassNotFoundException: javax.xml.parsers.SAXParserFactory

at java.net.URLClassLoader$1.run(Unknown Source)

at java.security.AccessController.doPrivileged(Native Method)

at java.net.URLClassLoader.findClass(Unknown Source)

at java.lang.ClassLoader.loadClass(Unknown Source)

at java.lang.ClassLoader.loadClass(Unknown Source)

at java.lang.ClassLoader.loadClassInternal(Unknown Source)

at java.lang.Class.forName0(Native Method)

at java.lang.Class.forName(Unknown Source)

at org.eclipse.core.runtime.adaptor.EclipseAdaptor.registerEndorsedXMLParser(EclipseAdaptor.java:251)

at org.eclipse.core.runtime.adaptor.EclipseAdaptor.frameworkStart(EclipseAdaptor.java:233)

at org.eclipse.osgi.framework.internal.core.SystemBundleActivator.start(SystemBundleActivator.java:61)

at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:958)

at java.security.AccessController.doPrivileged(Native Method)

at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:954)

at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:937)

at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:548)

at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:472)

at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:273)

at org.eclipse.osgi.framework.internal.core.StartLevelManager.launch(StartLevelManager.java:243)

at org.eclipse.osgi.framework.internal.core.SystemBundle.resume(SystemBundle.java:166)

at org.eclipse.osgi.framework.internal.core.Framework.launch(Framework.java:423)

at org.eclipse.osgi.framework.internal.core.OSGi.launch(OSGi.java:51)

at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:213)

at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:125)

at java.lang.reflect.Method.invoke(Native Method)

at org.eclipse.core.launcher.Main.basicRun(Main.java:185)

at org.eclipse.core.launcher.Main.run(Main.java:638)

at org.eclipse.core.launcher.Main.main(Main.java:622)

!ENTRY org.eclipse.osgi Mai 25, 2004 08:19:50.623

!MESSAGE Startup error

!STACK 1

java.lang.NoClassDefFoundError: org/xml/sax/helpers/DefaultHandler

at java.lang.ClassLoader.defineClass0(Native Method)

at java.lang.ClassLoader.defineClass(Unknown Source)

at java.security.SecureClassLoader.defineClass(Unknown Source)

at java.net.URLClassLoader.defineClass(Unknown Source)

at java.net.URLClassLoader.access$100(Unknown Source)

at java.net.URLClassLoader$1.run(Unknown Source)

at java.security.AccessController.doPrivileged(Native Method)

at java.net.URLClassLoader.findClass(Unknown Source)

at java.lang.ClassLoader.loadClass(Unknown Source)

at java.lang.ClassLoader.loadClass(Unknown Source)

at java.lang.ClassLoader.loadClassInternal(Unknown Source)

at org.eclipse.core.runtime.adaptor.PluginConverterImpl.parsePluginInfo(PluginConverterImpl.java:547)

at org.eclipse.core.runtime.adaptor.PluginConverterImpl.fillPluginInfo(PluginConverterImpl.java:108)

at org.eclipse.core.runtime.adaptor.PluginConverterImpl.convertManifest(PluginConverterImpl.java:650)

at org.eclipse.core.runtime.adaptor.EclipseBundleData.generateManifest(EclipseBundleData.java:196)

at org.eclipse.core.runtime.adaptor.EclipseBundleData.loadManifest(EclipseBundleData.java:173)

at org.eclipse.core.runtime.adaptor.EclipseBundleData.getManifest(EclipseBundleData.java:155)

at org.eclipse.core.runtime.adaptor.EclipseBundleData.loadFromManifest(EclipseBundleData.java:236)

at org.eclipse.osgi.framework.internal.defaultadaptor.DefaultBundleData.initializeNewBundle(DefaultBundleData.java:77)

at org.eclipse.osgi.framework.internal.defaultadaptor.DefaultAdaptor$1.begin(DefaultAdaptor.java:436)

at org.eclipse.osgi.framework.internal.core.Framework.installWorkerPrivileged(Framework.java:739)

at org.eclipse.osgi.framework.internal.core.Framework$2.run(Framework.java:657)

at java.security.AccessController.doPrivileged(Native Method)

at org.eclipse.osgi.framework.internal.core.Framework.installWorker(Framework.java:708)

at org.eclipse.osgi.framework.internal.core.Framework.installBundle(Framework.java:652)

at org.eclipse.osgi.framework.internal.core.BundleContextImpl.installBundle(BundleContextImpl.java:219)

at org.eclipse.core.runtime.adaptor.EclipseStarter.loadBasicBundles(EclipseStarter.java:438)

at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:219)

at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:125)

at java.lang.reflect.Method.invoke(Native Method)

at org.eclipse.core.launcher.Main.basicRun(Main.java:185)

at org.eclipse.core.launcher.Main.run(Main.java:638)

at org.eclipse.core.launcher.Main.main(Main.java:622)

[/u]

Running Eclipse

After installing the Eclipse SDK in a directory, you can start the Workbench by running the Eclipse executable included with the release (you also need a JRE, included with the Eclipse SDK). On Windows, the executable file is called eclipse.exe, and is located in the eclipse subdirectory of the install. If installed at c:eclipse-SDK-2.1-win32, the executable is c:eclipse-SDK-2.1-win32eclipseeclipse.exe. Note: Set-up on other operating environments is analogous.

If you do not specify otherwise, Eclipse creates a default workspace in a subdirectory as a sibling of the executable (that is, at, c:eclipse-SDK-2.1-win32eclipseworkspace). This workspace directory is used as the default content area for your projects as well as for holding any required metadata. For shared or multi-workspace installs you must explicitly specify the location for your workspace using the “-data” command line argument; for example,

eclipse -data c:myworkspace -vm c:jdk1.4.1_01jreinjavaw

Tip: It’s generally a good idea to explicitly specify which Java VM to use when running Eclipse. This is achieved with the “-vm” command line argument as illustrated above. If you don’t use “-vm”, Eclipse will look on the O/S path. When you install other Java-based products, they may change your path and could result in a different Java VM being used when you next launch Eclipse.

To create a Windows shortcut to an installed Eclipse and a particular workspace (e.g., c:myworkspace):

Navigate to eclipse.exe in Windows Explorer and use Create Shortcut on the content menu.
Select the shortcut and edit its Properties. In the Target: field append the -data option followed by the location of the workspace (e.g., -data “c:myworkspace”).

3 Respostas

Topicos relacionados