[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [equinox-dev] New version of Equinox quits upon bundle error

 
Ah! Thank you. Your hints helped me solved my problems. Much appreciated!
 
 
Cheers,
David
 
 
 
-----Original Message-----
From: equinox-dev-bounces@xxxxxxxxxxx [mailto:equinox-dev-bounces@xxxxxxxxxxx]On Behalf Of Patrick Dempsey
Sent: 2 May 2008 13:00
To: Equinox development mailing list
Subject: Re: [equinox-dev] New version of Equinox quits upon bundle error

David,

When running simple osgi programs under equinox you probably just want to use the following two vm options
-Declipse.ignoreApp=true -Dosgi.noShutdown=true
These are the default options that appear in a new OSGi Framework launch config. These options were not in eclipse 3.3 launch configs (so if you are trying to use old launch configs this may be the problem) These are also the options that make it so that you don't need to use an Eclipse Application. These should also make it so that all you need to start the framework is org.eclipse.osgi.jar

The -noExit option is not a VM option but rather a Program argument and you would put it next to the options like -console
It has the same effect as the -Dosgi.noShutdown=true VM argument

Patrick
P.S.As a note to a new Mac user, if your applications have ui's you may (more likely will <g>) have problems with swt. There are issues related to which thread is the display thread.
On May 1, 2008, at 11:20 PM, David Leangen wrote:
Thank you, Tom,
While looking into this a little more, I discovered that this probably isn't a regression issue after all.
I recently moved over to Mac, so I've been trying to get set up on my new machine. This has not been easy. :-(
The behaviour I described below is the same on 3.4M3 and 3.4M6.
Is there someplace I can get a list of the differences between how Eclipse is set up to run out of the box on Mac as opposed to Linux? They are obviously not the same, and I haven't had any luck yet finding such info.
Thank you!
David
-----Original Message-----
From: equinox-dev-bounces@xxxxxxxxxxx [mailto:equinox-dev-bounces@xxxxxxxxxxx]On Behalf Of Thomas Watson
Sent: 1 May 2008 23:29
To: Equinox development mailing list
Subject: RE: [equinox-dev] New version of Equinox quits upon bundle error

More information is needed on how you are launching Equinox, including what bundles you are using and what config.ini options etc. Also, what version of Eclipse you are migrating from where your application worked. Lets move this discussion into a bug report. If you have an application that used to work in 3.2-3.3 and now does not work in 3.4 then that is the bug you should open with a description of how to reproduce or even better would be a testcase for us to reproduce. I would open that bug against Equinox->Bundles

In 3.3 we split the application container out of org.eclipse.core.runtime into org.eclipse.equinox.app. You must include the org.eclipse.equinox.app bundle in your configuration to use the Eclipse application container.

Hope we can help you out.

Tom



<graycol.gif>"David Leangen" ---05/01/2008 09:06:01 AM---Thank you, Tom,

<ecblank.gif>
From:
<ecblank.gif>
"David Leangen" <osgi@xxxxxxxxxxx>
<ecblank.gif>
To:
<ecblank.gif>
"Equinox development mailing list" <equinox-dev@xxxxxxxxxxx>
<ecblank.gif>
Date:
<ecblank.gif>
05/01/2008 09:06 AM
<ecblank.gif>
Subject:
<ecblank.gif>
RE: [equinox-dev] New version of Equinox quits upon bundle error






Thank you, Tom,

What would the bug be, then? "Running in console requires
org.eclipse.equinox.core.runtime"? It is my understanding that only the osgi
package should be required.


BTW, when I add the -noExit option, I get an error (Unrecognized option). Is
that really a valid option?


Regards,
David


-----Original Message-----
From: equinox-dev-bounces@xxxxxxxxxxx
[
mailto:equinox-dev-bounces@xxxxxxxxxxx]On Behalf Of Thomas Watson
Sent: 1 May 2008 22:17
To: Equinox development mailing list
Subject: Re: [equinox-dev] New version of Equinox quits upon bundle error


Please open a bug if you think you have found a regression. In the bug
report please give steps to reproduce. Thanks.

If you launch with the option command line option -noExit that should help
keep the framework running when the application fails.

Tom



"David Leangen" ---05/01/2008 02:30:03 AM---Hello!


From:
"David Leangen" <osgi@xxxxxxxxxxx>

To:
<equinox-dev@xxxxxxxxxxx>

Date:
05/01/2008 02:30 AM

Subject:
[equinox-dev] New version of Equinox quits upon bundle error







Hello!

I recently updated to 3.4M6, which IIUC is the most recent release.

I run my apps in the Eclipse console because it is great for debugging.
However, with this version, when one of my bundles has an error, everything
shuts down with a message "The Application could not start...".


How can I get the console to work like before and just run with the
erroneous bundles in a RESOLVED state so I can debug the problems?


BTW, the error logs are complaining that I need
org.eclipse.equinox.core.runtime installed. I don't mind installing one
bundle, but that bundle has lots of dependencies that I don't want.

I never needed this before... so what's changed?



Thank you!
David


_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev

_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev

<graycol.gif><ecblank.gif>
_______________________________________________
equinox-dev mailing list