if i delete the framework.info.X (x is 4 in my situation now but i have seen that changed a lot) then it works fine, But i think that just means it doesn't find anything because that is kind of the index of that directory structure. (i see a lot of dir then created)
On Wed, 4 Dec 2019 at 16:28, Johan Compagner <[email protected]> wrote: > bundles seems to be correct > > > org.eclipse.core.runtime,3.15.300.v20190508-0543,plugins/org.eclipse.core.runtime_3.15.300.v20190508-0543.jar,4,true > > it has that line and only that line > > It does try to activate it problem is that the activation (or loading the > activator class) results in loading other stuff that ends up again in thate > core.runtime.. > > > ad the moment i rename this dir in the configuration dir: org.eclipse.osgi > > it works. > > > On Wed, 4 Dec 2019 at 16:16, Thomas Watson <[email protected]> wrote: > >> Please open a bug report with details from this thread against p2 at >> https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Equinox >> >> Then we can continue discussion there. The >> bundle org.eclipse.core.runtime is not typically configured by p2 to >> be lazily activated. There is a bundles.info file located in the >> configuration folder ( >> configuration/org.eclipse.equinox.simpleconfigurator/bundles.info). It >> should have a line that looks something like this: >> >> >> org.eclipse.core.runtime,3.17.0.v20191106-1738,plugins/org.eclipse.core.runtime_3.17.0.v20191106-1738.jar,4,true >> >> It is possible that p2 got confused and either has multiple versions >> of org.eclipse.core.runtime configured or configured incorrectly? >> >> Tom >> >> >> >> ----- Original message ----- >> From: Johan Compagner <[email protected]> >> Sent by: [email protected] >> To: P2 developer discussions <[email protected]> >> Cc: >> Subject: [EXTERNAL] Re: [p2-dev] anybody knows why an upgrade of our >> product (but not an eclipse upgrade) goes wrong like this? >> Date: Wed, Dec 4, 2019 8:53 AM >> >> yes that is the problem >> start is not hit for me, it comes directly in getBundles() >> >> the thing is how is that possible? because InternalPlatform is in >> org.eclipse.core.runtime >> and that plugin has a Activator and Bundle-ActivationPolicy: lazy (which >> i think in the ui stands for "activate this plugin if one of its classes is >> loaded" >> >> any good place where i can place a breakpoint? >> >> >> >> On Wed, 4 Dec 2019 at 14:57, Thomas Watson <[email protected]> wrote: >> >> My guess is that org.eclipse.core.runtime isn't getting activated at all >> or is failing to activate resulting in a null fwkWiring. Although I would >> have expected some other exception in the log about failing to activate >> the org.eclipse.core.runtime bundle. If you are able to debug check that >> the org.eclipse.core.internal.runtime.InternalPlatform.start(BundleContext) >> method is even getting called. >> >> Tom >> >> >> >> >> ----- Original message ----- >> From: Johan Compagner <[email protected]> >> Sent by: [email protected] >> To: P2 developer discussions <[email protected]> >> Cc: >> Subject: [EXTERNAL] Re: [p2-dev] anybody knows why an upgrade of our >> product (but not an eclipse upgrade) goes wrong like this? >> Date: Wed, Dec 4, 2019 7:36 AM >> >> there is no simple test i am afraid >> its really our install from a product version 2019.9 -> 2019.12 >> (and i think even the latest version of our product of .9 because it >> seems that bit older 2019.9_rc -> .12 works) >> >> i checked the code >> >> Collection<BundleCapability> matchingBundleCapabilities = >> fwkWiring.findProviders(ModuleContainer >> >> and it bombs out there >> so very like the fwkWiring is null >> >> that is assigned in the start() method >> >> public void start(BundleContext runtimeContext) { >> this.context = runtimeContext; >> this.fwkWiring = >> runtimeContext.getBundle(Constants.SYSTEM_BUNDLE_LOCATION).adapt(FrameworkWiring.class); >> >> so it seems that somehow that returns null (i guess that start() method >> has to be called) >> >> i can try to debug it a bit. >> >> >> On Wed, 4 Dec 2019 at 13:23, Mickael Istria <[email protected]> wrote: >> >> Hi, >> >> In any case, a NPE is a bug. So please report it, with the simplest steps >> to reproduce you can figure out. >> _______________________________________________ >> p2-dev mailing list >> [email protected] >> To change your delivery options, retrieve your password, or unsubscribe >> from this list, visit >> https://www.eclipse.org/mailman/listinfo/p2-dev >> >> _______________________________________________ >> p2-dev mailing list >> [email protected] >> To change your delivery options, retrieve your password, or unsubscribe >> from this list, visit >> https://www.eclipse.org/mailman/listinfo/p2-dev >> >> >> >> _______________________________________________ >> p2-dev mailing list >> [email protected] >> To change your delivery options, retrieve your password, or unsubscribe >> from this list, visit >> https://www.eclipse.org/mailman/listinfo/p2-dev >> >> _______________________________________________ >> p2-dev mailing list >> [email protected] >> To change your delivery options, retrieve your password, or unsubscribe >> from this list, visit >> https://www.eclipse.org/mailman/listinfo/p2-dev >> >> >> >> _______________________________________________ >> p2-dev mailing list >> [email protected] >> To change your delivery options, retrieve your password, or unsubscribe >> from this list, visit >> https://www.eclipse.org/mailman/listinfo/p2-dev > >
_______________________________________________ p2-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/p2-dev
