| How to use the VE SDK [message #50438] |
Thu, 15 July 2004 16:46  |
Eclipse User |
|
|
|
I'm new to Eclipse PlugIn development. I'm interested in creating a
VisualBuilder for our own proprietary 4GL development system.
So wanted to run VE and examine source of VE.
I've downloaded the latest version of the SDK (VE-SDK-20040628.zip).
I unzipped this to my plugin directory and restarted Eclipse.
When I view the "Help About" the set of features for GEF, EMF, JEM, and VE
match what is mentioned in the FAQ.
But I get the below exception when I try to open the Visual Editor on a
java file.
I tried the procedure in the FAQ named:
How do I develop on top of VE (i.e. extend the VE)?
I still get the exception below and now I have a ton of projects in my
workspace.
------------------------------------------------------------ ------------------
org.eclipse.core.runtime.CoreException[1]:
java.lang.ClassNotFoundException:
org.eclipse.ve.internal.java.codegen.editorpart.JavaVisualEd itorPart
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:404)
at
org.eclipse.osgi.framework.adaptor.core.AbstractClassLoader. loadClass(AbstractClassLoader.java:93)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.loadCl ass(BundleLoader.java:307)
at
org.eclipse.osgi.framework.internal.core.BundleHost.loadClas s(BundleHost.java:336)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.load Class(AbstractBundle.java:1313)
at
org.eclipse.core.internal.registry.ConfigurationElement.crea teExecutableExtension(ConfigurationElement.java:131)
at
org.eclipse.core.internal.registry.ConfigurationElement.crea teExecutableExtension(ConfigurationElement.java:124)
at
org.eclipse.core.internal.registry.ConfigurationElement.crea teExecutableExtension(ConfigurationElement.java:113)
at org.eclipse.ui.internal.WorkbenchPlugin$1.run(WorkbenchPlugi n.java:196)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:69)
at
org.eclipse.ui.internal.WorkbenchPlugin.createExtension(Work benchPlugin.java:193)
at org.eclipse.ui.internal.EditorManager$5.run(EditorManager.ja va:790)
at
org.eclipse.core.internal.runtime.InternalPlatform.run(Inter nalPlatform.java:615)
at org.eclipse.core.runtime.Platform.run(Platform.java:747)
at
org.eclipse.ui.internal.EditorManager.createPart(EditorManag er.java:788)
at
org.eclipse.ui.internal.EditorManager.openInternalEditor(Edi torManager.java:775)
at
org.eclipse.ui.internal.EditorManager.openEditorFromDescript or(EditorManager.java:585)
at
org.eclipse.ui.internal.EditorManager.openEditor(EditorManag er.java:573)
at
org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched( WorkbenchPage.java:2201)
at
org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(Workben chPage.java:2134)
at org.eclipse.ui.internal.WorkbenchPage.access$6(WorkbenchPage .java:2126)
at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.ja va:2113)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:69)
at
org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPa ge.java:2108)
at
org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPa ge.java:2091)
at org.eclipse.ui.actions.OpenWithMenu.openEditor(OpenWithMenu. java:258)
at org.eclipse.ui.actions.OpenWithMenu.access$0(OpenWithMenu.ja va:251)
at
org.eclipse.ui.actions.OpenWithMenu$2.handleEvent(OpenWithMe nu.java:166)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :82)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:796)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:2772)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2431)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:1377)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1348)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:254)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:141)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:96)
at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.java:335)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:273)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:129)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.eclipse.core.launcher.Main.basicRun(Main.java:183)
at org.eclipse.core.launcher.Main.run(Main.java:644)
at org.eclipse.core.launcher.Main.main(Main.java:628)
------------------------------------------------------------ ------------------
|
|
|
|
|
|
|
| Re: How to use the VE SDK [message #50912 is a reply to message #50857] |
Mon, 19 July 2004 15:11  |
| Eclipse User |
|
|
|
Steve
You have (maybe) any plugin with gef libraries inside plugin
(jfacedbc or sqlexplorer have this; older version myeclipse <3.8beta2
have gef < 3.0, too)
You try delete this plugin (if You have one)
regards
Steve Harper wrote:
> "Help About | Feature Details" shows these versions:
> Eclipse Project SDK 3.0.0
> Visual Editor 1.0.0
> GEF 3.0.0
> EMF 2.0.0
>
> I tried a reinstall and reloaded just the runtime of VE and insured I had
> the recommended version of GEF and EMF - still got the same ClassNotFound
> exception when I try to run the created Visual Editor Wizard or open an
> exising Java file with the Visual Editor.
>
> What happens to the rest of my eclipse environment if I delete the
> configuration directory. I also use Eclipse to develop Java that is not a
> PlugIn. Sure it's OK to delete configuration directory?
>
>
>
> Jeff Myers wrote:
>
>> Steve,
>
>> Please reply with a list the versions of VE, GEF, EMF and Eclipse you
>> have installed. It may also help to delete the configuration directory
>> in your eclipse directory and see if that helps.
>
>> Thanks,
>
>> - Jeff
|
|
|
| Re: How to use the VE SDK [message #50939 is a reply to message #50885] |
Mon, 19 July 2004 13:30 |
| Eclipse User |
|
|
|
Thanks Rich the -clean option worked.
I can now run VE.
Thanks for all the help.
Rich Kulp wrote:
> Just use the -clean argument on your command line. That is the better
> equivalent to erasing the configuration directory. BUT only do it the
> first, DON'T use -clean everytime or you will keep clearing the
> configuration directory and recreating it.
|
|
|
| Re: How to use the VE SDK [message #50967 is a reply to message #50939] |
Mon, 19 July 2004 14:05 |
| Eclipse User |
|
|
|
Originally posted by: myersj.nospam.us.ibm.com
Steve,
Using the -clean option is equivalent to removing your configuration
directory. The configuration directory is a cache of the information
about the plug-ins you have installed. Your user Eclipse options and
preferences are stored in the .metadata directory in your workspace.
This trouble with the configuration directory that so many people are
running into is due to the builds of VE having the same plug-in version
number. When Eclipse comes up it checks to see if the version numbers
have changed, and if not, doesn't bother updating the cached info for
that plug-in. So often when upgrading to new development versions of VE
(as opposed to new point releases) you need to clear out the cached
configuration info to get it to recognize the changes properly.
- Jeff
Steve Harper wrote:
> Thanks Rich the -clean option worked.
> I can now run VE.
>
> Thanks for all the help.
>
>
> Rich Kulp wrote:
>
>
>>Just use the -clean argument on your command line. That is the better
>>equivalent to erasing the configuration directory. BUT only do it the
>>first, DON'T use -clean everytime or you will keep clearing the
>>configuration directory and recreating it.
>
>
>
>
|
|
|
| Re: How to use the VE SDK [message #595325 is a reply to message #50438] |
Thu, 15 July 2004 20:48 |
| Eclipse User |
|
|
|
You have wrong GFE or draw2d (maybe from another plugin like myeclipse,
jfacedbc, sqlexplorer etc)
regards
Steve Harper wrote:
> I'm new to Eclipse PlugIn development. I'm interested in creating a
> VisualBuilder for our own proprietary 4GL development system.
> So wanted to run VE and examine source of VE.
> I've downloaded the latest version of the SDK (VE-SDK-20040628.zip).
> I unzipped this to my plugin directory and restarted Eclipse.
> When I view the "Help About" the set of features for GEF, EMF, JEM, and VE
> match what is mentioned in the FAQ.
>
> But I get the below exception when I try to open the Visual Editor on a
> java file.
>
> I tried the procedure in the FAQ named:
> How do I develop on top of VE (i.e. extend the VE)?
> I still get the exception below and now I have a ton of projects in my
> workspace.
>
>
>
------------------------------------------------------------ ------------------
> org.eclipse.core.runtime.CoreException[1]:
> java.lang.ClassNotFoundException:
> org.eclipse.ve.internal.java.codegen.editorpart.JavaVisualEd itorPart
> at
>
org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:404)
> at
>
org.eclipse.osgi.framework.adaptor.core.AbstractClassLoader. loadClass(AbstractClassLoader.java:93)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
> at
>
org.eclipse.osgi.framework.internal.core.BundleLoader.loadCl ass(BundleLoader.java:307)
> at
>
org.eclipse.osgi.framework.internal.core.BundleHost.loadClas s(BundleHost.java:336)
> at
>
org.eclipse.osgi.framework.internal.core.AbstractBundle.load Class(AbstractBundle.java:1313)
> at
>
org.eclipse.core.internal.registry.ConfigurationElement.crea teExecutableExtension(ConfigurationElement.java:131)
> at
>
org.eclipse.core.internal.registry.ConfigurationElement.crea teExecutableExtension(ConfigurationElement.java:124)
> at
>
org.eclipse.core.internal.registry.ConfigurationElement.crea teExecutableExtension(ConfigurationElement.java:113)
> at org.eclipse.ui.internal.WorkbenchPlugin$1.run(WorkbenchPlugi n.java:196)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:69)
> at
>
org.eclipse.ui.internal.WorkbenchPlugin.createExtension(Work benchPlugin.java:193)
> at org.eclipse.ui.internal.EditorManager$5.run(EditorManager.ja va:790)
> at
>
org.eclipse.core.internal.runtime.InternalPlatform.run(Inter nalPlatform.java:615)
> at org.eclipse.core.runtime.Platform.run(Platform.java:747)
> at
> org.eclipse.ui.internal.EditorManager.createPart(EditorManag er.java:788)
> at
>
org.eclipse.ui.internal.EditorManager.openInternalEditor(Edi torManager.java:775)
> at
>
org.eclipse.ui.internal.EditorManager.openEditorFromDescript or(EditorManager.java:585)
> at
> org.eclipse.ui.internal.EditorManager.openEditor(EditorManag er.java:573)
> at
>
org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched( WorkbenchPage.java:2201)
> at
>
org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(Workben chPage.java:2134)
> at org.eclipse.ui.internal.WorkbenchPage.access$6(WorkbenchPage .java:2126)
> at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.ja va:2113)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:69)
> at
> org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPa ge.java:2108)
> at
> org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPa ge.java:2091)
> at org.eclipse.ui.actions.OpenWithMenu.openEditor(OpenWithMenu. java:258)
> at org.eclipse.ui.actions.OpenWithMenu.access$0(OpenWithMenu.ja va:251)
> at
> org.eclipse.ui.actions.OpenWithMenu$2.handleEvent(OpenWithMe nu.java:166)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :82)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:796)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:2772)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2431)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:1377)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1348)
> at
>
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:254)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:141)
> at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:96)
> at
>
org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.java:335)
> at
>
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:273)
> at
>
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:129)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
>
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
> at
>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at org.eclipse.core.launcher.Main.basicRun(Main.java:183)
> at org.eclipse.core.launcher.Main.run(Main.java:644)
> at org.eclipse.core.launcher.Main.main(Main.java:628)
>
------------------------------------------------------------ ------------------
|
|
|
| Re: How to use the VE SDK [message #595383 is a reply to message #50438] |
Fri, 16 July 2004 10:22 |
| Eclipse User |
|
|
|
Steve,
Please reply with a list the versions of VE, GEF, EMF and Eclipse you
have installed. It may also help to delete the configuration directory
in your eclipse directory and see if that helps.
Thanks,
- Jeff
Steve Harper wrote:
> I'm new to Eclipse PlugIn development. I'm interested in creating a
> VisualBuilder for our own proprietary 4GL development system.
> So wanted to run VE and examine source of VE.
> I've downloaded the latest version of the SDK (VE-SDK-20040628.zip).
> I unzipped this to my plugin directory and restarted Eclipse.
> When I view the "Help About" the set of features for GEF, EMF, JEM, and VE
> match what is mentioned in the FAQ.
>
> But I get the below exception when I try to open the Visual Editor on a
> java file.
>
> I tried the procedure in the FAQ named:
> How do I develop on top of VE (i.e. extend the VE)?
> I still get the exception below and now I have a ton of projects in my
> workspace.
>
>
> ------------------------------------------------------------ ------------------
> org.eclipse.core.runtime.CoreException[1]:
> java.lang.ClassNotFoundException:
> org.eclipse.ve.internal.java.codegen.editorpart.JavaVisualEd itorPart
> at
> org.eclipse.osgi.framework.internal.core.BundleLoader.findCl ass(BundleLoader.java:404)
> at
> org.eclipse.osgi.framework.adaptor.core.AbstractClassLoader. loadClass(AbstractClassLoader.java:93)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
> at
> org.eclipse.osgi.framework.internal.core.BundleLoader.loadCl ass(BundleLoader.java:307)
> at
> org.eclipse.osgi.framework.internal.core.BundleHost.loadClas s(BundleHost.java:336)
> at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.load Class(AbstractBundle.java:1313)
> at
> org.eclipse.core.internal.registry.ConfigurationElement.crea teExecutableExtension(ConfigurationElement.java:131)
> at
> org.eclipse.core.internal.registry.ConfigurationElement.crea teExecutableExtension(ConfigurationElement.java:124)
> at
> org.eclipse.core.internal.registry.ConfigurationElement.crea teExecutableExtension(ConfigurationElement.java:113)
> at org.eclipse.ui.internal.WorkbenchPlugin$1.run(WorkbenchPlugi n.java:196)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:69)
> at
> org.eclipse.ui.internal.WorkbenchPlugin.createExtension(Work benchPlugin.java:193)
> at org.eclipse.ui.internal.EditorManager$5.run(EditorManager.ja va:790)
> at
> org.eclipse.core.internal.runtime.InternalPlatform.run(Inter nalPlatform.java:615)
> at org.eclipse.core.runtime.Platform.run(Platform.java:747)
> at
> org.eclipse.ui.internal.EditorManager.createPart(EditorManag er.java:788)
> at
> org.eclipse.ui.internal.EditorManager.openInternalEditor(Edi torManager.java:775)
> at
> org.eclipse.ui.internal.EditorManager.openEditorFromDescript or(EditorManager.java:585)
> at
> org.eclipse.ui.internal.EditorManager.openEditor(EditorManag er.java:573)
> at
> org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched( WorkbenchPage.java:2201)
> at
> org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(Workben chPage.java:2134)
> at org.eclipse.ui.internal.WorkbenchPage.access$6(WorkbenchPage .java:2126)
> at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.ja va:2113)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:69)
> at
> org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPa ge.java:2108)
> at
> org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPa ge.java:2091)
> at org.eclipse.ui.actions.OpenWithMenu.openEditor(OpenWithMenu. java:258)
> at org.eclipse.ui.actions.OpenWithMenu.access$0(OpenWithMenu.ja va:251)
> at
> org.eclipse.ui.actions.OpenWithMenu$2.handleEvent(OpenWithMe nu.java:166)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :82)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:796)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:2772)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2431)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:1377)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1348)
> at
> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:254)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:141)
> at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:96)
> at
> org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.java:335)
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:273)
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:129)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at org.eclipse.core.launcher.Main.basicRun(Main.java:183)
> at org.eclipse.core.launcher.Main.run(Main.java:644)
> at org.eclipse.core.launcher.Main.main(Main.java:628)
> ------------------------------------------------------------ ------------------
>
>
|
|
|
| Re: How to use the VE SDK [message #595470 is a reply to message #50606] |
Mon, 19 July 2004 11:57 |
| Eclipse User |
|
|
|
"Help About | Feature Details" shows these versions:
Eclipse Project SDK 3.0.0
Visual Editor 1.0.0
GEF 3.0.0
EMF 2.0.0
I tried a reinstall and reloaded just the runtime of VE and insured I had
the recommended version of GEF and EMF - still got the same ClassNotFound
exception when I try to run the created Visual Editor Wizard or open an
exising Java file with the Visual Editor.
What happens to the rest of my eclipse environment if I delete the
configuration directory. I also use Eclipse to develop Java that is not a
PlugIn. Sure it's OK to delete configuration directory?
Jeff Myers wrote:
> Steve,
> Please reply with a list the versions of VE, GEF, EMF and Eclipse you
> have installed. It may also help to delete the configuration directory
> in your eclipse directory and see if that helps.
> Thanks,
> - Jeff
|
|
|
| Re: How to use the VE SDK [message #595475 is a reply to message #50857] |
Mon, 19 July 2004 12:50 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.NO.SPAM.us.ibm.com
Just use the -clean argument on your command line. That is the better
equivalent to erasing the configuration directory. BUT only do it the
first, DON'T use -clean everytime or you will keep clearing the
configuration directory and recreating it.
--
Thanks, Rich Kulp
|
|
|
| Re: How to use the VE SDK [message #595479 is a reply to message #50857] |
Mon, 19 July 2004 15:11 |
| Eclipse User |
|
|
|
Steve
You have (maybe) any plugin with gef libraries inside plugin
(jfacedbc or sqlexplorer have this; older version myeclipse <3.8beta2
have gef < 3.0, too)
You try delete this plugin (if You have one)
regards
Steve Harper wrote:
> "Help About | Feature Details" shows these versions:
> Eclipse Project SDK 3.0.0
> Visual Editor 1.0.0
> GEF 3.0.0
> EMF 2.0.0
>
> I tried a reinstall and reloaded just the runtime of VE and insured I had
> the recommended version of GEF and EMF - still got the same ClassNotFound
> exception when I try to run the created Visual Editor Wizard or open an
> exising Java file with the Visual Editor.
>
> What happens to the rest of my eclipse environment if I delete the
> configuration directory. I also use Eclipse to develop Java that is not a
> PlugIn. Sure it's OK to delete configuration directory?
>
>
>
> Jeff Myers wrote:
>
>> Steve,
>
>> Please reply with a list the versions of VE, GEF, EMF and Eclipse you
>> have installed. It may also help to delete the configuration directory
>> in your eclipse directory and see if that helps.
>
>> Thanks,
>
>> - Jeff
|
|
|
| Re: How to use the VE SDK [message #595483 is a reply to message #50885] |
Mon, 19 July 2004 13:30 |
| Eclipse User |
|
|
|
Thanks Rich the -clean option worked.
I can now run VE.
Thanks for all the help.
Rich Kulp wrote:
> Just use the -clean argument on your command line. That is the better
> equivalent to erasing the configuration directory. BUT only do it the
> first, DON'T use -clean everytime or you will keep clearing the
> configuration directory and recreating it.
|
|
|
| Re: How to use the VE SDK [message #595492 is a reply to message #50939] |
Mon, 19 July 2004 14:05 |
| Eclipse User |
|
|
|
Steve,
Using the -clean option is equivalent to removing your configuration
directory. The configuration directory is a cache of the information
about the plug-ins you have installed. Your user Eclipse options and
preferences are stored in the .metadata directory in your workspace.
This trouble with the configuration directory that so many people are
running into is due to the builds of VE having the same plug-in version
number. When Eclipse comes up it checks to see if the version numbers
have changed, and if not, doesn't bother updating the cached info for
that plug-in. So often when upgrading to new development versions of VE
(as opposed to new point releases) you need to clear out the cached
configuration info to get it to recognize the changes properly.
- Jeff
Steve Harper wrote:
> Thanks Rich the -clean option worked.
> I can now run VE.
>
> Thanks for all the help.
>
>
> Rich Kulp wrote:
>
>
>>Just use the -clean argument on your command line. That is the better
>>equivalent to erasing the configuration directory. BUT only do it the
>>first, DON'T use -clean everytime or you will keep clearing the
>>configuration directory and recreating it.
>
>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.05063 seconds
Home