Hi,
The public facing URL for our SonarQube server has been changed to
https://sonar.eclipse.org
which is more convenient and easier to remember than the old one
(https://dev.eclipse.org/sonar). It's also now the same URL as the
internal URL, so there is less guess work involved in the
Should we add uninstallbundle commands in the p2.inf file for the Docker
Tooling feature to remove all the http bundles
that might have been installed by a previous version? I have found another
problem when installing the Docker tooling
feature from the new aggregation on top of the Neon.3 EPP
Ed Merks wrote:
➢ If nothing requires a given bundle, I would expect that bundle to be
➢ removed from the profile, but I don't see the problematic bundles being
➢ removed...
If I’m not mistaken, the current solution with Neon.3a is reverting the
problematic http bundle to the Neon.2 version;
FWIW: I did a test where I removed my new Docker Tooling feature from my
EPP for committers and installed the old Neon.3 version from
the Neon repo. This caused a number of errors as everyone else is seeing.
I then updated to the new Docker Tooling version I just merged into
Ok, I have found the problem. The Neon site has some newer dependency
plug-ins that were used by the docker-client 3.6.8.
I fixed org.eclipse.linuxtools.docker.core to demand 3.4.0, but the newer
dependencies
were being brought in like slf4j and jackson packages since they were
latest and
Thanks Jeff,
This is the comparison of the non-unique versions list:
neon3_respin aggregation build 20.04.
(https://hudson.eclipse.org/simrel/job/simrel.neon.3_respin.runaggregator.BUILD__CLEAN/2/artifact/aggregation/final/buildInfo/reporeports/reports/nonUniqueVersions.txt):
> Users that already upgraded are unaffected by this. They still need to
wait for a "wiring issue" fix.
Why is that? If they upgrade from Neon.3 to Neon.3a I would expect it
disables the broken bundles and things work. Like I can also update from
Neon.0 to Neon.3a.
Dani
From: Frederic
Fred,
What update site URL contains these results?
Regards,
Ed
On 25.04.2017 14:28, Frederic Gurr wrote:
Thanks Jeff,
This is the comparison of the non-unique versions list:
neon3_respin aggregation build 20.04.
Ed,
The temporary update site URL is:
https://hudson.eclipse.org/simrel/job/simrel.neon.3_respin.runaggregator.BUILD__CLEAN/3/artifact/aggregation/final
Regards,
Fred
On 25.04.2017 15:13, Ed Merks wrote:
> Fred,
>
> What update site URL contains these results?
>
> Regards,
> Ed
>
>
> On
Fred,
Installing the Eierlegende Wollmilchsau with this additional repository
in the p2 task's repository list results in an installation without
wiring problems.
The profile of the installation contains version 2.3.0.20170421191 of
org.eclipse.linuxtools.docker.core with is indeed the
Thanks Ed.
That sounds promising. Did you also test updating a broken ELWMS with
the new repo?
I'm currently trying to reproduce the error with EPP packages, but so
far updating a Neon.2 package to Neon.3 (with "Check for Updates") did
not result in a broken MPC. Not sure what I'm missing.
Fred,
No I didn't try that. It's much harder to try that. Oomph itself is
broken, so I can't run setup tasks. Check for Updates finds no updates
because I installed all the categories and their IUs don't have updated
versions. I tried explicitly installing Docker so that it would do an
12 matches
Mail list logo
