Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EGit/New and Noteworthy/5.3"
(→GPG-signing Commits) |
|||
| (7 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
= EGit = | = EGit = | ||
| + | |||
| + | == Requires Eclipse Neon == | ||
| + | |||
| + | EGit 5.3.0 requires Eclipse Neon (4.6) or better. If you use an older version of Eclipse, you are recommended to upgrade the complete Eclipse IDE. | ||
== GPG-signing Commits == | == GPG-signing Commits == | ||
| Line 5: | Line 9: | ||
EGit 5.3.0 can sign commits with GPG. | EGit 5.3.0 can sign commits with GPG. | ||
| − | [[File:egit-commit-sign.png]] | + | [[File:egit-commit-sign.png|alt=Screenshot of the EGit Staging View with the new "Sign commit" icon]] |
The new icon in the upper right will allow you to toggle commit signing on or off. The default is read from the Git configuration. If the config option <code>commit.gpgsign</code> is set to <code>true</code>, the button will be selected by default. The value of <code>user.signingkey</code> will be used to determine the signing key. If the value is unset, the email address of the committer will be used to lookup the key. If no key can be found a commit will fail. | The new icon in the upper right will allow you to toggle commit signing on or off. The default is read from the Git configuration. If the config option <code>commit.gpgsign</code> is set to <code>true</code>, the button will be selected by default. The value of <code>user.signingkey</code> will be used to determine the signing key. If the value is unset, the email address of the committer will be used to lookup the key. If no key can be found a commit will fail. | ||
| − | Keys will be looked up from your GPG keyring (either <code>~/.gnupg/pubring.kbx</code> or <code>~/.gnupg/secring. | + | Keys will be looked up from your GPG keyring (either <code>~/.gnupg/pubring.kbx</code> or <code>~/.gnupg/secring.gpg</code>; on Windows the directory <code>%APPDATA%\gnupg</code> is used—if it exists—instead of <code>~/.gnupg</code>). |
See the following GitHub help pages for help on GPG signing keys: | See the following GitHub help pages for help on GPG signing keys: | ||
| Line 19: | Line 23: | ||
In the last release we had introduced a new SSH client based on the [https://mina.apache.org/sshd-project/ Apache MINA sshd] library as an alternative to the JSch-based client. In EGit 5.3.0 the default settings are switched: by default, the Apache MINA implementation is used. | In the last release we had introduced a new SSH client based on the [https://mina.apache.org/sshd-project/ Apache MINA sshd] library as an alternative to the JSch-based client. In EGit 5.3.0 the default settings are switched: by default, the Apache MINA implementation is used. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
We plan to remove the old JSch SSH implementation completely in a future release of EGit. | We plan to remove the old JSch SSH implementation completely in a future release of EGit. | ||
| − | + | == Compare and Merge Editors == | |
| − | + | ||
| − | + | Text comparisons in Eclipse have been improved to make "Show Whitespace" work in more cases. | |
| − | + | ||
| + | Also, concurrent editing of a file in a merge editor and in another editor open on the same file has been improved and works now better and even for files not in the Eclipse workspace. | ||
| + | |||
| + | [[File:EGit Compare Editor Show Whitespace.png|alt=Screenshot of a Java comparison in Eclipse (workspace against index) showing whitespace on the index side]] | ||
| + | |||
| + | Note that both showing whitespace and concurrent editing depend not only on the way EGit sets up the comparison (which is what we improved) but also on the actual editors being used. These editors are beyond the control of EGit. With files not in the Eclipse workspace, one may encounter Platform [https://bugs.eclipse.org/bugs/show_bug.cgi?id=214351 bug 214351] when a file is open in another editor. | ||
== Other Changes == | == Other Changes == | ||
| − | The complete list of new features and bug fixes is available in the [https://projects.eclipse.org/projects/technology.egit/releases/5.3.0/ release notes]. | + | EGit 5.3.0 includes lots of less noticeable improvements in the UI, plus a number of bug fixes. We also made a number of performance improvements. The complete list of new features and bug fixes is available in the [https://projects.eclipse.org/projects/technology.egit/releases/5.3.0/ release notes]. |
= Contributors = | = Contributors = | ||
| − | The following | + | The following 10 developers worked on this release: |
| + | |||
| + | Christian W. Damus, | ||
| + | Frédéric Cilia, | ||
| + | Gunnar Wagenknecht, | ||
| + | Lars Vogel, | ||
| + | Luca Andreatta, | ||
| + | Matthias Becker, | ||
| + | Matthias Sohn, | ||
| + | Michael Keppler, | ||
| + | Thomas Wolf, | ||
| + | Tim Neumann | ||
| − | + | [[Category:EGit]] | |
Latest revision as of 22:20, 29 November 2023
Contents
EGit
Requires Eclipse Neon
EGit 5.3.0 requires Eclipse Neon (4.6) or better. If you use an older version of Eclipse, you are recommended to upgrade the complete Eclipse IDE.
GPG-signing Commits
EGit 5.3.0 can sign commits with GPG.
The new icon in the upper right will allow you to toggle commit signing on or off. The default is read from the Git configuration. If the config option commit.gpgsign is set to true, the button will be selected by default. The value of user.signingkey will be used to determine the signing key. If the value is unset, the email address of the committer will be used to lookup the key. If no key can be found a commit will fail.
Keys will be looked up from your GPG keyring (either ~/.gnupg/pubring.kbx or ~/.gnupg/secring.gpg; on Windows the directory %APPDATA%\gnupg is used—if it exists—instead of ~/.gnupg).
See the following GitHub help pages for help on GPG signing keys:
SSH Library
In the last release we had introduced a new SSH client based on the Apache MINA sshd library as an alternative to the JSch-based client. In EGit 5.3.0 the default settings are switched: by default, the Apache MINA implementation is used.
We plan to remove the old JSch SSH implementation completely in a future release of EGit.
Compare and Merge Editors
Text comparisons in Eclipse have been improved to make "Show Whitespace" work in more cases.
Also, concurrent editing of a file in a merge editor and in another editor open on the same file has been improved and works now better and even for files not in the Eclipse workspace.
Note that both showing whitespace and concurrent editing depend not only on the way EGit sets up the comparison (which is what we improved) but also on the actual editors being used. These editors are beyond the control of EGit. With files not in the Eclipse workspace, one may encounter Platform bug 214351 when a file is open in another editor.
Other Changes
EGit 5.3.0 includes lots of less noticeable improvements in the UI, plus a number of bug fixes. We also made a number of performance improvements. The complete list of new features and bug fixes is available in the release notes.
Contributors
The following 10 developers worked on this release:
Christian W. Damus, Frédéric Cilia, Gunnar Wagenknecht, Lars Vogel, Luca Andreatta, Matthias Becker, Matthias Sohn, Michael Keppler, Thomas Wolf, Tim Neumann