Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ecf-dev] Asyncproxy and Java 7

On 2/21/2015 12:54 AM, Dario Foresti wrote:

Hi Scott, 

thank you for your usefull reply to my question.


I'm not running one of examples within ECF, i'm running a product specific for my application. 

My product config is based on features, in one of these features there is the dependency from org.eclipse.ecfremoteservice.asyncproxy bundle. If i run the product from PDE i have a version error because eclipse always load the highest version of asyncproxy bundle, not the right one for j7 environment. And your detailed answer confirms to me that in eclipse PDE there is a bug .


Before to post my question on ecf mailing list, i tried to resolve the problem fixing the exact version of asyncprovy bundle (with the correct version and qualifier) into the feature config (as suggested also in your answer). But for me this solution seems to be wrong, because when i run the application Eclipse continue to load the highest version of the bundle. It seems like Eclipse consider the version as a "minimum version", not a "fixed version". But, if i export the product and run the application outside the PDE, the right plugin version is loaded and wired.


For now, the right solution for me seems to be the second one: create a product, launch the application with wrong version and then modify the created launch config forcing the 1.0.0 version of asyncproxy bundle. I try this solution and works perfectly.


At last, another little question: what about the J7 support in next ECF releases? I'm not sure that IBM will develop a JDK8 for Power8 and linux in short times and it is possible that i will have to use J7 also when the new release of ECF will be released.


I/we will do what we can to work around the PDE issue causing the problem WRT j7 and asyncproxy 1.0.0 bundle.  If you are able to help with this (e.g. make suggestions, etc) please join bug

https://bugs.eclipse.org/bugs/show_bug.cgi?id=460466

BTW, another work around (hinted at by Wim) would be to simply remove the asyncproxy 2.0.0 version from your target platform.  If it's not there, it can't be incorrectly selected by PDE.

Thanks,

Scott


Back to the top