| Migration an Eclipse 3.x RCP application to E4: product problem [message #1239230] |
Mon, 03 February 2014 17:58  |
|
Hi,
I am working on project developed in Eclipse Helios, migrating from Eclipse 3.x to Eclipse 4 (in Luna release), when i run RCP application, as "run a product" the following errors on stack trace is shown:
...
org.eclipse.core.runtime.AssertionFailedException: null argument:
at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85)
at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:73)
at org.eclipse.jface.resource.ColorRegistry.put(ColorRegistry.java:308)
at org.eclipse.jface.resource.ColorRegistry.put(ColorRegistry.java:287)
at org.eclipse.ui.internal.themes.ThemeElementHelper.installColor(ThemeElementHelper.java:311)
at org.eclipse.ui.internal.themes.ThemeElementHelper.populateRegistry(ThemeElementHelper.java:172)
at org.eclipse.ui.internal.Workbench$28.runWithException(Workbench.java:1665)
at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4145)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3762)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2706)
at org.eclipse.ui.internal.Workbench.access$7(Workbench.java:2614)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:609)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:565)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at xx.yyy.zzzz.Application.start(Application.java:42)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:109)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:80)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:372)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:226)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
...
In the ".metadata\.plugin" folder, the folders were NOT created:
- org.eclipse.core.runtime
- org.eclipse.e4.workbench
- org.eclipse.ui.workbench
Any suggestions?
Thanks in advance.
|
|
|
|
| Re: Migration an Eclipse 3.x RCP application to E4: product problem [message #1240038 is a reply to message #1239828] |
Wed, 05 February 2014 15:23  |
|
Hi Divya,
thanks very much, your document marked is really interessing.
But my dream ( )if it possibile, to do this migration without any change the code of the my project.
By observing the eclipse stack trace, It seems that my project is using some kind of color, which is no longer supported, but I can not have more details about kind of error.
bye,
Pina
|
|
|
|
| Re: Migration an Eclipse 3.x RCP application to E4: product problem [message #1240523 is a reply to message #1240290] |
Thu, 06 February 2014 17:18 |
|
Hi,
The error raised in Kepler depends on the management of custom themes in my project.
I am using "org.eclipse.ui.theme" extension point to customize colors in my views with the follwing theme category structure:
I Attach my custom plugin.xml file used and a screenshot during debug of my code.
You can see debugging of the code in the screenshot attached what happens when the
symbolic name is the "ColorBkgStepInfo" value, no value is bind to variable "ColorData".
Indeed the plugin.xml shows the assigned value:
<colorDefinition
categoryId="AppsColors"
defaultsTo="255,250,250"
id="ColorBkgStepInfo"
isEditable="true"
label="Step Info Background Color">
<description>
Background color for the step info area.
</description>
</colorDefinition>
This works fine in Helios release, and now in Kepler it raise an exception.
I'd appreciate any help/suggestion on that point.
Regards,
Pina
Attachment: BugThemeEx.PNG
(Size: 198.28KB, Downloaded 270 times)
Attachment: plugin.xml
(Size: 38.54KB, Downloaded 274 times)
[Updated on: Thu, 06 February 2014 17:21] Report message to a moderator |
|
|
Powered by
FUDForum. Page generated in 0.03948 seconds
] 
Search
Help
Register
Login
Home
I don't know. May be it depends. In my case when I migrated using compatibility layer then also I had to put some code patches here and there to make my code running.