| Re: [ecf-dev] Asyncproxy and Java 7 |
|
On 2/20/2015 7:41 AM, Dario Foresti
wrote:
Sure. First question: how are you starting/running/debugging things? If you are running one of the example product configs (e.g. TimeService.*.product from within Eclipse, there's a known problem with PDE that I'm trying to find a reliable work-around for: The behavior seems to be that when the Eclipse generates a launch config from running/debugging the .product config it *always* uses the highest version (i.e. 2.0.0 of asyncproxy) when there are multiple versions of a bundle present in the target (as is the case with the ECF remoteservice SDK installed into Eclipse). In this case, it should rather select the 1.0.0 version of asyncproxy, because of the Require-Capability constraint you quote above (2.0.0 requires java8, 1.0.0 =< j7). I suspect the reason for this is that PDE doesn't yet look at Require-Capability constraints (probably because I don't think p2 does yet either [1]) and so doesn't pay attention to the 1.8 constraint when selecting bundles for the launch config. Anyway, I'm trying to think of ways to word around this in the next ECF release, but haven't got a solution yet. If this is what's happening (.product config -> .launch config selecting wrong version), then one work around that you can do yourself is to generate the launch config, get the error above on start, and then go to the Run.../Debug... entry for that generated launch config, go to the plugins tab, and unselect the 2.0.0 version and select the 1.0.0 version from the list on the plugins tab. This is inconvenient, I know, especially since if you have to change the product config, then you will need to re-generate the .launch (as I do for the examples), change the selected version again...etc. But it does work. If you are *not* using the example product configs, however (you have your own product config and/or features), this does point to a different/better solution for you. In that case, in your product config and/or feature that includes the asyncproxy bundle, you can specify the *exact version* of the async proxy to use (i.e. 1.0.0.v20140410-1838). Then, when PDE generated the launch config, it will use the correct one. I understand this is somewhat brittle, because if we update the qualifier in a new version you will have to update your product and/or feature to reference a new version, but I can say that this version has been in place for nine months without change, and I don't know of/expect any bugs, so I expect it to be relatively stable. If I'm misunderstanding/misinterpreting what you are doing to launch please let me know. If you are doing something else/different from what I described above, then there may be other ways to prevent this from happening. I've opened an ECF bug [2] to track pursuing a work-around for this. Thanks for speaking up. Scott [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=313553 [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=460466 |