Congratulations Stefan!
Am 08.10.2015 6:02 vorm. schrieb "portal on behalf of" <
portal-nore...@eclipse.org>:
> rt.equinox.bundles Committers,
> This automatically generated message marks the successful completion of
> voting for Stefan Xenos to receive full Committer status on the
> rt.equinox.bu
rt.equinox.bundles Committers,
This automatically generated message marks the successful completion of
voting for Stefan Xenos to receive full Committer status on the
rt.equinox.bundles project. The next step is for the PMC to approve this
vote, followed by the EMO processing the paperwork and prov
The Bug, which has been reverted is
https://bugs.eclipse.org/bugs/show_bug.cgi?id=473845
Thanks for your help, Tom.
Regards,
Simon
On 07.10.2015 19:53, Thomas Watson wrote:
What is the bug number where the revert happened and we can discuss
the alternatives?
If you want to avoid lazy acti
What is the bug number where the revert happened and we can discuss the
alternatives?
If you want to avoid lazy activation of the bundle then we have to avoid
actually loading the class in the check. I think you may be able to try
locating the .class resource instead of actually trying to load
ILog has been around for a very long time, before OSGi as a runtime in
Eclipse I think. So its access is a bit static. If you have motivation
to access it in an 'OSGi way' then I recommend you enhance the eclipse
platform to register a ServiceFactory that bundles can use. The
ServiceFactory
Here is the invocation that I use to get ILog without an Activator:
Platform.getLog( Platform.getBundle( "..." ) )
Thanks,
- Konstantin
From: Neil Bartlett
Sent: Wednesday, October 7, 2015 8:50 AM
To: Equinox development mailing list
Subject: Re: [equinox-dev] Accessing the log without Activ
Looking at the source code, ILog is not an OSGi service but is constructed as a
wrapper object around the OSGi LogService. The relevant code is in
org.eclipse.core.internal.runtime.InternalPlatform.
Do you need the full functionality of an ILog, or is standard OSGi LogService
sufficient? If the
> On 7 Oct 2015, at 09:24, Lars Vogel wrote:
>
> Thanks Neil.
>
> So to summaries: without the "lazy" flag my activator is only started
> if I do this explicit, i.e., it is not started without my code.
Technically, OSGi never starts a bundle unless somebody calls the
Bundle.start() method. In
Hello,
we are currently facing problems, when trying to figure out if a class
is available in the target platform or not.
So in case certain bundles are removed from the target platform the E4
application model should be cleaned up accordingly, which means that
referenced model objects, should
Hi,
in my Activator based on Plugin, I have this nice method:
MyActivator.getDefault().getLog() which is basically Plugin.getLog().
What is the correct way to access the ILog in OSGi without an Activator?
Best regards, Lars
--
Eclipse Platform UI and e4 project co-lead
CEO vogella GmbH
Haind
Thanks Neil.
So to summaries: without the "lazy" flag my activator is only started
if I do this explicit, i.e., it is not started without my code. So to
ensure the Activator runs, the flag is needed. (Unless I would start
the bundles somewhere in my code).
Best regards, Lars
On Wed, Oct 7, 2015
It depends what you want to achieve.
If you want the activator to run lazily, only when a class is loaded from the
bundle for some other reason (eg because it contributes an extension) then that
is exactly what BAP:lazy does.
If you don't have that class loading trigger, then you will have to
Hi,
I have a plug-in with an activator. It also sets the
Bundle-ActivationPolicy: lazy policy set, even though it provides no
declarative services nor any others services.
id State Bundle
208 ACTIVE org.eclipse.ui.cheatsheets_3.4.200.N20151006-2000
osgi> services 208
"No registered ser
13 matches
Mail list logo
