| Re: [cdt-dev] Future of Qt Plug-ins (Issue #123) |
Hello folks,I have opened this ticket to figure out what to do about the Qt plug-ins.I propose we simply delete them as part of CDT 11. I previously discussed this off-list with Blackberry folk as they were the only ones to be involved and Alena confirmed at the time that it was Doug's pet project.If you need them, please speak up. We can always restore them, or you can fork them.Jonah---------- Forwarded message ---------
From: Jonah Graham <notifications@xxxxxxxxxx>
Date: Fri, 28 Oct 2022 at 16:39
Subject: [eclipse-cdt/cdt] Future of Qt Plug-ins (Issue #123)
To: eclipse-cdt/cdt <cdt@xxxxxxxxxxxxxxxxxx>
Cc: Jonah Graham <jonah@xxxxxxxxxxxxxxxx>, Your activity <your_activity@xxxxxxxxxxxxxxxxxx>
For a while now the Qt plug-ins have had at least some issues. They rely on the Nashorn script engine which was removed in Java 15. In theory, before CDT 11 someone could have been using the Qt plug-ins with Java 11 still, even though the packaged Eclipse for C/C++ Developers has been on Java >=15 for ~2 years.
We did a workaround to make the error non-fatal in 2020 when Java 15 came out. I don't know how much of the rest of the Qt features are usable/relevant without the Nashorn script engine.
The last feature/bugfix commit of relevance on Qt was b9c9c44 3+ years ago, but the last real work was back in 2017. Qt was one of Doug's projects, I don't know if QNX/Blackberry relied on it.
Going forward now that we have upped the requirement to Java 17 (in #80) we have to decide what to do about Qt going forward.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.