Re: [equinox-dev] Accessing the log without Activator (extendsPlugin)
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 Activator (extendsPlugin) 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 latter, then you can use a DS component and just inject a reference to the LogService. If you really need ILog then I think you have to go through InternalPlatform.getDefault().getLog(). Neil > On 7 Oct 2015, at 09:38, Lars Vogel wrote: > > 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 > > Haindaalwisch 17a, 22395 Hamburg > Amtsgericht Hamburg: HRB 127058 > Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel > USt-IdNr.: DE284122352 > Fax (032) 221739404, Email: lars.vo...@vogella.com, Web: > http://www.vogella.com > ___ > equinox-dev mailing list > equinox-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] Missing download artifacts for Equinox Mars M4
It looks like Equinox Mars M4 build is missing various artifacts that should be in the build, such as the equinox-SDK-MarsM4.zip file. This is blocking some projects from being able to move to M4 and contribute to M4. http://download.eclipse.org/equinox/drops/S-MarsM4-201412102000/index.php Thanks, - Konstantin ___ equinox-dev mailing list equinox-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] Composite repository entry that does not bring in categories
Sending this question to the dev mailing list since I didn't get any response on the forum and other channels. Would appreciate a response, even if it's of the "we can't do that right now" nature. We need to add an entry to a p2 composite repository that does not merge the feature categorization from the referenced repository. Basically, we need to content of the repo to be accessible for dependency resolution, but not present to the user of the composite for selection. Is that possible? Thanks, - Konstantin ___ equinox-dev mailing list equinox-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] org.eclipse.osgi.framework.debug.FrameworkDebugOptions
Thanks for the follow-up, Thomas. I think another reminder of Equinox changes might be in order on cross-project. I notice that some Luna projects (not going to name the guilty parties) with dependencies on Equinox internals have yet to try building with Luna platform. I expect lots of surprised and angry reactions in about a week. Thanks, - Konstantin From: equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] On Behalf Of Thomas Watson Sent: Friday, August 09, 2013 8:53 AM To: Equinox development mailing list Subject: Re: [equinox-dev] org.eclipse.osgi.framework.debug.FrameworkDebugOptions David's answer is correct. Thanks David! FrameworkDebugOptions is not API, the Equinox API (not OSGi API!) is org.eclipse.osgi.service.debug.DebugOptions. As David mentions, this is intended to be consumed as an OSGi service and Equinox does not provide static API to access it. the Platform.getDebugOption method does provide static access to the debug options service if that is what you would prefer to use. But I still recommend using the OSGi service directly instead of using the old org.eclipse.core.runtime.Platform class, but that is because I really dislike static APIs and I am used to using the OSGi service registry for such things. Tom Inactive hide details for "Konstantin Komissarchik" ---08/06/2013 04:45:34 PM---Thanks, David."Konstantin Komissarchik" ---08/06/2013 04:45:34 PM---Thanks, David. From: "Konstantin Komissarchik" To: "'Equinox development mailing list'" , Date: 08/06/2013 04:45 PM Subject: Re: [equinox-dev] org.eclipse.osgi.framework.debug.FrameworkDebugOptions Sent by: equinox-dev-boun...@eclipse.org _ Thanks, David. I found that I can replace FrameworkDebugOptions.getDefault().getBooleanOption(key) with Platform.getDebugOption(key). - Konstantin From: equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] On Behalf Of David M Williams Sent: Monday, August 05, 2013 11:03 PM To: Equinox development mailing list Subject: Re: [equinox-dev] org.eclipse.osgi.framework.debug.FrameworkDebugOptions Tom (and the one or two others who might know) are not available this week so ... just so that you do not feel ignored :) I'll respond with the tiny bit I know, and Tom can later address deeper if needed. Short answer: I believe it is intended to be gone ... but I don't what to recommend on "how to transition". The previous version, in package org.eclipse.osgi.framework.debug, was marked as "x-internal" in MANIFEST.MF (meaning, was not API, even though did not have internal in the package name). There is a new version of FrameworkDebugOptions, now in a package with 'internal' in the name, org.eclipse.osgi.internal.debug, which, off hand, ... from the most casual of skim reading ... appears to be intended to be used more as a service, not by direct (non-API) reference. Tom has been working hard re-implementing a large amount of "Equinox internals" for some time (in anticipation of new specs) and while I didn't see 'debug' mentioned explicitly, there is a lot written about the changes at <http://wiki.eclipse.org/Equinox/Luna_Framework> http://wiki.eclipse.org/Equinox/Luna_Framework and that wiki page in turn points to various specs and other specific bugs which might help you migrate off the non-API class. Hope this helps ... but if if not, ask again in a week or two and I'm sure Tom can say more. Thanks, From:"Konstantin Komissarchik" < <mailto:konstantin.komissarc...@oracle.com> konstantin.komissarc...@oracle.com> To:"'Equinox development mailing list'" < <mailto:equinox-dev@eclipse.org> equinox-dev@eclipse.org>, Date:08/06/2013 12:47 AM Subject:Re: [equinox-dev] org.eclipse.osgi.framework.debug.FrameworkDebugOptions Sent by: <mailto:equinox-dev-boun...@eclipse.org> equinox-dev-boun...@eclipse.org _ Does anyone have any thoughts on this issue? I am assuming that this is result of recent refactoring. The package in question doesn’t have internal in the name, but if the class is going away for good, could someone let me know what the equivalent invocation should be? Thanks, - Konstantin From: <mailto:equinox-dev-boun...@eclipse.org> equinox-dev-boun...@eclipse.org [ <mailto:equinox-dev-boun...@eclipse.org> mailto:equinox-dev-boun...@eclipse.org] On Behalf Of Konstantin Komissarchik Sent: Friday, August 02, 2013 5:03 PM To: <mailto:equinox-dev@eclipse.org> equinox-dev@eclipse.org Subject: [equinox-dev] org.eclipse.osgi.framework.debug.FrameworkDebugOptions In the process of migrating Oracle Enterprise Pack for Eclipse to the latest Luna integration build, I have disc
Re: [equinox-dev] org.eclipse.osgi.framework.debug.FrameworkDebugOptions
Thanks, David. I found that I can replace FrameworkDebugOptions.getDefault().getBooleanOption(key) with Platform.getDebugOption(key). - Konstantin From: equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] On Behalf Of David M Williams Sent: Monday, August 05, 2013 11:03 PM To: Equinox development mailing list Subject: Re: [equinox-dev] org.eclipse.osgi.framework.debug.FrameworkDebugOptions Tom (and the one or two others who might know) are not available this week so ... just so that you do not feel ignored :) I'll respond with the tiny bit I know, and Tom can later address deeper if needed. Short answer: I believe it is intended to be gone ... but I don't what to recommend on "how to transition". The previous version, in package org.eclipse.osgi.framework.debug, was marked as "x-internal" in MANIFEST.MF (meaning, was not API, even though did not have internal in the package name). There is a new version of FrameworkDebugOptions, now in a package with 'internal' in the name, org.eclipse.osgi.internal.debug, which, off hand, ... from the most casual of skim reading ... appears to be intended to be used more as a service, not by direct (non-API) reference. Tom has been working hard re-implementing a large amount of "Equinox internals" for some time (in anticipation of new specs) and while I didn't see 'debug' mentioned explicitly, there is a lot written about the changes at <http://wiki.eclipse.org/Equinox/Luna_Framework> http://wiki.eclipse.org/Equinox/Luna_Framework and that wiki page in turn points to various specs and other specific bugs which might help you migrate off the non-API class. Hope this helps ... but if if not, ask again in a week or two and I'm sure Tom can say more. Thanks, From:"Konstantin Komissarchik" To:"'Equinox development mailing list'" , Date:08/06/2013 12:47 AM Subject:Re: [equinox-dev] org.eclipse.osgi.framework.debug.FrameworkDebugOptions Sent by:equinox-dev-boun...@eclipse.org _ Does anyone have any thoughts on this issue? I am assuming that this is result of recent refactoring. The package in question doesn’t have internal in the name, but if the class is going away for good, could someone let me know what the equivalent invocation should be? Thanks, - Konstantin From: equinox-dev-boun...@eclipse.org [ <mailto:equinox-dev-boun...@eclipse.org> mailto:equinox-dev-boun...@eclipse.org] On Behalf Of Konstantin Komissarchik Sent: Friday, August 02, 2013 5:03 PM To: equinox-dev@eclipse.org Subject: [equinox-dev] org.eclipse.osgi.framework.debug.FrameworkDebugOptions In the process of migrating Oracle Enterprise Pack for Eclipse to the latest Luna integration build, I have discovered that FrameworkDebugOptions class seems to be missing. Thoughts? Thanks, - Konstantin [java] [javac] 1. ERROR in D:\Oracle\OEPE\Depot\trunk\luna\plugins\oracle.eclipse.tools.xml.model\src\oracle\ec ipse\tools\xml\model\TraceOptions.java (at line 6) [java] [javac] import org.eclipse.osgi.framework.debug.FrameworkDebugOptions; [java] [javac] [java] [javac] The import org.eclipse.osgi.framework.debug cannot be resolved [java] [javac] -- [java] [javac] 2. ERROR in D:\Oracle\OEPE\Depot\trunk\luna\plugins\oracle.eclipse.tools.xml.model\src\oracle\ec ipse\tools\xml\model\TraceOptions.java (at line 36) [java] [javac] final DebugOptions debugOptions = FrameworkDebugOptions.getDefault(); [java] [javac] ^ [java] [javac] FrameworkDebugOptions cannot be resolved [java] [javac] -- [java] [javac] 2 problems (2 errors)___ equinox-dev mailing list equinox-dev@eclipse.org <https://dev.eclipse.org/mailman/listinfo/equinox-dev> https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] org.eclipse.osgi.framework.debug.FrameworkDebugOptions
Does anyone have any thoughts on this issue? I am assuming that this is result of recent refactoring. The package in question doesn't have internal in the name, but if the class is going away for good, could someone let me know what the equivalent invocation should be? Thanks, - Konstantin From: equinox-dev-boun...@eclipse.org [mailto:equinox-dev-boun...@eclipse.org] On Behalf Of Konstantin Komissarchik Sent: Friday, August 02, 2013 5:03 PM To: equinox-dev@eclipse.org Subject: [equinox-dev] org.eclipse.osgi.framework.debug.FrameworkDebugOptions In the process of migrating Oracle Enterprise Pack for Eclipse to the latest Luna integration build, I have discovered that FrameworkDebugOptions class seems to be missing. Thoughts? Thanks, - Konstantin [java] [javac] 1. ERROR in D:\Oracle\OEPE\Depot\trunk\luna\plugins\oracle.eclipse.tools.xml.model\src\o racle\ec ipse\tools\xml\model\TraceOptions.java (at line 6) [java] [javac] import org.eclipse.osgi.framework.debug.FrameworkDebugOptions; [java] [javac] [java] [javac] The import org.eclipse.osgi.framework.debug cannot be resolved [java] [javac] -- [java] [javac] 2. ERROR in D:\Oracle\OEPE\Depot\trunk\luna\plugins\oracle.eclipse.tools.xml.model\src\o racle\ec ipse\tools\xml\model\TraceOptions.java (at line 36) [java] [javac] final DebugOptions debugOptions = FrameworkDebugOptions.getDefault(); [java] [javac] ^ [java] [javac] FrameworkDebugOptions cannot be resolved [java] [javac] -- [java] [javac] 2 problems (2 errors) ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] org.eclipse.osgi.framework.debug.FrameworkDebugOptions
In the process of migrating Oracle Enterprise Pack for Eclipse to the latest Luna integration build, I have discovered that FrameworkDebugOptions class seems to be missing. Thoughts? Thanks, - Konstantin [java] [javac] 1. ERROR in D:\Oracle\OEPE\Depot\trunk\luna\plugins\oracle.eclipse.tools.xml.model\src\o racle\ec ipse\tools\xml\model\TraceOptions.java (at line 6) [java] [javac] import org.eclipse.osgi.framework.debug.FrameworkDebugOptions; [java] [javac] [java] [javac] The import org.eclipse.osgi.framework.debug cannot be resolved [java] [javac] -- [java] [javac] 2. ERROR in D:\Oracle\OEPE\Depot\trunk\luna\plugins\oracle.eclipse.tools.xml.model\src\o racle\ec ipse\tools\xml\model\TraceOptions.java (at line 36) [java] [javac] final DebugOptions debugOptions = FrameworkDebugOptions.getDefault(); [java] [javac] ^ [java] [javac] FrameworkDebugOptions cannot be resolved [java] [javac] -- [java] [javac] 2 problems (2 errors) ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
