Re: [cross-project-issues-dev] Guava versions in Oxygen

2017-05-08 Thread Ed Merks
No, my reading is that you need a PB CQ for what you redistribute. Of course the need for a PB CQ is questionably stupid at best in the first place and I've offered to automate the whole process of tracking such dependencies. But alas, to no avail... On 08.05.2017 20:58, Sam Davis wrote:

Re: [cross-project-issues-dev] Guava versions in Oxygen

2017-05-08 Thread Sam Davis
> > Whether you need a PB is debateable. My reading of the words is that you > need a PB for anything any configuration might use. > I hope that is not the correct reading because it would imply that if you have open version ranges you need a PB for every version that will ever be released in the

Re: [cross-project-issues-dev] Guava versions in Oxygen

2017-05-08 Thread Ed Willink
Hi Wide version ranges should work fine. For OCL, I had to write one replacement routine that had no common solution in both version 15 and 21. Whether you need a PB is debateable. My reading of the words is that you need a PB for anything any configuration might use. I was very unpopular

Re: [cross-project-issues-dev] Guava versions in Oxygen

2017-05-08 Thread Zoltán Ujhelyi
Hi, the VIATRA project is not ready to move to Guava 21, as we still use Java 7 as a minimum requirement, while Guava 21 requires Java 8. We are now in the process of figuring out whether we can set up dependency ranges and uses constraints in a way that we can work both with Guava 15 and 21 (e

Re: [cross-project-issues-dev] [eclipse.org-planning-council] Neon.3 update problem status

2017-05-08 Thread Marcel Bruch
Hi Carsten, did any of the three scenarios previously result in an error? In other words: Was the problem reproducible for you and is that reproducible situation now fixed? Thanks, Marcel > On 8. May 2017, at 13:34, Carsten Reckord wrote: > > Hi all, > > I have tested the respin candidate w

Re: [cross-project-issues-dev] [eclipse.org-planning-council] Neon.3 update problem status

2017-05-08 Thread Carsten Reckord
Hi all, I have tested the respin candidate with MPC, and it looks good. I've tested 3 scenarios, using the JavaEE EPP package: 1. Neon.2 with Docker Tools and Oomph installed, updated to Neon.3a -> works, and the offending HttpClient is not installed 2. Direct install of Neon.3a with Docker Too

Re: [cross-project-issues-dev] SonarQube URL has changed

2017-05-08 Thread Lars Vogel
Looks like our Sonar server requires an update to allow the Eclipse IDE to connect to it: See https://bugs.eclipse.org/bugs/show_bug.cgi?id=516297 https://bugs.eclipse.org/bugs/show_bug.cgi?id=497088 Maybe once this is done, the URL will also start to work. Best regards, Lars On Mon, May 8, 201

Re: [cross-project-issues-dev] SonarQube URL has changed

2017-05-08 Thread Lars Vogel
Hi Fred, The generate toking button in the SonarLint Eclipse plug-in (see screenshot) tries to connect to the following webpage, which is reported as not existing: https://sonar.eclipse.org/account/security Can this be fixed? Best regards, Lars On Wed, Apr 26, 2017 at 1:38 AM, Frederic Gurr w