Re: peer not authenticated error
INFRA advised me to upgrade to maven 3.8.6. That did not fix the problem. It then occurred to me to follow the terminal advice from the failed upload: [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn -rf :derbyLocale_ko_KR Even though there were no errors to correct, I issued that command. The upload continued without further errors. I verified that the artifacts were all uploaded to the Nexus staging repository. Thanks to everyone who helped me puzzle through this, -Rick On 6/14/22 6:51 AM, Rick Hillegas wrote: Thanks for looking at the pom, Slawomir. As part of the publication process, we run a program which replaces all of those ALPHA_VERSION tokens with the actual release id (in this case, 10.16.1.1). On 6/14/22 1:19 AM, Slawomir Jaranowski wrote: Hi, In your project I see: derby-project ALPHA_VERSION Please try to change project version to SNAPSHOT (all modules), eg 10.16.0-SNAPSHOT , you can use mvn versions:set -DnewVersion=10.16.0-SNAPSHOT and than try mvn deploy Please note that you can not override release version. wt., 14 cze 2022 o 10:00 Tamás Cservenák napisał(a): Howdy, So is the "peer not authenticated" error still sporadically happening? Qs: - can you use some LTS java instead of 18? (17 or 11?) - could you execute the build with -e (or -X but this will give you a LOT of logs) and paste the stack trace? - you sure you are directly accessing repo.a.o, no proxy or whatever in between your maven process and repo.a.o? HTH T On Tue, Jun 14, 2022 at 12:10 AM Rick Hillegas wrote: Thanks, Tamas. On your advice, I updated the top level pom to refer to version 26 of the parent apache pom. This caused the maven-antrun-plugin to object that a major upgrade had obsoleted the element. I was advised to change to . I did that too. However, I am still seeing "peer not authenticated" messages. On 6/13/22 11:15 AM, Tamás Cservenák wrote: Howdy, Well, sadly I see that svn tag is in place, but the very first observation I have is that due to ancient parent Apache POM version 10, you use ancient plugins despite the latest Maven being used. Please try to upgrade parent to current one (current version is 26). So in here https://svn.apache.org/repos/asf/db/derby/code/trunk/maven2/pom.xml make project/parent/version = 26 Parent version 10 you use is from 2011 hence you use plugins that are 11 years old or older, made for Maven2, and I really have no idea what kind of bug(s) may be hit here... Note: ASF parent 10 says java level is 1.4... so this may need some alignment as well... Also, why Java 18? Is it needed or is it just handy? (I'd go with some LTS rather) Other than that, given the sporadic nature of the error, I really can't say more, maybe some misbehaving proxy in between maven process and repo.apache.org? HTH Tamas On Mon, Jun 13, 2022 at 7:45 PM Rick Hillegas wrote: I need advice about how to move past a "peer not authenticated" error. I am trying to stage some 20 jars and corresponding poms via the following command: mvn -Dgpg.passphrase="my secret passphrase" clean deploy I am able to upload most of the artifacts, but the command eventually fails with a "peer not authenticated" error. The artifact which incurs this error is not consistent. I have tried this from two different locations (Palm Springs and San Francisco). But I can't get to the end of the upload without a "peer not authenticated" error: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy) on project derbyLocale_ko_KR: Failed to deploy artifacts: Could not transfer artifact org.apache.derby:derbyLocale_ko_KR:pom.asc:10.16.1.1 from/to apache.releases.https (https://repository.apache.org/service/local/staging/deploy/maven2): transfer failed for https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/derby/derbyLocale_ko_KR/10.16.1.1/derbyLocale_ko_KR-10.16.1.1.pom.asc : peer not authenticated -> [Help 1] Here is my environment: maven 3.8.5 OpenJDK Runtime Environment 18.9 (build 11+28) Based on some advice I found on the internet, I tried adding the following stanza to my top level pom: ... org.apache.maven.plugins maven-deploy-plugin 3 That does not fix the problem. Any help you can give me would be appreciated. Thanks, Rick - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail:
Re: peer not authenticated error
Thanks for looking at the pom, Slawomir. As part of the publication process, we run a program which replaces all of those ALPHA_VERSION tokens with the actual release id (in this case, 10.16.1.1). On 6/14/22 1:19 AM, Slawomir Jaranowski wrote: Hi, In your project I see: derby-project ALPHA_VERSION Please try to change project version to SNAPSHOT (all modules), eg 10.16.0-SNAPSHOT , you can use mvn versions:set -DnewVersion=10.16.0-SNAPSHOT and than try mvn deploy Please note that you can not override release version. wt., 14 cze 2022 o 10:00 Tamás Cservenák napisał(a): Howdy, So is the "peer not authenticated" error still sporadically happening? Qs: - can you use some LTS java instead of 18? (17 or 11?) - could you execute the build with -e (or -X but this will give you a LOT of logs) and paste the stack trace? - you sure you are directly accessing repo.a.o, no proxy or whatever in between your maven process and repo.a.o? HTH T On Tue, Jun 14, 2022 at 12:10 AM Rick Hillegas wrote: Thanks, Tamas. On your advice, I updated the top level pom to refer to version 26 of the parent apache pom. This caused the maven-antrun-plugin to object that a major upgrade had obsoleted the element. I was advised to change to . I did that too. However, I am still seeing "peer not authenticated" messages. On 6/13/22 11:15 AM, Tamás Cservenák wrote: Howdy, Well, sadly I see that svn tag is in place, but the very first observation I have is that due to ancient parent Apache POM version 10, you use ancient plugins despite the latest Maven being used. Please try to upgrade parent to current one (current version is 26). So in here https://svn.apache.org/repos/asf/db/derby/code/trunk/maven2/pom.xml make project/parent/version = 26 Parent version 10 you use is from 2011 hence you use plugins that are 11 years old or older, made for Maven2, and I really have no idea what kind of bug(s) may be hit here... Note: ASF parent 10 says java level is 1.4... so this may need some alignment as well... Also, why Java 18? Is it needed or is it just handy? (I'd go with some LTS rather) Other than that, given the sporadic nature of the error, I really can't say more, maybe some misbehaving proxy in between maven process and repo.apache.org? HTH Tamas On Mon, Jun 13, 2022 at 7:45 PM Rick Hillegas I need advice about how to move past a "peer not authenticated" error. I am trying to stage some 20 jars and corresponding poms via the following command: mvn -Dgpg.passphrase="my secret passphrase" clean deploy I am able to upload most of the artifacts, but the command eventually fails with a "peer not authenticated" error. The artifact which incurs this error is not consistent. I have tried this from two different locations (Palm Springs and San Francisco). But I can't get to the end of the upload without a "peer not authenticated" error: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy) on project derbyLocale_ko_KR: Failed to deploy artifacts: Could not transfer artifact org.apache.derby:derbyLocale_ko_KR:pom.asc:10.16.1.1 from/to apache.releases.https (https://repository.apache.org/service/local/staging/deploy/maven2): transfer failed for https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/derby/derbyLocale_ko_KR/10.16.1.1/derbyLocale_ko_KR-10.16.1.1.pom.asc : peer not authenticated -> [Help 1] Here is my environment: maven 3.8.5 OpenJDK Runtime Environment 18.9 (build 11+28) Based on some advice I found on the internet, I tried adding the following stanza to my top level pom: ... org.apache.maven.plugins maven-deploy-plugin 3 That does not fix the problem. Any help you can give me would be appreciated. Thanks, Rick - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: peer not authenticated error
Thanks for the additional advice, Tamas. Infra is going to restart the service on the Nexus end. See https://issues.apache.org/jira/browse/INFRA-23348 Maybe that will fix the problem. I'm sorry for sowing confusion about the Java version. I am using the GA release of Java 11. Here is the full output of java -version: openjdk version "11" 2018-09-25 OpenJDK Runtime Environment 18.9 (build 11+28) OpenJDK 64-Bit Server VM 18.9 (build 11+28, mixed mode) I haven't set up any proxies on my end. Thanks, -Rick On 6/14/22 12:59 AM, Tamás Cservenák wrote: Howdy, So is the "peer not authenticated" error still sporadically happening? Qs: - can you use some LTS java instead of 18? (17 or 11?) - could you execute the build with -e (or -X but this will give you a LOT of logs) and paste the stack trace? - you sure you are directly accessing repo.a.o, no proxy or whatever in between your maven process and repo.a.o? HTH T On Tue, Jun 14, 2022 at 12:10 AM Rick Hillegas wrote: Thanks, Tamas. On your advice, I updated the top level pom to refer to version 26 of the parent apache pom. This caused the maven-antrun-plugin to object that a major upgrade had obsoleted the element. I was advised to change to . I did that too. However, I am still seeing "peer not authenticated" messages. On 6/13/22 11:15 AM, Tamás Cservenák wrote: Howdy, Well, sadly I see that svn tag is in place, but the very first observation I have is that due to ancient parent Apache POM version 10, you use ancient plugins despite the latest Maven being used. Please try to upgrade parent to current one (current version is 26). So in here https://svn.apache.org/repos/asf/db/derby/code/trunk/maven2/pom.xml make project/parent/version = 26 Parent version 10 you use is from 2011 hence you use plugins that are 11 years old or older, made for Maven2, and I really have no idea what kind of bug(s) may be hit here... Note: ASF parent 10 says java level is 1.4... so this may need some alignment as well... Also, why Java 18? Is it needed or is it just handy? (I'd go with some LTS rather) Other than that, given the sporadic nature of the error, I really can't say more, maybe some misbehaving proxy in between maven process and repo.apache.org? HTH Tamas On Mon, Jun 13, 2022 at 7:45 PM Rick Hillegas wrote: I need advice about how to move past a "peer not authenticated" error. I am trying to stage some 20 jars and corresponding poms via the following command: mvn -Dgpg.passphrase="my secret passphrase" clean deploy I am able to upload most of the artifacts, but the command eventually fails with a "peer not authenticated" error. The artifact which incurs this error is not consistent. I have tried this from two different locations (Palm Springs and San Francisco). But I can't get to the end of the upload without a "peer not authenticated" error: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy) on project derbyLocale_ko_KR: Failed to deploy artifacts: Could not transfer artifact org.apache.derby:derbyLocale_ko_KR:pom.asc:10.16.1.1 from/to apache.releases.https (https://repository.apache.org/service/local/staging/deploy/maven2): transfer failed for https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/derby/derbyLocale_ko_KR/10.16.1.1/derbyLocale_ko_KR-10.16.1.1.pom.asc : peer not authenticated -> [Help 1] Here is my environment: maven 3.8.5 OpenJDK Runtime Environment 18.9 (build 11+28) Based on some advice I found on the internet, I tried adding the following stanza to my top level pom: ... org.apache.maven.plugins maven-deploy-plugin 3 That does not fix the problem. Any help you can give me would be appreciated. Thanks, Rick - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: peer not authenticated error
Hi, In your project I see: derby-project ALPHA_VERSION Please try to change project version to SNAPSHOT (all modules), eg 10.16.0-SNAPSHOT , you can use mvn versions:set -DnewVersion=10.16.0-SNAPSHOT and than try mvn deploy Please note that you can not override release version. wt., 14 cze 2022 o 10:00 Tamás Cservenák napisał(a): > Howdy, > > So is the "peer not authenticated" error still sporadically happening? > > Qs: > - can you use some LTS java instead of 18? (17 or 11?) > - could you execute the build with -e (or -X but this will give you a LOT > of logs) and paste the stack trace? > - you sure you are directly accessing repo.a.o, no proxy or whatever in > between your maven process and repo.a.o? > > HTH > T > > > > On Tue, Jun 14, 2022 at 12:10 AM Rick Hillegas > wrote: > > > Thanks, Tamas. On your advice, I updated the top level pom to refer to > > version 26 of the parent apache pom. This caused the maven-antrun-plugin > > to object that a major upgrade had obsoleted the element. I was > > advised to change to . I did that too. However, I am > > still seeing "peer not authenticated" messages. > > > > On 6/13/22 11:15 AM, Tamás Cservenák wrote: > > > Howdy, > > > > > > Well, sadly I see that svn tag is in place, but the very first > > observation > > > I have is that due to ancient parent Apache POM version 10, you use > > ancient > > > plugins despite the latest Maven being used. Please try to upgrade > parent > > > to current one (current version is 26). > > > > > > So in here > > > https://svn.apache.org/repos/asf/db/derby/code/trunk/maven2/pom.xml > > > make project/parent/version = 26 > > > > > > Parent version 10 you use is from 2011 hence you use plugins that are > 11 > > > years old or older, made for Maven2, and I really have no idea what > kind > > of > > > bug(s) may be hit here... > > > Note: ASF parent 10 says java level is 1.4... so this may need some > > > alignment as well... Also, why Java 18? Is it needed or is it just > handy? > > > (I'd go with some LTS rather) > > > > > > Other than that, given the sporadic nature of the error, I really can't > > say > > > more, maybe some misbehaving proxy in between maven process and > > > repo.apache.org? > > > > > > HTH > > > Tamas > > > > > > > > > > > > On Mon, Jun 13, 2022 at 7:45 PM Rick Hillegas > > > > wrote: > > > > > >> I need advice about how to move past a "peer not authenticated" error. > > >> > > >> I am trying to stage some 20 jars and corresponding poms via the > > >> following command: > > >> > > >> mvn -Dgpg.passphrase="my secret passphrase" clean deploy > > >> > > >> I am able to upload most of the artifacts, but the command eventually > > >> fails with a "peer not authenticated" error. The artifact which incurs > > >> this error is not consistent. I have tried this from two different > > >> locations (Palm Springs and San Francisco). But I can't get to the end > > >> of the upload without a "peer not authenticated" error: > > >> > > >> [ERROR] Failed to execute goal > > >> org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy > (default-deploy) > > >> on project derbyLocale_ko_KR: Failed to deploy artifacts: Could not > > >> transfer artifact org.apache.derby:derbyLocale_ko_KR:pom.asc:10.16.1.1 > > >> from/to apache.releases.https > > >> (https://repository.apache.org/service/local/staging/deploy/maven2): > > >> transfer failed for > > >> > > >> > > > https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/derby/derbyLocale_ko_KR/10.16.1.1/derbyLocale_ko_KR-10.16.1.1.pom.asc > > : > > >> > > >> peer not authenticated -> [Help 1] > > >> > > >> Here is my environment: > > >> > > >> maven 3.8.5 > > >> > > >> OpenJDK Runtime Environment 18.9 (build 11+28) > > >> > > >> > > >> Based on some advice I found on the internet, I tried adding the > > >> following stanza to my top level pom: > > >> > > >> > > >> > > >> > > >> ... > > >> > > >> > > >> org.apache.maven.plugins > > >> maven-deploy-plugin > > >> > > >> 3 > > >> > > >> > > >> > > >> > > >> > > >> > > >> That does not fix the problem. Any help you can give me would be > > >> appreciated. > > >> > > >> Thanks, > > >> Rick > > >> > > >> > > >> - > > >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > >> For additional commands, e-mail: users-h...@maven.apache.org > > >> > > >> > > > > > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > -- Sławomir Jaranowski
Re: peer not authenticated error
Howdy, So is the "peer not authenticated" error still sporadically happening? Qs: - can you use some LTS java instead of 18? (17 or 11?) - could you execute the build with -e (or -X but this will give you a LOT of logs) and paste the stack trace? - you sure you are directly accessing repo.a.o, no proxy or whatever in between your maven process and repo.a.o? HTH T On Tue, Jun 14, 2022 at 12:10 AM Rick Hillegas wrote: > Thanks, Tamas. On your advice, I updated the top level pom to refer to > version 26 of the parent apache pom. This caused the maven-antrun-plugin > to object that a major upgrade had obsoleted the element. I was > advised to change to . I did that too. However, I am > still seeing "peer not authenticated" messages. > > On 6/13/22 11:15 AM, Tamás Cservenák wrote: > > Howdy, > > > > Well, sadly I see that svn tag is in place, but the very first > observation > > I have is that due to ancient parent Apache POM version 10, you use > ancient > > plugins despite the latest Maven being used. Please try to upgrade parent > > to current one (current version is 26). > > > > So in here > > https://svn.apache.org/repos/asf/db/derby/code/trunk/maven2/pom.xml > > make project/parent/version = 26 > > > > Parent version 10 you use is from 2011 hence you use plugins that are 11 > > years old or older, made for Maven2, and I really have no idea what kind > of > > bug(s) may be hit here... > > Note: ASF parent 10 says java level is 1.4... so this may need some > > alignment as well... Also, why Java 18? Is it needed or is it just handy? > > (I'd go with some LTS rather) > > > > Other than that, given the sporadic nature of the error, I really can't > say > > more, maybe some misbehaving proxy in between maven process and > > repo.apache.org? > > > > HTH > > Tamas > > > > > > > > On Mon, Jun 13, 2022 at 7:45 PM Rick Hillegas > > wrote: > > > >> I need advice about how to move past a "peer not authenticated" error. > >> > >> I am trying to stage some 20 jars and corresponding poms via the > >> following command: > >> > >> mvn -Dgpg.passphrase="my secret passphrase" clean deploy > >> > >> I am able to upload most of the artifacts, but the command eventually > >> fails with a "peer not authenticated" error. The artifact which incurs > >> this error is not consistent. I have tried this from two different > >> locations (Palm Springs and San Francisco). But I can't get to the end > >> of the upload without a "peer not authenticated" error: > >> > >> [ERROR] Failed to execute goal > >> org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy) > >> on project derbyLocale_ko_KR: Failed to deploy artifacts: Could not > >> transfer artifact org.apache.derby:derbyLocale_ko_KR:pom.asc:10.16.1.1 > >> from/to apache.releases.https > >> (https://repository.apache.org/service/local/staging/deploy/maven2): > >> transfer failed for > >> > >> > https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/derby/derbyLocale_ko_KR/10.16.1.1/derbyLocale_ko_KR-10.16.1.1.pom.asc > : > >> > >> peer not authenticated -> [Help 1] > >> > >> Here is my environment: > >> > >> maven 3.8.5 > >> > >> OpenJDK Runtime Environment 18.9 (build 11+28) > >> > >> > >> Based on some advice I found on the internet, I tried adding the > >> following stanza to my top level pom: > >> > >> > >> > >> > >> ... > >> > >> > >> org.apache.maven.plugins > >> maven-deploy-plugin > >> > >> 3 > >> > >> > >> > >> > >> > >> > >> That does not fix the problem. Any help you can give me would be > >> appreciated. > >> > >> Thanks, > >> Rick > >> > >> > >> - > >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > >> For additional commands, e-mail: users-h...@maven.apache.org > >> > >> > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: peer not authenticated error
Thanks, Tamas. On your advice, I updated the top level pom to refer to version 26 of the parent apache pom. This caused the maven-antrun-plugin to object that a major upgrade had obsoleted the element. I was advised to change to . I did that too. However, I am still seeing "peer not authenticated" messages. On 6/13/22 11:15 AM, Tamás Cservenák wrote: Howdy, Well, sadly I see that svn tag is in place, but the very first observation I have is that due to ancient parent Apache POM version 10, you use ancient plugins despite the latest Maven being used. Please try to upgrade parent to current one (current version is 26). So in here https://svn.apache.org/repos/asf/db/derby/code/trunk/maven2/pom.xml make project/parent/version = 26 Parent version 10 you use is from 2011 hence you use plugins that are 11 years old or older, made for Maven2, and I really have no idea what kind of bug(s) may be hit here... Note: ASF parent 10 says java level is 1.4... so this may need some alignment as well... Also, why Java 18? Is it needed or is it just handy? (I'd go with some LTS rather) Other than that, given the sporadic nature of the error, I really can't say more, maybe some misbehaving proxy in between maven process and repo.apache.org? HTH Tamas On Mon, Jun 13, 2022 at 7:45 PM Rick Hillegas wrote: I need advice about how to move past a "peer not authenticated" error. I am trying to stage some 20 jars and corresponding poms via the following command: mvn -Dgpg.passphrase="my secret passphrase" clean deploy I am able to upload most of the artifacts, but the command eventually fails with a "peer not authenticated" error. The artifact which incurs this error is not consistent. I have tried this from two different locations (Palm Springs and San Francisco). But I can't get to the end of the upload without a "peer not authenticated" error: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy) on project derbyLocale_ko_KR: Failed to deploy artifacts: Could not transfer artifact org.apache.derby:derbyLocale_ko_KR:pom.asc:10.16.1.1 from/to apache.releases.https (https://repository.apache.org/service/local/staging/deploy/maven2): transfer failed for https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/derby/derbyLocale_ko_KR/10.16.1.1/derbyLocale_ko_KR-10.16.1.1.pom.asc: peer not authenticated -> [Help 1] Here is my environment: maven 3.8.5 OpenJDK Runtime Environment 18.9 (build 11+28) Based on some advice I found on the internet, I tried adding the following stanza to my top level pom: ... org.apache.maven.plugins maven-deploy-plugin 3 That does not fix the problem. Any help you can give me would be appreciated. Thanks, Rick - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: peer not authenticated error
Howdy, Well, sadly I see that svn tag is in place, but the very first observation I have is that due to ancient parent Apache POM version 10, you use ancient plugins despite the latest Maven being used. Please try to upgrade parent to current one (current version is 26). So in here https://svn.apache.org/repos/asf/db/derby/code/trunk/maven2/pom.xml make project/parent/version = 26 Parent version 10 you use is from 2011 hence you use plugins that are 11 years old or older, made for Maven2, and I really have no idea what kind of bug(s) may be hit here... Note: ASF parent 10 says java level is 1.4... so this may need some alignment as well... Also, why Java 18? Is it needed or is it just handy? (I'd go with some LTS rather) Other than that, given the sporadic nature of the error, I really can't say more, maybe some misbehaving proxy in between maven process and repo.apache.org? HTH Tamas On Mon, Jun 13, 2022 at 7:45 PM Rick Hillegas wrote: > I need advice about how to move past a "peer not authenticated" error. > > I am trying to stage some 20 jars and corresponding poms via the > following command: > >mvn -Dgpg.passphrase="my secret passphrase" clean deploy > > I am able to upload most of the artifacts, but the command eventually > fails with a "peer not authenticated" error. The artifact which incurs > this error is not consistent. I have tried this from two different > locations (Palm Springs and San Francisco). But I can't get to the end > of the upload without a "peer not authenticated" error: > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy) > on project derbyLocale_ko_KR: Failed to deploy artifacts: Could not > transfer artifact org.apache.derby:derbyLocale_ko_KR:pom.asc:10.16.1.1 > from/to apache.releases.https > (https://repository.apache.org/service/local/staging/deploy/maven2): > transfer failed for > > https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/derby/derbyLocale_ko_KR/10.16.1.1/derbyLocale_ko_KR-10.16.1.1.pom.asc: > > peer not authenticated -> [Help 1] > > Here is my environment: > >maven 3.8.5 > >OpenJDK Runtime Environment 18.9 (build 11+28) > > > Based on some advice I found on the internet, I tried adding the > following stanza to my top level pom: > > > > >... > > > org.apache.maven.plugins > maven-deploy-plugin > > 3 > > > > > > > That does not fix the problem. Any help you can give me would be > appreciated. > > Thanks, > Rick > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
