Hi As I was the one introducing google guava 12 to orbit I think I'm also addressed here. I understand that its not ok to have more than one version of a library in the application. But what I don't understand is what you want. Should the projects delivering versions of guava switch to a particular one? And which if this is the case? Or shouldn't the deliver guava at all and rely on the presence/absence of it in the application/EPP?
Sincerely Stephan --- Stephan Leicht Vogt Senior Software Engineer BSI Business Systems Integration AG Täfernstrasse 16a, CH-5405 Baden Phone (direct): +41 56 484 19 47 www.bsiag.com<http://www.bsiag.com> On May 8, 2013, at 8:23 AM, Ed Willink <e...@willink.me.uk<mailto:e...@willink.me.uk>> wrote: Hi For development I use 1.7, and so installation installs com.google.guava 10,11,12 and the tight tight 10.0.1 version bound of Xtext and other modeling applications seems to collaborate so that the IDE is ok. The problem is perhaps a bug in the launcher, where I use the default Project EE of 1.5 to check compliance. When MWE or Acceleo scripts are launched, the classpath provides the wrong com.google.guava and the bad version results. With the problem understood, I can easily change my launch settings, BUT This demonstrates that M7 has introduced a significant change compared to M5 (M6 was a transitional mess). com.google.guava has become a standard library so the change impacts perhaps 50%, perhaps more, of Eclipse applications. My particular problem came from using Xtext functionality in a standalone application. Nearly a year ago I tried to start a discussion as to whether EMF should move on from 1.5 to perhaps 1.6 but probably 1.7 so as to use a non EOL Java. No discussion followed. I favour moving on, but feel that it should be a positive community decision, rather than a de facto accident imposed by a library, which IMHO should be built with 1.5 compatibility. Regards Ed Willink On 07/05/2013 22:35, David M Williams wrote: > Since the bulk of Eclipse is still Java 5 compliant, this seems like a killer. The bulk, in terms of bundles, maybe ... but I know the Platform requires 1.6 (for Help to work, because Jetty requires 1.6) and I believe all the EPP packages specify 1.6 as minimum runtime (for that "product", not at a bundle level). So, I may be showing my ignorance, or missing your point, but if its simply a matter that using 12 would require users to use 1.6, it does not seem like a killer to me. Of course ... depends greatly on your adopters and target user. For interest, the "distribution" of BREEs are listed in one of our "simrel repo" reports ... http://build.eclipse.org/simrel/kepler/reporeports/reports/breedata.txt It shows the bulk still at 1.5 level, on a bundle-by-bundle basis, but a number at 1.6 and even some at 1.7! (Those requiring 1.7 make me a little nervous .. but, assume its necessary and satisfactory for adopters, or they would say if it was causing them problems). From: Ed Willink <e...@willink.me.uk><mailto:e...@willink.me.uk> To: Cross project issues <cross-project-issues-dev@eclipse.org><mailto:cross-project-issues-dev@eclipse.org>, Date: 05/07/2013 05:11 PM Subject: Re: [cross-project-issues-dev] com.google.guava versions Sent by: cross-project-issues-dev-boun...@eclipse.org<mailto:cross-project-issues-dev-boun...@eclipse.org> ________________________________ Hi https://bugs.eclipse.org/bugs/show_bug.cgi?id=401285 and https://bugs.eclipse.org/bugs/show_bug.cgi?id=370651 give details on com.google issues. My class version error arises because com.google.guava 12 has Java 6 rather than Java 5 classes. Since the bulk of Eclipse is still Java 5 compliant, this seems like a killer. Regards Ed Willink On 07/05/2013 20:11, David M Williams wrote: Can you explain more? I don't recall any previous problems (which, I know, says more about my memory than anything else .... just asking for current details). There are versions 10, 11, and 12 available from Orbit ... are you saying in your individual build you are getting multiple versions? If so, sounds like you simply need to "constrain" which version you want. Or ... are you saying multiple projects are using different versions and that causes a problem? If that's the case, I suggest a "cross-project bug" and describe what you are seeing, and if possible who is using which versions and see if you can gain some agreement to use "the highest version"? (Assuming that's the right one). HTH From: Ed Willink <e...@willink.me.uk><mailto:e...@willink.me.uk> To: Cross project issues <cross-project-issues-dev@eclipse.org><mailto:cross-project-issues-dev@eclipse.org>, Date: 05/07/2013 02:58 PM Subject: [cross-project-issues-dev] com.google.guava versions Sent by: cross-project-issues-dev-boun...@eclipse.org<mailto:cross-project-issues-dev-boun...@eclipse.org> ________________________________ Hi My recollection is that there was a com.google.guava version problem at M6. It seems to have got worse for M7. I find that I have version 10, 11 and 12 and no doubt the bad class version trouble is a consequence. How are we going to solve this? Regards Ed Willink _______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org<mailto:cross-project-issues-dev@eclipse.org> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev _______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org<mailto:cross-project-issues-dev@eclipse.org> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev No virus found in this message. Checked by AVG - www.avg.com<http://www.avg.com/> Version: 2013.0.3272 / Virus Database: 3162/6306 - Release Date: 05/07/13 _______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org<mailto:cross-project-issues-dev@eclipse.org> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev _______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org<mailto:cross-project-issues-dev@eclipse.org> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev No virus found in this message. Checked by AVG - www.avg.com<http://www.avg.com/> Version: 2013.0.3272 / Virus Database: 3162/6306 - Release Date: 05/07/13 _______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org<mailto:cross-project-issues-dev@eclipse.org> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
