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>
To: Cross project issues <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
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
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
