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
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
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
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
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,
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
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
