Home » Eclipse Projects » Plugin Development Environment (PDE) » Eclipse RCP app hang on MACOSX 10.6(RCP App hangs indefinitely on startup on macosx 10.6 cocoa)
| |
Re: Eclipse RCP app hang on MACOSX 10.6 [message #525665 is a reply to message #525657] |
Wed, 07 April 2010 12:27 |
Christian Messages: 8 Registered: April 2010 |
Junior Member |
|
|
Hello Ralf, thanks for the answer,
our RCP application is deployed as an eclipse product :
--eclipse
|---configuration
| |---config.ini
|---eclipse.exe
|---eclipse.ini
|---plugins
|---...
With the following eclipse.ini file:
-startup
plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715. jar
--launcher.library
plugins/org.eclipse.equinox.launcher.cocoa.macosx_1.0.1.R35x _v20090707
-os
-ws
-arch
-nl
-clean
-console
-consolelog
-vmargs
-Driena.lnf=ch.llb.contact.ui.applications.LigueLnf
-Driena.application.width=1120
-Driena.application.height=850
-Driena.lnf.update.view=true
-Dreport.output.dir=
Any suggestion ?
Regards
Christian.
Here is our config.ini file:
#This configuration file was written by: org.eclipse.equinox.internal.frameworkadmin.equinox.EquinoxF wConfigFileParser
#Tue Sep 15 18:23:11 CEST 2009
osgi.bundles=reference\:file\:ch.llb.abonnement.busi_1.0.0.jar@4, \
reference\:file\:ch.llb.abonnement.entity_1.0.0.jar@4, \
reference\:file\:ch.llb.abonnement.report_1.0.0.jar@4\:start, \
reference\:file\:ch.llb.activite.busi_1.0.0.jar@4, \
reference\:file\:ch.llb.activite.entity_1.0.0.jar@4, \
reference\:file\:ch.llb.activite.report_1.0.0.jar@4\:start, \
reference\:file\:ch.llb.common.report-i18n_1.0.0.jar@4, \
reference\:file\:ch.llb.common.report_1.0.0.jar@4, \
reference\:file\:ch.llb.common.i18n_1.0.0.jar@4, \
reference\:file\:ch.llb.common.ui-i18n_1.0.0.jar@4, \
reference\:file\:ch.llb.common.util_1.0.0.jar@4, \
reference\:file\:ch.llb.common.vo_1.0.0.jar@4, \
reference\:file\:ch.llb.contact.busi_1.0.0.jar@4, \
reference\:file\:ch.llb.contact.entity_1.0.0.jar@4, \
reference\:file\:ch.llb.contact.report_1.0.0.jar@4\:start, \
reference\:file\:ch.llb.contact.ui_1.0.0.200909151822.jar@4, \
reference\:file\:ch.llb.contact.ui.stage.prod_1.0.0.jar@4, \
reference\:file\:ch.llb.don.busi_1.0.0.jar@4, \
reference\:file\:ch.llb.don.entity_1.0.0.jar@4, \
reference\:file\:ch.llb.facturation.busi_1.0.0.jar@4, \
reference\:file\:ch.llb.facturation.entity_1.0.0.jar@4, \
reference\:file\:ch.llb.librairie.busi_1.0.0.jar@4, \
reference\:file\:ch.llb.librairie.entity_1.0.0.jar@4, \
reference\:file\:ch.llb.librairie.report_1.0.0.jar@4\:start, \
reference\:file\:ch.llb.reference.busi_1.0.0.jar@4, \
reference\:file\:ch.llb.reference.entity_1.0.0.jar@4, \
reference\:file\:asm.osgi-2.2.3-SNAPSHOT.jar@4, \
reference\:file\:com.caucho.hessian_3.1.3.jar@4, \
reference\:file\:com.ibm.icu_4.0.1.v20090415.jar@4, \
reference\:file\:com.lowagie.itext-2.1.0.jar@4, \
reference\:file\:com.springsource.antlr-2.7.7.jar@4, \
reference\:file\:commons-collections-3.2.1.jar@4, \
reference\:file\:commons-digester-2.0.jar@4, \
reference\:file\:groovy-1.7.0.jar@4, \
reference\:file\:javax.servlet_2.5.0.v200806031605.jar@4, \
reference\:file\:net.sf.jasperreports-3.7.0.jar@4, \
reference\:file\:org.apache.commons.beanutils_1.7.0.v200902170505.jar@4, \
reference\:file\:org.apache.commons.logging_1.0.4.v200904062259.jar@4, \
reference\:file\:org.apache.log4j_1.2.13.v200903072027.jar@4, \
reference\:file\:org.eclipse.core.commands_3.5.0.I20090525-2000.jar@4, \
reference\:file\:org.eclipse.core.contenttype_3.4.1.R35x_v20090826-0451.jar@4, \
reference\:file\:org.eclipse.core.databinding_1.2.0.M20090819-0800.jar@4, \
reference\:file\:org.eclipse.core.databinding.beans_1.2.0.I20090525-2000.jar@4, \
reference\:file\: org.eclipse.core.databinding.observable_1.2.0.M20090902-0800 .jar @4, \
reference\:file\: org.eclipse.core.databinding.property_1.2.0.M20090819-0800.j ar @4, \
reference\:file\:org.eclipse.core.expressions_3.4.101.R35x_v20100209.jar@4, \
reference\:file\:org.eclipse.core.jobs_3.4.100.v20090429-1800.jar@4, \
reference\:file\:org.eclipse.core.runtime_3.5.0.v20090525.jar@4\:start, \
reference\:file\:org.eclipse.core.variables_3.2.200.v20090521.jar@4, \
reference\:file\:org.eclipse.equinox.app_1.2.1.R35x_v20091203.jar@4, \
reference\:file\:org.eclipse.equinox.common_3.5.1.R35x_v20090807-1100.jar@2\:start, \
reference\:file\:org.eclipse.equinox.ds_1.1.1.R35x_v20090806.jar@4\:start, \
reference\:file\:org.eclipse.equinox.log_1.2.0.v20090520-1800.jar@4, \
reference\:file\:org.eclipse.equinox.preferences_3.2.301.R35x_v20091117.jar@4, \
reference\:file\:org.eclipse.equinox.registry_3.4.100.v20090520-1800.jar@4, \
reference\:file\:org.eclipse.equinox.util_1.0.100.v20090520-1800.jar@4, \
reference\:file\:org.eclipse.help_3.4.1.v20090805_35x.jar@4, \
reference\:file\:org.eclipse.jface_3.5.2.M20100120-0800.jar@4, \
reference\:file\:org.eclipse.jface.databinding_1.3.1.M20090826-0800.jar@4, \
reference\:file\:org.eclipse.nebula.widgets.compositetable_1.0.0.jar@4, \
reference\:file\:org.eclipse.osgi.services_3.2.0.v20090520-1800.jar@4, \
reference\:file\:org.eclipse.riena.beans.common_1.2.0.v20091214_1_2_0_0.jar@4, \
reference\:file\:org.eclipse.riena.client_1.2.0.v20091214_1_2_0_0.jar@4, \
reference\:file\: org.eclipse.riena.communication.console_1.2.0.v20091214_1_2_ 0_0.jar @4, \
reference\:file\: org.eclipse.riena.communication.core_1.2.0.v20091214_1_2_0_0 .jar @4, \
reference\:file\: org.eclipse.riena.communication.factory.hessian_1.2.0.v20091 214_1_2_0_0.jar @4, \
reference\:file\:org.eclipse.riena.core_1.2.0.v20091214_1_2_0_0.jar@4, \
reference\:file\:org.eclipse.riena.navigation_1.2.0.v20091214_1_2_0_0.jar@4, \
reference\:file\:org.eclipse.riena.navigation.ui_1.2.0.v20091214_1_2_0_0.jar@4, \
reference\:file\: org.eclipse.riena.navigation.ui.swt_1.2.0.v20091214_1_2_0_0. jar @4, \
reference\:file\: org.eclipse.riena.security.common_2.0.0.v20091214_1_2_0_0.ja r @4, \
reference\:file\:org.eclipse.riena.ui.common_1.2.0.v20091214_1_2_0_0.jar@4, \
reference\:file\:org.eclipse.riena.ui.core_1.2.0.v20091214_1_2_0_0.jar@4, \
reference\:file\:org.eclipse.riena.ui.filter_1.2.0.v20091214_1_2_0_0.jar@4, \
reference\:file\:org.eclipse.riena.ui.ridgets_1.2.0.v20091214_1_2_0_0.jar@4, \
reference\:file\: org.eclipse.riena.ui.ridgets.swt_2.0.0.v20091214_1_2_0_0.jar @4, \
reference\:file\:org.eclipse.riena.ui.swt_1.2.0.v20091214_1_2_0_0.jar@4, \
reference\:file\:org.eclipse.riena.ui.workarea_1.2.0.v20091214_1_2_0_0.jar@4, \
reference\:file\:org.eclipse.swt_3.5.2.v3557f.jar@4, \
reference\:file\:org.eclipse.swt.cocoa.macosx_3.5.2.v3557f.jar@4, \
reference\:file\:org.eclipse.ui_3.5.2.M20100120-0800.jar@4, \
reference\:file\:org.eclipse.ui.workbench_3.5.2.M20100113-0800.jar@4, \
reference\:file\:org.hibernate.client_3.3.1.GA.jar@4
eclipse.application=ch.llb.contact.ui.application
# the default start level is 4
osgi.bundles.defaultStartLevel=4
osgi.framework=file\:plugins/org.eclipse.osgi_3.5.2.R35x_v20 100126.jar
eclipse.product=ch.llb.contact.ui.llb_app_ui_product
osgi.framework.extensions=reference\:file\:org.eclipse.equin ox.transforms.hook_1.0.100.v20090520-1800.jar
eclipse.p2.data.area=@config.dir/../p2/
eclipse.p2.profile=profile
|
|
|
Re: Eclipse RCP app hang on MACOSX 10.6 [message #525679 is a reply to message #525665] |
Wed, 07 April 2010 12:59 |
Ralf Ebert Messages: 168 Registered: July 2009 |
Senior Member |
|
|
Hi,
the missing values for -os, -ws, -arch, -nl in your eclipse.ini look suspicious, are these
really missing or did they get lost when you pasted the contents?
This is the eclipse.ini as created by the PDE Build when exporting for Mac OS X:
-startup
.../../../plugins/org.eclipse.equinox.launcher_1.1.0.v201003 29.jar
--launcher.library
.../../../plugins/org.eclipse.equinox.launcher.cocoa.macosx. x86_64_1.1.0.v20100322-1720
-vmargs
-XstartOnFirstThread
-Dorg.eclipse.swt.internal.carbon.smallFonts
I'm not sure about the "-XstartOnFirstThread", I think this is Carbon-related, on Cocoa
starting works fine even without this argument for me, but it might not hurt to try it.
Greetings,
Ralf
--
http://www.ralfebert.de/blog/
http://twitter.com/ralfebert/
|
|
| |
Re: Eclipse RCP app hang on MACOSX 10.6 [message #525735 is a reply to message #525636] |
Wed, 07 April 2010 15:51 |
Eclipse User |
|
|
|
Originally posted by: cold.phusion.gmail.com
Hi Christian,
is there any specific UI component that you are using? For instance,
custom components, Nebula widgets or Swing code using an AWT bridge?
Keep in mind that the Cocoa implementation of SWT is fairly new and
might be not completely finished.
You could also try out the Carbon version, if 64-bit is not a requirement.
Regards,
Alex
Am 07.04.2010 11:58, schrieb Christian:
> Hello, we have an Eclipse RCP application running perfectly on windows
> but we cannot make it run on MAC OS X (10.6) with Java 6.
> When launching the application in the OSGI console we have:
> [Java CocoaComponent compatibility mode]: Setting timeout for SWT to
> 0.10000
> and the application hangs indefinitely.
> In the OSGI console we can display the status of our ui bundle; it is
> RESOLVED; and if we start it manually, we can see that the bundle
> Activator class is executed but the GUI does not show up.
>
> We tried with Eclipse galileo SR1-cocoa-32 and SR2-cocoa-32; but it
> produce the same result.
>
> - Is there any issue with SWT on Mac OS X ?
> - Why do we have the message "CocoaComponent compatibility mode" ?
> - We are developping with SWT Designer on windows, is there known
> problems on Macosx ?
> - Could you suggest some options we can try ?
>
> Best regards
>
> Christian
|
|
| |
Re: Eclipse RCP app hang on MACOSX 10. 6 [message #526344 is a reply to message #525759] |
Fri, 09 April 2010 17:48 |
Eclipse User |
|
|
|
Originally posted by: cold.phusion.gmail.com
Hi Christian,
if it works fine with Carbon, you can still deploy your application with it. I
don't think the Carbon implementation of SWT would get deprecated before the
next major release of Eclipse (e4).
As for the Nebula widgets - may be not all of them, but the majority hasn't been
updated in a while, so I wouldn't expect them to be compatible with the new
version of SWT. Moreover, depending on the exact implementation, it's not
unusual that they were built only for Windows (In fact, they used to include the
OS compatibility on the top of the page, but I see this has been removed).
I'm not familiar with the specific settings for every Nebula widget, so I can't
tell you how to fix your problem (or if it is at all fixable) - but you can ask
in the Nebula newsgroup, the chaps over there should have some pointers.
Cheers,
Alex
Christian <christian_schatt@hotmail.com> wrote:
> Hi Alex,
>
> Yes we are using the Nebula compositetable widget.
>
> I tried out with the Carbon version and it works.
>
> However some widgets does not behave like on the windows platform: for
instance the calendar widget has no drop down list.
>
> DateTime birthDate = new DateTime(parent, SWT.BORDER | SWT.SINGLE);
>
> Is there some options to get it like on the windows platform ?
>
> Thanks for your help
>
> Christian.
>
|
|
|
Re: Eclipse RCP app hang on MACOSX 10.6 [message #605517 is a reply to message #525665] |
Wed, 07 April 2010 12:59 |
Ralf Ebert Messages: 168 Registered: July 2009 |
Senior Member |
|
|
Hi,
the missing values for -os, -ws, -arch, -nl in your eclipse.ini look suspicious, are these
really missing or did they get lost when you pasted the contents?
This is the eclipse.ini as created by the PDE Build when exporting for Mac OS X:
-startup
.../../../plugins/org.eclipse.equinox.launcher_1.1.0.v201003 29.jar
--launcher.library
.../../../plugins/org.eclipse.equinox.launcher.cocoa.macosx. x86_64_1.1.0.v20100322-1720
-vmargs
-XstartOnFirstThread
-Dorg.eclipse.swt.internal.carbon.smallFonts
I'm not sure about the "-XstartOnFirstThread", I think this is Carbon-related, on Cocoa
starting works fine even without this argument for me, but it might not hurt to try it.
Greetings,
Ralf
--
http://www.ralfebert.de/blog/
http://twitter.com/ralfebert/
|
|
| | |
Re: Eclipse RCP app hang on MACOSX 10. 6 [message #605558 is a reply to message #605534] |
Fri, 09 April 2010 17:48 |
Alex Shterev Messages: 20 Registered: April 2010 |
Junior Member |
|
|
Hi Christian,
if it works fine with Carbon, you can still deploy your application with it. I
don't think the Carbon implementation of SWT would get deprecated before the
next major release of Eclipse (e4).
As for the Nebula widgets - may be not all of them, but the majority hasn't been
updated in a while, so I wouldn't expect them to be compatible with the new
version of SWT. Moreover, depending on the exact implementation, it's not
unusual that they were built only for Windows (In fact, they used to include the
OS compatibility on the top of the page, but I see this has been removed).
I'm not familiar with the specific settings for every Nebula widget, so I can't
tell you how to fix your problem (or if it is at all fixable) - but you can ask
in the Nebula newsgroup, the chaps over there should have some pointers.
Cheers,
Alex
Christian <christian_schatt@hotmail.com> wrote:
> Hi Alex,
>
> Yes we are using the Nebula compositetable widget.
>
> I tried out with the Carbon version and it works.
>
> However some widgets does not behave like on the windows platform: for
instance the calendar widget has no drop down list.
>
> DateTime birthDate = new DateTime(parent, SWT.BORDER | SWT.SINGLE);
>
> Is there some options to get it like on the windows platform ?
>
> Thanks for your help
>
> Christian.
>
|
|
|
Goto Forum:
Current Time: Tue Sep 24 04:34:02 GMT 2024
Powered by FUDForum. Page generated in 0.05824 seconds
|