[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cross-project-issues-dev] [eclipse.org-planning-council] Neon.3 update problem status
- From: "Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>
- Date: Tue, 9 May 2017 16:53:30 +0000
- Accept-language: en-US
- Delivered-to: firstname.lastname@example.org
- Thread-index: AQHSyOTJ0LvdsEPrUkGSsuerZBfwgQ==
- Thread-topic: [cross-project-issues-dev] [eclipse.org-planning-council] Neon.3 update problem status
- User-agent: Microsoft-MacOutlook/f.20.0.170309
Regarding ânon-deterministicâ: One thing Iâve observed earlier is, that once a bundle is
Wired that wiring tends to âstickâ if there are multiple alternatives (ie thereâs ambiguity).
So it might make a difference in what order you install / update your stuff.
In my use-case, I could reproduce a wiring problem when I installed bundles with
Command-line p2 and launched Eclipse on the full install (which was ambiguous).
I could resolve the issue by installing only part of my bundles, launching Eclipse
(which caused bundles to be wired OK), and installed the rest afterwards.
I cannot explain this behavior, but perhaps this observation helps â
Martin Oberhuber, SMTS / Product Owner â Development Tools, Wind River
On 09/05/17 11:45, "cross-project-issues-dev-bounces@xxxxxxxxxxx on behalf of Carsten Reckord" <cross-project-issues-dev-bounces@xxxxxxxxxxx on behalf of reckord@xxxxxxxx> wrote:
> 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?
Good question. I was able to reproduce the issue when it first came up by installing the Docker Client into a vanilla Neon.3, and also by updating a Neon.2 that had it installed. So I actually didn't try this time around.
As it turned out now that I did, I couldn't get the broken wiring to appear even with the current public Neon.3 version. Equinox now always wires both MPC and USS to the non-broken 4.3.6 version, whereas it did wire MPC to 4.5 before, causing the breakage. I guess there's some non-deterministic element in what's going on in bug 514149? Otherwise I'm not sure what might be different...
At any rate, installations based on the new Neon.3a candidate are looking good from MPC's perspective.
cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit