Re: [cross-project-issues-dev] "The software you installed requires [...] nodejs >= 6"

On Mon, Dec 9, 2019 at 4:12 AM Jonah Graham wrote: > > > On Sun, 8 Dec 2019 at 14:05, Aleksandar Kurtakov > wrote: > >> On Sun, Dec 8, 2019 at 5:43 PM Jonah Graham >> wrote: >> >>> Does anyone recognize the attached error message? It comes up whenever I >>> open the cdt.target file recently,

Re: [cross-project-issues-dev] Re-spin for 4.14

Hi Vikas, Will there be a new 4.14RC2 repository in this page? The I20191210-0610 build is marked unstable. Or am I just asking too early?... https://download.eclipse.org/eclipse/downloads/index.html Thanks, Patrick On Tue, Dec 10, 2019 at 4:39 AM Vikas Chandra wrote: > Hi all, > > I have

Re: [cross-project-issues-dev] Installer Enhancements for 2019-12 / Making Marketplace Great Again

I tried installing the Simrel IDE (on macOS). When I run it, I get four errors from org.eclipse.e4.ui.workbench, including two ConcurrentModificationExceptions from SWT and a NullPointerException from mylyn, a warning from oomph.setup.core "org.eclipse.jgit.api.errors.TransportException:

Re: [cross-project-issues-dev] Can we please stop using composite repos?

Jonah, I think one way that a *.target is invalidated is in the case that one specifies exact IU IDs in a *.target file.  Then of course the specific versions could disappear and a *.target that previously resolved would no longer resolve (and PDE has a bad habit of destroying the target

Re: [cross-project-issues-dev] Can we please stop using composite repos?

Hi Ah! That corresponds to what I observe and am always puzzled by. Given that the previous installations are fully available in the features/plugins folders, why is it necessary for a reversion to do any remote access at all? At best it wastes time, at worst it fails.     Regards        

Re: [cross-project-issues-dev] Can we please stop using composite repos?

Thank you Camille. I have added your extra information to the FAQ for posterity. ~~~ Jonah Graham Kichwa Coders www.kichwacoders.com On Tue, 10 Dec

Re: [cross-project-issues-dev] Can we please stop using composite repos?

Hi Jonah, IIRC (from a few years ago :) ), one of the reasons to keep multiple versions in the Simrel Composite was to support rollback. If you updated e.g. from M1 to M2 and noticed that something's broken, you can revert to M1 automatically (Via Installed Software -> Installation History).

Re: [cross-project-issues-dev] Can we please stop using composite repos?

Thanks Ed and Mikael for responding. I will change to use the staging repo to build & release my EPP product - I hadn't liked it in the past because it was a moving target as people updated the simrel contents. However, I was only referring to multiple children providing just different versions

Re: [cross-project-issues-dev] Installer Enhancements for 2019-12 / Making Marketplace Great Again

Keep pushing things forward, Ed. Love it, thank you for your work! Denis On 2019-12-10 6:12 a.m., Ed Merks wrote: > > Hi, > > On a more positive note, for the 2019-12 release, the installer > exploits the platform's cool "link handler" support that was > implemented by Matthias Becker; thanks

Re: [cross-project-issues-dev] Installer Enhancements for 2019-12 / Making Marketplace Great Again

Hi Ed, awesome response time! Thank you for looking into this! Best Sebastian On Tue, Dec 10, 2019 at 1:34 PM Ed Merks wrote: > Sebastian, > > So I had a quick look and indeed these are false positives as detailed in > this comment: > >

Re: [cross-project-issues-dev] Installer Enhancements for 2019-12 / Making Marketplace Great Again

Sebastian, So I had a quick look and indeed these are false positives as detailed in this comment:   https://bugs.eclipse.org/bugs/show_bug.cgi?id=550713#c22 The short explanation is that the resolution process resolves the Xtext requirement to the version of Xtext on the train repo that

Re: [cross-project-issues-dev] Installer Enhancements for 2019-12 / Making Marketplace Great Again

Sebastian, Note that the job which does this testing is this one which includes a link to the overall report (which loads very slowly and is bad for the server):   https://ci.eclipse.org/oomph/job/marketplace-analyzer/ The testing actually tests every listing (does a p2 resolve) against

Re: [cross-project-issues-dev] Installer Enhancements for 2019-12 / Making Marketplace Great Again

Hi Ed, thank you very much for providing all the insights and reports. This is greatly appreciated! When I checked the report for the Xtext marketplace entry, I saw a green checkmark for the Juno release, even though the marketplace entry is only for Oxygen and newer. What does that mean? Best

[cross-project-issues-dev] Installer Enhancements for 2019-12 / Making Marketplace Great Again

Hi, On a more positive note, for the 2019-12 release, the installer exploits the platform's cool "link handler" support that was implemented by Matthias Becker; thanks Lars Vogel for drawing my attention to this gem. As an example, this means that clicking the following link can

Re: [cross-project-issues-dev] 2019-12: The Eclipse Eierlegende Wollmilchsau

Ed, The early startup is not really so early.  It's certainly not something that is invoked before the choose-workspace dialog comes up.   It's more of a performance thing (how much "eager" stuff does one really need to do?) and also a thread-safety thing (does your bundle start expect to

Re: [cross-project-issues-dev] 2019-12: The Eclipse Eierlegende Wollmilchsau

Mickael, Comments below. On 10.12.2019 10:05, Mickael Istria wrote: Hi Ed, Thanks for bringing this. I was actually waiting for the best opportunity to start discussing a very related topic, but from a maintenance POV not a user one, and I think this is a good one: *What is the value and

Re: [cross-project-issues-dev] 2019-12: The Eclipse Eierlegende Wollmilchsau

Hi Mickael I think you forget why SimRel started and so overlook its major utility. Pre-SimRel, it was hard to know what version of what worked with what requiring users of multiple tools to maintain distinct Eclipses for distinct application domains. Post-SimRel there is a pretty good

Re: [cross-project-issues-dev] [4.14] [regression] Bug 558004 - Several NPEs when compiling module declarations after 549855

This one will not be included in the respin. Dani From: "Vikas Chandra" To: eclipse-...@eclipse.org Cc: eclipse-pmc-boun...@eclipse.org, platform-dev , Cross-Project Date: 10.12.2019 05:08 Subject:[EXTERNAL] [cross-project-issues-dev] [4.14] [regression] Bug 558004 -

[cross-project-issues-dev] Re-spin for 4.14

Hi all, I have just started re-spin for 4.14. The respin contains fix for Bug 558022 - [regression] Dot resources are shown by default in Project Explorer / Common Navigator https://bugs.eclipse.org/bugs/show_bug.cgi?id=558022 Thanks and Regards, Vikas

Re: [cross-project-issues-dev] 2019-12: The Eclipse Eierlegende Wollmilchsau

Hi Ed On 10/12/2019 08:56, Arthur van Dorp wrote: Or is it just the interactions such that no single bundle is actually to blame?  Or did I install something that should not be installed in an IDE? Kind of Yes. My strong prejudice is that earlyStartup is a major facility that some projects

Re: [cross-project-issues-dev] 2019-12: The Eclipse Eierlegende Wollmilchsau

Hi Ed, Thanks for bringing this. I was actually waiting for the best opportunity to start discussing a very related topic, but from a maintenance POV not a user one, and I think this is a good one: *What is the value and quality of SimRel? Is it worth it's cost?* As you're highlighting, the

Re: [cross-project-issues-dev] Can we please stop using composite repos?

>> >> Can the composite only include the current/latest version, or can someone >> educate me as to the value of having multiple versions? > It's a really good question. It just seems to be a "habit" to compose > multiple children, usually with some restriction on the number of children, >