Community
Participate
Working Groups
Build Identifier: I20120608-1400 (4.2.0) I put Google Guava 12.0.1 into the dropins folder. It looks like another version of guava is used by the code recommenders. A possible fix is to restrict the required guava version in all plug-ins: com.google.guava;bundle-version="[10.0.0,11.0.0)" I added the version constraints to about 4 plug-ins (2 were already correct) and now it is working for me. The Guave team does not support unlimited backward compatibility, so restricting the versions to major would be better, instead to leave it unbounded. Reproducible: Always Steps to Reproduce: 1. Put Google Guava 12.0.1 into dropins folder 2. Start Eclipse 3. Type e.g.: System.err.println 4. Invoke Content Assist at the end of println (Content assist for parameters works, but not for types)
Created attachment 218791 [details] The errors that appear in the Error Log view.
Thanks for the report. We'll fix this for 1.0.1
Fix will be available on HEAD update site in 30 minute for testing. The following manifests have been modified: http://git.eclipse.org/c/recommenders/org.eclipse.recommenders.git/commit/?id=b43b194ab86538c14fd72af745d4fb9cedd668dc Please note that the root cause is not a binary incompatibility between 10 and 12 (guava keeps compatibilitiy for non-beta classes for 6 releases ~1 1/2 years) but that different bundles loaded different versions of the same class with two different class loaders. A cleaner workaround would be to reexport the guava bundle from those plugins that make these types available as part of their API to prevent us from these classloader issues in future. Anyway. This fix should work ;)
Thank you for the fix and the explanation of the real cause.
