your bundle threads.
Yes, that is what I did. Sorry again.
regards,
Karl
> Tom
>
>
>
> "Karl Pauls" ---03/11/2008 05:14:20 PM---> Hi Karl,
>
>
>
>
> From:
> "Karl Pauls" <[EMAIL PROTECTED]>
>
> To:
> "Equino
Date: 03/11/2008 05:14 PM
Subject:Re: [equinox-dev] equinox standalone problem
> Hi Karl,
>
> You are running into bug
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=215730
:
> > Hi Karl,
> >
> > You are running into bug
> > https://bugs.eclipse.org/bugs/show_bug.cgi?id=215730
>
> :-)
>
> > With 3.4 M5 you can set the configuration property
> > osgi.framework.activeThreadType=normal to force a non-daemon thread be
> > started so that the VM does not exit when t
> Hi Karl,
>
> You are running into bug
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=215730
:-)
> With 3.4 M5 you can set the configuration property
> osgi.framework.activeThreadType=normal to force a non-daemon thread be
> started so that the VM does not exit when the framework is running.
Hi Karl,
You are running into bug
https://bugs.eclipse.org/bugs/show_bug.cgi?id=215730
With 3.4 M5 you can set the configuration property
osgi.framework.activeThreadType=normal to force a non-daemon thread be
started so that the VM does not exit when the framework is running. The
reason you see
Greetings Karl,
When you supply a port for the console (osgi.console=), or allow it
to use the default one with the -console switch, OSGi has something
other than the framework to start and run. What you need is an OSGi
"application" which becomes the job for which OSGi was started. The
Coro
