Re: [ee4j-build] Problem releasing XML Registries (JAXR)

["Kevin Sutter" <sutter@xxxxxxxxxx>]

Even with these strange
errors, maybe the release processing still worked?

https://repo.maven.apache.org/maven2/jakarta/xml/registry/jakarta.xml.registry-api/1.0.10/


---------------------------------------------------
Kevin Sutter 
STSM, MicroProfile and Jakarta EE architect
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn: https://www.linkedin.com/in/kevinwsutter



From:
       Jim
Krueger <jckofbyron@xxxxxxxxx>
To:
       EE4J
build and releng discussions <ee4j-build@xxxxxxxxxxx>
Date:
       09/05/2019
05:16 PM
Subject:
       [EXTERNAL]
[ee4j-build] Problem releasing XML Registries (JAXR)
Sent
by:        ee4j-build-bounces@xxxxxxxxxxx

---

Hi,
I've hit a problem releasing the XML
Registries (JAXR) project running the recommended script https://jenkins.eclipse.org/jakartaee-stable/job/nexus-release-by-project/configure

I first ran the job to see the list of
id's (mvnq ${NEXUS_PLUGIN_PARAMS} ${NEXUS_PLUGIN}:rc-list)  and saw
the following output:  https://jenkins.eclipse.org/jakartaee-stable/job/nexus-release-by-project/4/console

[INFO] jakartaenterprisedeploy-1011
CLOSED   Close staging repository automatically for uploaded bundle.
[INFO] jakartaxmlregistry-1005 CLOSED   jakarta.xml.registry:xml.registry-api-parent:1.0.10

So I then used the given id (jakartaxmlregistry-1005)
and attempted the release job
(mvnq -DstagingRepositoryId="$ID" ${NEXUS_PLUGIN_PARAMS} ${NEXUS_PLUGIN}:rc-release)
but this job failed: https://jenkins.eclipse.org/jakartaee-stable/job/nexus-release-by-project/5/console

[INFO] RC-Releasing staging repository with IDs=[jakartaxmlregistry-1005]

Waiting for operation to complete...
....

[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  29.472 s
[INFO] Finished at: 2019-09-05T21:34:44Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.7:rc-release
(default-cli) on project standalone-pom: Execution default-cli of goal
org.sonatype.plugins:nexus-staging-maven-plugin:1.6.7:rc-release failed:
A message body reader for Java class com.sonatype.nexus.staging.api.dto.StagingProfileRepositoryDTO,
and Java type class com.sonatype.nexus.staging.api.dto.StagingProfileRepositoryDTO,
and MIME media type text/html was not found -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the
-e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.

If I run the list job again I no
longer see jakartaxmlregistry in the list so I assume I cannot re-run the
release job.

Has anyone seen this failure or know
how to resolve?

Thanks
 _______________________________________________
ee4j-build mailing list
ee4j-build@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-build