Try to fix releases again.

Use maven server to specify git username/password
Remove references to maven-deploy-plugin, since nexus-staging-maven-plugin overrides it

Author: philsttr

.github/maven/settings.xml

@@ -1,5 +1,10 @@
 <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
     <servers>
+        <server>
+            <id>github</id>
+            <username>${env.GITHUB_ACTOR}</username>
+            <password>${env.GITHUB_TOKEN}</password>
+        </server>
         <server>
             <id>ossrh</id>
             <username>${env.OSSRH_USERNAME}</username>

.github/workflows/build.yml

@@ -53,7 +53,7 @@ jobs:
     if: github.event_name == 'push' && github.repository == 'logstash/logstash-logback-encoder' && github.ref == 'refs/heads/main' && startsWith(github.event.commits[0].message, '[release]')
     steps:
       - name: Checkout Code
-        uses: actions/checkout@v1.1.0
+        uses: actions/checkout@v2
         with:
           ref: main
 
@@ -86,5 +86,7 @@ jobs:
       - name: Release
         run: ./mvnw --batch-mode --no-transfer-progress --show-version --settings .github/maven/settings.xml --activate-profiles ossrh release:prepare release:perform
         env:
+          GITHUB_ACTOR: ${{ GITHUB_ACTOR }}
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           OSSRH_USERNAME: ${{ secrets.OSSRH_USERNAME }}
           OSSRH_PASSWORD: ${{ secrets.OSSRH_PASSWORD }}

.github/workflows/steps/setup-git.sh

@@ -19,7 +19,3 @@ git config --local tag.forceSignAnnotated true
 echo Setting git user to "${GPG_USER_NAME}" with email "${GPG_USER_EMAIL}"
 git config --local user.name "${GPG_USER_NAME}"
 git config --local user.email "${GPG_USER_EMAIL}"
-
-echo Propagating git authentication from local config to global config
-git config --global http.https://github.com/.extraheader "$(git config --get http.https://github.com/.extraheader)"
-

pom.xml

@@ -44,7 +44,6 @@
         <maven-checkstyle-plugin.version>3.1.2</maven-checkstyle-plugin.version>
         <maven-clean-plugin.version>3.1.0</maven-clean-plugin.version>
         <maven-compiler-plugin.version>3.8.1</maven-compiler-plugin.version>
-        <maven-deploy-plugin.version>2.8.2</maven-deploy-plugin.version>
         <maven-enforcer-plugin.version>3.0.0</maven-enforcer-plugin.version>
         <maven-gpg-plugin.version>3.0.1</maven-gpg-plugin.version>
         <maven-install-plugin.version>3.0.0-M1</maven-install-plugin.version>
@@ -62,6 +61,9 @@
         <!-- maven-javadoc-plugin configuration -->
         <maven.javadoc.failOnError>true</maven.javadoc.failOnError>
         <maven.javadoc.failOnWarnings>true</maven.javadoc.failOnWarnings>
+
+        <!-- the server id the maven-release-plugin uses to obtain credentials to use when pushing tags/commits -->
+        <project.scm.id>github</project.scm.id>
     </properties>
 
     <licenses>
@@ -433,12 +435,6 @@
                     </configuration>
                 </plugin>
 
-                <plugin>
-                    <groupId>org.apache.maven.plugins</groupId>
-                    <artifactId>maven-deploy-plugin</artifactId>
-                    <version>${maven-deploy-plugin.version}</version>
-                </plugin>
-
                 <plugin>
                     <groupId>org.apache.maven.plugins</groupId>
                     <artifactId>maven-install-plugin</artifactId>
@@ -541,10 +537,6 @@
                     <groupId>org.apache.maven.plugins</groupId>
                     <artifactId>maven-release-plugin</artifactId>
                     <version>${maven-release-plugin.version}</version>
-                    <configuration>
-                        <!-- Use our own profile instead of the default "release-profile" -->
-                        <releaseProfiles>release</releaseProfiles>
-                    </configuration>
                 </plugin>
 
                 <plugin>
@@ -601,33 +593,6 @@
             </properties>
         </profile>
 
-        <!-- Profile activated during release:prepare and release:perform instead
-             of the legacy release-profile that is otherwise activated during a release 
-             build by the maven-release-plugin.
-             
-             Reasons are:
-             - the "sources" artifact is produced by the shade plugin. The one produced by
-               the legacy profile must be discarded.
-             - javadoc is already produced by normal builds.
-             
-             Note: maven-deploy-plugin:3.0.0 does not support the "updateReleaseInfo" configuration
-                   parameter anymore. This profile can be removed after upgrading.
-         -->
-        <profile>
-            <id>release</id>
-            <build>
-                <plugins>
-                    <plugin>
-                        <groupId>org.apache.maven.plugins</groupId>
-                        <artifactId>maven-deploy-plugin</artifactId>
-                        <configuration>
-                            <updateReleaseInfo>true</updateReleaseInfo>
-                        </configuration>
-                    </plugin>
-                </plugins>
-            </build>
-        </profile>
-        
         <profile>
             <id>github</id>
             <activation>