Re: [equinox-dev] JAXB with Java 11 in OSGi

IIRC you need to set the thread-context-classloader! Try that: ---8<--- ClassLoader cl = Thread.currentThread().getContextClassLoader(); try { ClassLoader tmp = Bookstore.class.getClassLoader() Thread.currentThread().setContextClassLoader(tmp); context =

[equinox-dev] Where is the launcher source-code?

Hi, I've filed https://bugs.eclipse.org/bugs/show_bug.cgi?id=495783 and now I wanted to look myself into the launcher code but i'm unable to find it. http://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/bundles/org.eclipse.equinox.launcher.cocoa.macosx.x86_64 is empty and

Re: [equinox-dev] OSGiServiceSupplier

Alex, What about this: > public class OSGiServiceWrapper { > private BundleContext ctx; > private BundleContext context; > private Class serviceType; > > public OSGiServiceWrapper(Class requestor, Class serviceType) { > this.context = >

Re: [equinox-dev] OSGiServiceSupplier

oid main(String[] args) { > OSGiServiceWrapper options = > OSGiServiceWrapper.create(OSGiServiceWrapper.class, DebugOptions.class); > Function<String, Boolean> f = options.createFunction( (o,s) -> { > return s.getBooleanOption(o

Re: [equinox-dev] Unable to resolve apache mina with jdk1.8

The resolve error for javax.* from the jre/ee is a bug in the pde target platform dialog or better in the way it uses p2. I have forgot the bug id. Tom Von meinem iPhone gesendet > Am 15.09.2015 um 02:31 schrieb John W Ross : > > If you're doing this by adding an Orbit

Re: [equinox-dev] Eclipse 4.5 RC2 and Equinox (Mars RC2) is available for download

Hi David and p2-devs, Starting with the latest mars-RC repo it looks like org.eclipse.equinox.p2.ql.source is NOT available anymore! Does anyone know why? Tom On 22.05.15 23:00, David M Williams wrote: It is my pleasure to announce that Mars RC2 is available from the Eclipse Platform Project.

Re: [equinox-dev] dependency on org.osgi.annotation?

PDE can have compile time dependencies in its build.properties but naturally build.properties is not part of the final jar Tom Von meinem iPhone gesendet Am 09.05.2015 um 00:52 schrieb Stephan Herrmann stephan.herrm...@berlin.de: I'm not responding to any of that religious anti-PDE flame

Re: [equinox-dev] Eclipse won't work on JDK9b61 unless default classloader hiearchy is changed

a therefore allow the framework to export the packages from ext can probably change. Tom From:Tom Schindl tom.schi...@bestsolution.at To:Equinox development mailing list equinox-dev@eclipse.org, platform-ui-...@eclipse.org Date:05/05/2015 04:12 AM Subject

Re: [equinox-dev] Eclipse won't work on JDK9b61 unless default classloader hiearchy is changed

Hi, On 05.05.15 16:05, Thomas Watson wrote: Please open a bug to track the issues. I assume you are having to set the configuration property osgi.frameworkParentClassloader=ext to get this to work on Java 9? Yes I still believe the default 'parent' class loader for bundles should be

Re: [equinox-dev] Eclipse won't work on JDK9b61 unless default classloader hiearchy is changed

Hi, [...] But you mention that using the boot class loader as the parent class loader for bundle class loaders causes problems for Nashorn. I fail to see why that is. I don't know the inner details but if you run this app package samplenashornosgi; import javax.script.ScriptEngine;

[equinox-dev] Eclipse won't work on JDK9b61 unless default classloader hiearchy is changed

Hi, Starting with b61 org.w3c.dom.** classes have been moved to * app classpath in b61 * ext classpath in b62 Isn't it time to throw out this none standard class lookup strategy and use at least ext. https://bugs.openjdk.java.net/browse/JDK-8042244

Re: [equinox-dev] [eclipse-dev] Announcing Eclipse 4.5 M6 and Luna (Mars M6) with a caution for Mac Users

I have to correct myself, p2-director works fine but naturally one has to adjust the call for the p2 director now, pointing to the Eclipse.app/Contents/Eclipse dir. Sorry Tom On 22.03.15 22:41, Tom Schindl wrote: Hi, It looks like the OS-X changes broke installing stuff headless. I'm

Re: [equinox-dev] Huge performance loss between Kepler and Luna/Mars on first start

Von meinem iPhone gesendet Am 20.02.2015 um 21:30 schrieb Thomas Watson tjwat...@us.ibm.com: From: Tom Schindl tom.schi...@bestsolution.at Hi, I've been with a customer today who wants to update from Eclipse 3.x Kepler to the 4.x code base and so he naturally inherits

[equinox-dev] Huge performance loss between Kepler and Luna/Mars on first start

Hi, I've been with a customer today who wants to update from Eclipse 3.x Kepler to the 4.x code base and so he naturally inherits the latest Equinox implementation who has changed in between those releases. The intial boot time increased from about 2 seconds to ~20 seconds on Mars (on Luna

Re: [equinox-dev] [e4-dev] Resolver Problem with guava and e4 (javax.annotation)

On 11.06.14 08:07, David M Williams wrote: My main question is ... is this required for Luna? (I assume not, that it shows up in e4 incubator? so could wait to SR1 if we find a safe, non-breaking change? Or Mars if breaking?) No I don't think we can fix the problem in Luna at all. Second,

[equinox-dev] Resolver Problem with guava and e4 (javax.annotation)

Hi, [cross posting because different projects are involved in the problem] I've just discover a problem when one tries to use e4-DI and com.google.guava 15.0.0. The MANIFEST.MF is really simply: Manifest-Version: 1.0 Bundle-ManifestVersion: 2 Bundle-Name: Problem Bundle-SymbolicName:

Re: [equinox-dev] Resolver Problem with guava and e4 (javax.annotation)

On 11.06.14 00:44, Neil Bartlett wrote: a) Removing the javax.annotation import would surely not work, since then you won’t have any visibility of that package at all. I assume resolver.problem does actually use this package? My proposal was not to remove it but to make it version less but

Re: [equinox-dev] Serious problems with EE Java 1.8 (and EE resolving in general) on Luna

...@us.ibm.com_ mailto:hargr...@us.ibm.com office: +1 386 848 1781 mobile: +1 386 848 3788 From:Tom Schindl tom.schi...@bestsolution.at To:equinox-dev@eclipse.org Date:2014/04/09 08:16 Subject:[equinox-dev] Serious problems with EE Java

[equinox-dev] Serious problems with EE Java 1.8 (and EE resolving in general) on Luna

Hi, I'm encountering strange problems with Luna M6 and EE 1.8. The scenario is like this: We provide a prebuilt distro where bundles require an EE of 1.8 if I download this distro and launch the IDE with a JDK 1.7 naturally those bundles do not resolve but stay in the INSTALLED state and a diag

Re: [equinox-dev] Simpler JavaFX class loading

This is not an option how would you make this work when installing through p2 you need to modify the launch parameters of the framework which is fine a single vendor env but not in a multi-vendor one like Eclipse. Other things: * repackage is not possible (legally) * repackage is not feasable

[equinox-dev] Stability of the New AdaptorHook API

Hi, I've already tried to port the e(fx)clipse AdapterHooks for JavaFX to the new AdaptorHook API provided as part of Luna (and succeeded!) but it looks like this API is still in the flux. Can I expect it to be stableized so that I can expect it to not get broken no more - I know the API-freeze

Re: [equinox-dev] IApplicationContext#applicationRunning needs to be called on the main thread?!?

Hi, I never got an answer to this, I would really appreciate any pointers. Tom On 31.10.13 16:39, Tom Schindl wrote: Hi, After having debugged now for some hours why the native splash screen in JavaFX-OSGi-Applications is not take down when IApplicationContext#applicationRunning is called

Re: [equinox-dev] IApplicationContext#applicationRunning needs to be called on the main thread?!?

then it should be documented somewhere. Do you know if this is only an issue on Windows or all platforms? I suggest you open a separate bug against the Equinox launcher. Tom Inactive hide details for Tom Schindl ---12/18/2013 02:11:30 PM---Hi, I never got an answer to this, I would really

Re: [equinox-dev] IApplicationContext#applicationRunning needs to be called on the main thread?!?

[1] http://msdn.microsoft.com/en-us/library/windows/desktop/ms632682%28v=vs.85%29.aspx Inactive hide details for Tom Schindl ---12/18/2013 03:00:00 PM---I've tested it on os-x, will open bugs. TomTom Schindl ---12/18/2013 03:00:00 PM---I've tested it on os-x, will open bugs. Tom From: Tom

[equinox-dev] IApplicationContext#applicationRunning needs to be called on the main thread?!?

Hi, After having debugged now for some hours why the native splash screen in JavaFX-OSGi-Applications is not take down when IApplicationContext#applicationRunning is called [1] I found out that this call does not work if your application is configured to be launched on any-thread (in contrast to

[equinox-dev] [p2] IPlanner and package imports from JRE

to have EE informations for this, right? Tom -- B e s t S o l u t i o n . a tEDV Systemhaus GmbH tom schindl geschäftsführer/CEO

Re: [equinox-dev] [p2] IPlanner and package imports from JRE

under the name a.jre. Also if you use the mirroring application this IU should be brought in. HTH Pascal On 2013-02-01, at 6:08 AM, Tom Schindl wrote: Hi, Yesterday in the night I tried to understand why IPlanner reports an error when a bundle does a package import coming from

Re: [equinox-dev] Equinox, PDE and packages from the ExtensionClasspath (e.g. JavaFX)

tom schindl geschäftsführer/CEO eduard-bodem-gasse 5-7/1 A-6020 innsbruck fax ++43 512 935833 http://www.BestSolution.at phone++43 512

Re: [equinox-dev] Java8 and JavaFX8

the runtime integration works I can go to PDE and provide them patches so that things also work with PDE. Tom -- B e s t S o l u t i o n . a tEDV Systemhaus GmbH tom schindl geschäftsführer

[equinox-dev] Java8 and JavaFX8

the problem at the runtime layer we can go the next step to tweak PDE in a way that it we can work with it. Tom -- B e s t S o l u t i o n . a tEDV Systemhaus GmbH tom schindl

Re: [equinox-dev] Java8 and JavaFX8

. This should allow the system bundle to export the packages available on the extension class path. Tom graycol.gifTom Schindl ---11/06/2012 12:42:54 PM---Hi, To integrate JavaFX2 into Java7 I had to reside to nasty stuff like From: Tom Schindl tom.schi...@bestsolution.at To: equinox

Re: [equinox-dev] Java8 and JavaFX8

+1.613.220.3223 -Original Message- From: Tom Schindl tom.schi...@bestsolution.at Sender: equinox-dev-boun...@eclipse.org Date: Tue, 6 Nov 2012 20:58:36 To: Equinox development mailing listequinox-dev@eclipse.org Reply-To: Equinox development mailing list equinox-dev@eclipse.org Subject: Re

Re: [equinox-dev] Java8 and JavaFX8

to make the use of the extension class loader and export the javafx package. I can think of some other rather nasty hacks that could be done by using equinox framework hooks. But I would like to avoid such hacks. Tom Inactive hide details for Tom Schindl ---11/06/2012 01:59:27 PM---For RCP