-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test implemention of #858 suggested method #890
Test implemention of #858 suggested method #890
Conversation
The idea is to enable a state that emulates a bugfix patch, after a release cycle ends. If confirmed to work It can be handed over to delivery by dependabot[bot]
…set=utf-8 to TextTransfer(). This makes it possible to paste into eclipse from a KDE/QT app in a wayland session with gtkv3.24.33 and higher(ubuntu 22.04-LTS).
…ain;charset=utf-8 to the wayland clipboard Enables copy from eclipse to KDE/QT apps in a wayland session(RFC-1341)
Fix wrong implementation of TEXT_PLAIN_UTF8 transfer feature due to commit 666b7fd
Hmmm
try to figure out what a jenkinsfile is and what the exact filename is. |
OK |
OK the local build now completes without any FAILURES.
Now just to solve the warnings
No |
OK and:
|
update maven to 2.9.3
|
Yes no warnings. Onto --> #858 (comment) |
Yes no warnings. Onto --> #858 (comment) Clipboard functionality validated with both local and automated build. With the downloaded files the about plugins view says:
With the local files the about plugins view says:
|
zzz |
OK It is only needed to copy 2 files not 3.
And Clipboard works both ways between Eclipse and Kate in a kde session running on a standard Kde Neon (ubuntu 22.04 LTS based) also on my old Eclipse PHP installation where the plugins are in the Eclipse installation folder (updated to 2023-09). |
I have a coarser-grain question here: what do you expect by trying to backport the change to 4.29 branch? The Eclipse project doesn't build a 4.29.x branch any more, so even if this is merged, then it wouldn't make the output available in any 4.29.x binary. Why not just using 4.30 ? |
I have an elder active scientist I'm supporting and he is unable to use 4.30 before the official release. |
This is a draft. Do not merge.Update:
Ready for review please look at #884
This is a test that implements #858 and adds #879 as payload
The purpose is to check if a Maintenance branch
would be able to deliver build artifacts suited
for testing bugfix purposes (during a freeze).
It will be implemented as 1 + 3 commits
The first one enables building by emulating dependabot[bot]
The idea is to setup a state that emulates a bugfix patch.
As there are needed functional changes for the build to succeed
The last 3 commits are cherry picked from the wayland_qt_clipboard_fix
merged recently.
Update
Test is concluded successfully, however:
I think I placed this Draft_PR the wrong place/way.
Where is there a place for testing adding new functionality under a freeze ?
Final update for review.
Is this a bug-fix or a new feature !
What would the consequences of being able to merge this commit in the M3-->RCx period be for 2023-09 users
I an ideal world ?