Hi,
Not-working VM is OpenJDK 1.6.0_24, working VM is OpenJDK 1.7.0_03. We
didn't try an incremental approach.
I was not able to find the plug-in org.eclipse.e4.tools.emf.ui, our
product is based on features. Adding required features didn't fix the
problem.
After pressing Alt+Shift+F9 under window there's only a Trimmed Window
with ID "IDEWindow".
We were able to make it work by moving an API call from the Activator
start method to a Workbench WindowListener, found the tip at
http://www.eclipsezone.com/eclipse/forums/t114596.html. Waiting for the
workbench to load prior to the API call fixed the problem. We suspect that
it was caused by the plug-ins loading order. Looks like we were trying to
access a code inside a plug-in that was not fully loaded, and the operation
timed out, please have a look at the stack trace below:
!ENTRY org.eclipse.osgi 2 0 2012-07-13 14:37:03.824
!MESSAGE While loading class
"com.android.ddmlib.AndroidDebugBridge$IClientChangeListener", thread
"Thread[DDMS Setup,6,main]" timed out waiting (5007ms) for thread
"Thread[Worker-0,5,main]" to finish starting bundle
"com.android.ide.eclipse.ddms_20.0.0.v201206242043-391819 [6]". To avoid
deadlock, thread "Thread[DDMS Setup,6,main]" is proceeding but
"com.android.ddmlib.AndroidDebugBridge$IClientChangeListener" may not be
fully initialized.
!STACK 0
org.osgi.framework.BundleException: State change in progress for bundle
"reference:file:plugins/com.android.ide.eclipse.ddms_20.0.0.v201206242043-391819.jar"
by thread "Worker-0".
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.beginStateChange(AbstractBundle.java:1088)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:298)
at
org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:440)
at
org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:263)
at
org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107)
at
org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:469)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216)
at
org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:395)
at
org.eclipse.osgi.internal.loader.SingleSourcePackage.loadClass(SingleSourcePackage.java:35)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:461)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
at java.lang.ClassLoader.loadClass(ClassLoader.java:266)
at
com.motorola.studio.android.AndroidPlugin$1.run(AndroidPlugin.java:107)
Caused by:
org.eclipse.osgi.framework.internal.core.AbstractBundle$BundleStatusException
... 15 more
Thanks,
Pablo.
On Sun, Jul 15, 2012 at 2:54 PM, Joseph D Carroll Jr <[email protected]
> wrote:
> Pablo-
>
> Could you provide a little more information, specifically what are the
> build numbers of the JVM's you are using (both working and not-working).
>
> Also, have you tried any kind of incremental approach, as in it works for
> features x & y and x & z but not x, y, & z?
>
> Lastly, if you include org.eclipse.e4.tools.emf.ui (make sure you 'Add
> Required Plug-ins') and press Alt+Shift+F9 what is listed under windows?
>
> Thanks,
>
> JD
>
> On Fri, Jul 13, 2012 at 2:14 PM, Pablo Leite <[email protected]> wrote:
>
>> Hi,
>>
>> We are using the compatibility layer to run our RCP on Eclipse 4.2.
>> Everything works fine on Windows and Mac OS-X, however on Linux (Ubuntu
>> 12.4) and java 1.6 all we got is a blank window with the Eclipse SDK title.
>> If we change the java to java 1.7, the RCP works fine, which is
>> strange since there's no dependency on Java 1.7.
>>
>> In order to enable the compatibility mode on our product we've added
>> the features below to the product definition:
>> org.eclipse.emf.ecore
>> org.eclipse.emf.common
>> And the following plug-ins as dependency
>> org.eclipse.e4.ui.workbench,
>> org.eclipse.e4.ui.workbench.addons.swt,
>> org.eclipse.equinox.ds,
>> org.eclipse.equinox.event,
>> org.eclipse.ui.forms
>>
>> Some properties also had to be added to the product's plugin.xml file
>> in order to make css themes work:
>> <property
>> name="applicationXMI"
>> value="org.eclipse.platform/LegacyIDE.e4xmi">
>> </property>
>> <property
>> name="cssTheme"
>> value="org.eclipse.e4.ui.css.theme.e4_default">
>> </property>
>> <property
>> name="applicationCSSResources"
>> value="platform:/plugin/org.eclipse.platform/images">
>> </property>
>>
>> Are we missing something? Is this a possible e4 bug? We just have no
>> clue on how to solve this problem.
>>
>> Thanks,
>> Pablo.
>>
>> --
>> Pablo
>>
>> _______________________________________________
>> e4-dev mailing list
>> [email protected]
>> https://dev.eclipse.org/mailman/listinfo/e4-dev
>>
>>
>
> _______________________________________________
> e4-dev mailing list
> [email protected]
> https://dev.eclipse.org/mailman/listinfo/e4-dev
>
>
--
Pablo
_______________________________________________
e4-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/e4-dev
