Hi.. I'm also having a problem deploying (Batch) to the Jakarta Nexus for the first time, getting a "401 Unauthorized"
(I don't see this answered in an earlier message/thread, hopefully I didn't miss it and hopefully OK to pile on this one..)
Some details:
1. Trying to deploy versions: 2.0.0-M1
3. I'm using the 1.0.6 parent POM
4. I deploy manually myself (not w/ Jenkins) as: "skurz@xxxxxxxxxx"
5. Using command:
mvn clean deploy -DskipTests=true -Pperform-release # my profile tweaks the GPG part a bit
Appreciate advice on the next step, where to open an issue, and again sorry if this was already mentioned.
Thanks,
------------------------------------------------------
Scott Kurz
WebSphere Batch and Developer Experience
skurz@xxxxxxxxxx
--------------------------------------------------------
----- Original message -----
From: arjan tijms <arjan.tijms@xxxxxxxxx>
Sent by: ee4j-pmc-bounces@xxxxxxxxxxx
To: EE4J PMC Discussions <ee4j-pmc@xxxxxxxxxxx>
Cc:
Subject: [EXTERNAL] Re: [ee4j-pmc] Migration to Jakarta installation of Nexus
Date: Fri, Feb 14, 2020 4:27 PM
Yes, we updated to the 1.0.6 parent pom to pickup the new staging repo information. The logs show that it is trying to connect to the
jakarta.oss.sonatype.org service:
That first part looks to be correct, for comparison this is what I get for instance for Jakarta Messaging:
[INFO] Performing remote staging...
[INFO]
[INFO] * Remote staging into staging profile ID "3c72217114e8"
[INFO] * Created staging repository with ID "jakartajms-1000".
[INFO] * Uploading locally staged artifacts to profile jakarta.jms
[INFO] * Upload of locally staged artifacts finished.
[INFO] * Closing staging repository with ID "jakartajms-1000".
The full command I use for staging is:
mvn -U -C -s /home/jenkins/.m2/settings.xml -DskipTests -Ddoclint=none -Poss-release clean package source:jar javadoc:jar gpg:sign install:install nexus-staging:deploy --batch-mode -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn
Kind regards,
Arjan