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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

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

From: "Kevin Sutter" <sutter@xxxxxxxxxx>
Date: Sat, 7 Sep 2019 14:42:08 +0000
Delivered-to: ee4j-build@xxxxxxxxxxx
List-archive: <https://www.eclipse.org/mailman/private/ee4j-build>
List-help: <mailto:ee4j-build-request@eclipse.org?subject=help>
List-subscribe: <https://www.eclipse.org/mailman/listinfo/ee4j-build>, <mailto:ee4j-build-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://www.eclipse.org/mailman/options/ee4j-build>, <mailto:ee4j-build-request@eclipse.org?subject=unsubscribe>

Jim,
I think we need to utilize Romain's suggestion and update that issue... Since it's Saturday and I'm not sure if you are following this today, I will go ahead and add a comment to the issue. These missing files are an immediate issue. When I try to build the overall jakartaee-api jar file, I am getting the following error:

[ERROR] Failed to execute goal on project jakarta.jakartaee-api: Could not resolve dependencies for project jakarta.platform:jakarta.jakartaee-api:jar:8.0.0-SNAPSHOT: Failed to collect dependencies at jakarta.xml.registry:jakarta.xml.registry-api:jar:1.0.10: Failed to read artifact descriptor for jakarta.xml.registry:jakarta.xml.registry-api:jar:1.0.10: Could not find artifact jakarta.xml.registry:xml.registry-api-parent:pom:1.0.10 in central (https://repo.maven.apache.org/maven2) -> [Help 1]

So, we need to get the repo correctly populated. Thanks!

---------------------------------------------------
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: Romain Grecourt <romain.grecourt@xxxxxxxxxx>
To: ee4j-build@xxxxxxxxxxx
Date: 09/06/2019 09:16 PM
Subject: [EXTERNAL] Re: [ee4j-build] Problem releasing XML Registries (JAXR)
Sent by: ee4j-build-bounces@xxxxxxxxxxx

On 9/6/19 1:07 PM, Jim Krueger wrote:
Thanks. I already filed a bug a few hours ago: https://issues.sonatype.org/browse/OSSRH-51386
The issue you created does not describe this problem explicitly.
Tell them that some released artifacts are missing on Maven central, with the links I shared below.

On Fri, Sep 6, 2019 at 2:47 PM Romain Grecourt <romain.grecourt@xxxxxxxxxx> wrote:
I was wrong with my previous assumption, in the script below ARTIFACT_ID would resolve to the parent pom artifactId which explains why the staging repository description included "xml.registry-parent".

I see the missing artifacts in OSSRH staging and in the OSSRH local release:
https://oss.sonatype.org/content/repositories/staging/jakarta/xml/registry/xml.registry-api-parent/1.0.10/xml.registry-api-parent-1.0.10.pom
https://oss.sonatype.org/content/repositories/staging/jakarta/xml/registry/xml-registries-spec/1.0.10/xml-registries-spec-1.0.10.zip
https://oss.sonatype.org/service/local/repositories/releases/content/jakarta/xml/registry/xml.registry-api-parent/1.0.10/xml.registry-api-parent-1.0.10.pom
https://oss.sonatype.org/service/local/repositories/releases/content/jakarta/xml/registry/xml-registries-spec/1.0.10/xml-registries-spec-1.0.10.zip

Something probably went wrong on Sonatype's side.
You should file a bug at https://issues.sonatype.org/projects/OSSRH/issuesand ask them to look into the missing artifacts.

On 9/6/19 11:25 AM, Jim Krueger wrote:
Here is the scripts to deploy the artifacts and also the nexus staging job.

JAXR_API_Release: https://jenkins.eclipse.org/jakartaee-stable/job/JAXR-API-Release/configure
#!/bin/bash -ex

TOOLS_PREFIX='/opt/tools'
JAVA_PREFIX="${TOOLS_PREFIX}/java/oracle"
MVN_HOME="${TOOLS_PREFIX}/apache-maven/latest"
JAVA_HOME="${JAVA_PREFIX}/jdk-8/latest"
PATH="${MVN_HOME}/bin:${JAVA_HOME}/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"

# Maven plugins
VERSIONS_PLUGIN='org.codehaus.mojo:versions-maven-plugin:2.7'
HELP_PLUGIN='org.apache.maven.plugins:maven-help-plugin:3.1.0'

# Check whether top level pom.xml contains SNAPSHOT version
if ! grep '<version>' pom.xml | grep 'SNAPSHOT' ; then
echo '-[ Missing SNAPSHOT version in POM! ]-------------------------------------------'
exit 1
fi

# Compute release versions
SNAPSHOT_VERSION=`mvn -B ${HELP_PLUGIN}:evaluate -Dexpression=project.version 2> /dev/null | grep -E '^[0-9]+(\.[0-9]+)+-SNAPSHOT$'`

if [ -z "${RELEASE_VERSION}" ]; then
if [ -z ${SNAPSHOT_VERSION} ]; then
echo '-[ Missing required snapshot version number! ]----------------------------------'
fi
RELEASE_VERSION=`echo ${SNAPSHOT_VERSION} | sed -e 's/-SNAPSHOT//'`
fi

# Bash specific code
if [ -z "${NEXT_VERSION}" ]; then
NEXT_VERSION=`echo ${RELEASE_VERSION} | sed -e 's/$[0-9][0-9]*\.[0-9][0-9]*$.*/\1/'`
set -f
NEXT_COMPONENTS=(${RELEASE_VERSION//\./ })
LAST_INDEX=$((${#NEXT_COMPONENTS[@]} - 1))
NEXT_COMPONENTS[${LAST_INDEX}]=$((${NEXT_COMPONENTS[${LAST_INDEX}]} + 1))
NEXT_VERSION=`echo ${NEXT_COMPONENTS[@]} | tr ' ' '.'`'-SNAPSHOT'
fi

RELEASE_TAG="${RELEASE_VERSION}"
RELEASE_BRANCH="${RELEASE_VERSION}"-BRANCH

echo "Current version: ${SNAPSHOT_VERSION}"
echo "Release version: ${RELEASE_VERSION}"
echo "Next version: ${NEXT_VERSION}"
echo "Release tag: ${RELEASE_TAG}"

if [ -z "${SNAPSHOT_VERSION}" -o -z "${RELEASE_VERSION}" -o -z "${NEXT_VERSION}" ]; then
echo '-[ Missing required version numbers! ]------------------------------------------'
exit 1
fi

if [ ${DRY_RUN} = 'true' ]; then
echo '-[ Dry run turned on ]----------------------------------------------------------'
MVN_DEPLOY_ARGS=''
echo '-[ Skipping GitHub branch and tag checks ]--------------------------------------'
else
MVN_DEPLOY_ARGS='deploy:deploy'
GIT_ORIGIN=`git remote`
echo '-[ Prepare branch ]-------------------------------------------------------------'
if [[ -n `git branch -r | grep "${GIT_ORIGIN}/${RELEASE_BRANCH}"` ]]; then
if [ "${OVERWRITE}" = 'true' ]; then
echo "${GIT_ORIGIN}/${RELEASE_BRANCH} branch already exists, deleting"
git push --delete origin "${RELEASE_BRANCH}" && true
else
echo "Error: ${GIT_ORIGIN}/${RELEASE_BRANCH} branch already exists"
exit 1
fi
fi
echo '-[ Release tag cleanup ]--------------------------------------------------------'
if [[ -n `git ls-remote --tags ${GIT_ORIGIN} | grep "${RELEASE_TAG}"` ]]; then
if [ "${OVERWRITE}" = 'true' ]; then
echo "${RELEASE_TAG} tag already exists, deleting"
git push --delete origin "${RELEASE_TAG}" && true
else
echo "Error: ${RELEASE_TAG} tag already exists"
exit 1
fi
fi
fi

# Always delete local branch if exists
git branch --delete "${RELEASE_BRANCH}" && true
git checkout -b ${RELEASE_BRANCH}
# Always delete local tag if exists
git tag --delete "${RELEASE_TAG}" && true

# Setup jakartaee-stable-bot account information
git config --global user.email "jakartaee-stable-bot@xxxxxxxxxxx"
git config --global user.name"Eclipse jakartaee-stable Bot"
# Workaround: GPG initialization
gpg --batch --import ${KEYRING}
for fpr in $(gpg --list-keys --with-colons | awk -F: '/fpr:/ {print $10}' | sort -u);
do
echo -e "5\ny\n" | gpg --batch --command-fd 0 --expert --edit-key $fpr trust;
done

# Project identifiers
ARTIFACT_ID=$(mvn -B ${HELP_PLUGIN}:evaluate -Dexpression=project.artifactId | grep -Ev '(^\[)')
GROUP_ID=$(mvn -B ${HELP_PLUGIN}:evaluate -Dexpression=project.groupId | grep -Ev '(^\[)')

echo '-[ Set release version ]--------------------------------------------------------'
# Set release version
mvn -U -C -B \
-DnewVersion="${RELEASE_VERSION}" \
-DgenerateBackupPoms=false \
clean ${VERSIONS_PLUGIN}:set

echo '-[ Commit modified pom.xml files ]----------------------------------------------'
POM_FILES=`git status | grep -E 'modified:.*pom\.xml' | sed -e 's/[[:space:]][[:space:]]*modified:[[:space:]][[:space:]]*//'`
git add ${POM_FILES} && \
git commit -m "Prepare release ${GROUP_ID}:${ARTIFACT_ID}:${RELEASE_VERSION}"

##### Temporary workaround begin
#NEXUS_PLUGIN='org.sonatype.plugins:nexus-staging-maven-plugin:1.6.7'
#NEXUS_PLUGIN_PARAMS='-DnexusUrl=https://oss.sonatype.org/-DserverId=ossrh'
#STAGING_PROFILE_ID='7edbe315063867'
#STAGING_DESC="jakartaxmlrpc-${BUILD_ID}"
## Open a new staging repo
#mvn -B ${NEXUS_PLUGIN_PARAMS} ${NEXUS_PLUGIN}:rc-open \
# -DstagingProfileId="${STAGING_PROFILE_ID}" \
# -DstagingDescription="${STAGING_DESC}"
## Get the ID of the newly created staging repo
#STAGING_REPO_ID=$(mvn -B ${NEXUS_PLUGIN_PARAMS} ${NEXUS_PLUGIN}:rc-list | \
# egrep "^\[INFO\] .*\-[0-9]+[ ]+OPEN[ ]+.*${STAGING_DESC}" | \
# awk '{print $2}' | head -1)
#echo "STAGING_REPO_ID=${STAGING_REPO_ID}"
##### Temporary workaround end

echo '-[ Deploy artifacts to staging repository ]-------------------------------------'
# -DstagingRepositoryId="${STAGING_REPO_ID}" \
mvn -U -C -B \
-DskipTests -DadditionalJOption=-Xdoclint:none -Poss-release -Pstaging \
clean package source:jar javadoc:jar gpg:sign install:install ${MVN_DEPLOY_ARGS}

echo '-[ Tag release ]----------------------------------------------------------------'
git tag "${RELEASE_TAG}" -m "Release ${GROUP_ID}:${ARTIFACT_ID}:${RELEASE_VERSION}"

echo '-[ Set next snapshot version ]--------------------------------------------------'
mvn -U -C -B \
-DnewVersion="${NEXT_VERSION}" \
-DgenerateBackupPoms=false \
clean ${VERSIONS_PLUGIN}:set

echo '-[ Commit modified pom.xml files ]----------------------------------------------'
POM_FILES=`git status | grep -E 'modified:.*pom\.xml' | sed -e 's/[[:space:]][[:space:]]*modified:[[:space:]][[:space:]]*//'`
git add ${POM_FILES} && \
git commit -m "Prepare next development cycle for ${NEXT_VERSION}"

if [ ${DRY_RUN} = 'true' ]; then
echo '-[ Skipping GitHub update ]-----------------------------------------------------'
else
echo '-[ Push branch and tag to GitHub ]----------------------------------------------'
git push origin "${RELEASE_BRANCH}"
git push origin "${RELEASE_TAG}"
fi

artaee-stable/job/nexus-staging/configure
#!/bin/bash -ex

TOOLS_PREFIX='/opt/tools'
JAVA_PREFIX="${TOOLS_PREFIX}/java/oracle"
MVN_HOME="${TOOLS_PREFIX}/apache-maven/latest"
JAVA_HOME="${JAVA_PREFIX}/jdk-8/latest"
PATH="${MVN_HOME}/bin:${JAVA_HOME}/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"

# Maven plugins
HELP_PLUGIN='org.apache.maven.plugins:maven-help-plugin:3.1.0'
NEXUS_PLUGIN='org.sonatype.plugins:nexus-staging-maven-plugin:1.6.7'
NEXUS_PLUGIN_PARAMS='-DnexusUrl=https://oss.sonatype.org/-DserverId=ossrh'

case "${PROJECT}" in

'Enterprise-Deployment')
GIT_REPO='git@xxxxxxxxxx:eclipse-ee4j/enterprise-deployment.git'
STAGING_NAME='jakartaenterprisedeploy'
;;

'JAX-RPC-API')
GIT_REPO='git@xxxxxxxxxx:eclipse-ee4j/jax-rpc-api.git'
STAGING_NAME='jakartaxmlrpc'
;;

'JAXR-API')
GIT_REPO='git@xxxxxxxxxx:eclipse-ee4j/jaxr-api.git'
STAGING_NAME='jakartaxmlregistry'
;;

'Management-API')
GIT_REPO='git@xxxxxxxxxx:eclipse-ee4j/management-api.git'
STAGING_NAME='jakartamanagementj2ee'
;;

*)
if [ "${ACTION}" != 'list' ]; then
echo '-[ Error ]----------------------------------------------------------------------'
echo 'No project selected, exitting.'
exit 1
else
GIT_REPO=''
fi
;;

esac

if [ -n "${GIT_REPO}" ]; then
echo '-[ Cloning Project Repository ]-------------------------------------------------'
git clone ${GIT_REPO} . && git checkout ${BRANCH}
echo '-[ Reading project identifiers ]------------------------------------------------'
if [ -n "${BUILD_DIR}" ]; then
cd ${BUILD_DIR}
fi
# Project identifiers
ARTIFACT_ID=$(mvn -B ${HELP_PLUGIN}:evaluate -Dexpression=project.artifactId | grep -Ev '(^\[)')
GROUP_ID=$(mvn -B ${HELP_PLUGIN}:evaluate -Dexpression=project.groupId | grep -Ev '(^\[)')
fi

echo "Project: ${PROJECT} API"
echo "Action: ${ACTION}"
echo "Repository ID prefix: ${STAGING_NAME}"
echo "Artifact: ${GROUP_ID}:${ARTIFACT_ID}"

case "${ACTION}" in

'list')

echo '-[ Profiles List ]--------------------------------------------------------------'
mvn -B ${NEXUS_PLUGIN_PARAMS} ${NEXUS_PLUGIN}:rc-list-profiles
echo '-[ Staging Repository List ]----------------------------------------------------'
if [ -n "${STAGING_NAME}" ]; then
mvn -B ${NEXUS_PLUGIN_PARAMS} ${NEXUS_PLUGIN}:rc-list | egrep "^\[INFO\] ${STAGING_NAME}\-[0-9]+[ ]+[A-Z]+[ ]" || true
else
mvn -B ${NEXUS_PLUGIN_PARAMS} ${NEXUS_PLUGIN}:rc-list
fi
;;

'close')

if [ -z "${VERSION}" ]; then
echo '-[ Missing version number ]-----------------------------------------------------'
exit 1
fi
STAGING_DESC="${GROUP_ID}:${ARTIFACT_ID}:${VERSION}"
echo "Project description: ${STAGING_DESC}"
echo '-[ Searching for open deployment ]----------------------------------------------'

# Get the ID of the opem staging repository
# if [ "${PROJECT}" = 'JAX-RPC-API' ]; then
# STAGING_REPO_ID=$(mvn -B ${NEXUS_PLUGIN_PARAMS} ${NEXUS_PLUGIN}:rc-list | \
# egrep "^\[INFO\] .*\-[0-9]+[ ]+OPEN[ ]+.*${STAGING_NAME}" | \
# awk '{print $2}' | head -1)
# else
STAGING_REPO_ID=$(mvn -B ${NEXUS_PLUGIN_PARAMS} ${NEXUS_PLUGIN}:rc-list | \
egrep "^\[INFO\] ${STAGING_NAME}\-[0-9]+[ ]+OPEN[ ]" | \
awk '{print $2}' | head -1)
# fi
echo "Nexus staging repository ID: ${STAGING_REPO_ID}"

if [ -n "${STAGING_REPO_ID}" ]; then
echo '-[ Closing Nexus staging repository ]-------------------------------------------'
mvn -B ${NEXUS_PLUGIN_PARAMS} ${NEXUS_PLUGIN}:rc-close \
-DstagingRepositoryId="${STAGING_REPO_ID}" \
-DstagingDescription="${STAGING_DESC}"
else
echo '-[ Delpoyment '${STAGING_NAME}' was not found ]------------------------------------'
fi
;;

'drop')

if [ -z "${VERSION}" ]; then
echo '-[ Searching for deployments ]----------------------------------------------'
for REPO_ID in $(mvn -B ${NEXUS_PLUGIN_PARAMS} ${NEXUS_PLUGIN}:rc-list | \
egrep "^\[INFO\] ${STAGING_NAME}\-[0-9]+[ ]+[A-Z]+[ ]" | \
awk '{print $2}' | head -1); do
echo '-[ Dropping Nexus staging repository ]------------------------------------------'
echo "Deployment: ${REPO_ID}"
mvn -B ${NEXUS_PLUGIN_PARAMS} ${NEXUS_PLUGIN}:rc-drop \
-DstagingRepositoryId="${REPO_ID}"
done
else
mvn -B ${NEXUS_PLUGIN_PARAMS} ${NEXUS_PLUGIN}:rc-drop \
-DstagingRepositoryId="${VERSION}"
fi
;;

release)
echo '-[ Action denied for security reasons ]-------------------------------------'
;;

esac

On Fri, Sep 6, 2019 at 1:00 PM Lukas Jungmann <lukas.jungmann@xxxxxxxxxx> wrote:

on a side note: make sure the 'spec' artifact won't make it to central;
AFAIK it is also not allowed to appear on staging repo...

thanks,
--lukas

On 9/6/19 7:57 PM, Romain Grecourt wrote:
> On 9/6/19 10:08 AM, Jim Krueger wrote:
>> I have created Sonatype issue
>> https://issues.sonatype.org/browse/OSSRH-51386for this problem. We
>> need to understand why the parent pom's for management and jaxr were
>> not deployed. Beyond that, the partial release that was performed
>> yesterday has left both projects in a state where maven central may
>> need to be cleaned up before any new attempts can be made.
> I'm not sure how the release jobs are setup, but you had a staging
> repository with a description that mentioned the parent pom:
>
> [INFO] jakartaxmlregistry-1005 CLOSED
> jakarta.xml.registry:xml.registry-api-parent:1.0.10
>
> This feels like it's not a side effect but rather something done
> explicitly by the release script.
>
> --
>
> Regarding the artifactId naming, I find the use of the same prefix in
> the artifactIds more consistent, i.e "jakarta.xml.registry-parent" and
> "jakarta.xml.registry-spec".
>
> I've looked at other similar repositories under the eclipse-ee4j
> organization:
> - https://github.com/eclipse-ee4j/jms-api
> - https://github.com/eclipse-ee4j/jsonb-api
> - https://github.com/eclipse-ee4j/jpa-api
> - https://github.com/eclipse-ee4j/security-api
> - https://github.com/eclipse-ee4j/websocket-api
> - https://github.com/eclipse-ee4j/ejb-api
> - https://github.com/eclipse-ee4j/common-annotations-api
> - https://github.com/eclipse-ee4j/jaxb-api
>
> There seems to be two patterns here:
> 1) JAXR and co: single Maven build with a parent pom and only the api
> artifactId starts with the package name
> 2) JPA, JAXB: the spec and api modules are standalone and can be
> deployed separately, there may be a top level pom (not a parent) to
> aggregate the Maven build
>
> JSONB is a little odd, it follows #2 except that the spec artifactId is
> "jsonb-spec".
>
> Note that it may be already too late to change what's been deployed
> already, Sonatype isn't very keen on pruning stuff out of Maven Central.
> Also the GAV matters mostly for the API artifacts since it's visible to
> end-users, the spec and parent pom if any are not very visible so
> consistency is not super important for these.
>
>> On Fri, Sep 6, 2019 at 9:30 AM Jim Krueger <jckofbyron@xxxxxxxxx
>> <mailto:jckofbyron@xxxxxxxxx>> wrote:
>>
>> I agree Kevin. The question is, should the pom.xml be changed to
>>    <parent>
>> <groupId>jakarta.xml.registry</groupId>
>> <artifactId>registry-api-parent</artifactId>
>>    <version>1.0.10-SNAPSHOT</version>
>>    </parent>
>> (which matches what Dmitry did in JAX-RPC)
>> or change it to:
>>    <parent>
>> <groupId>jakarta.xml.registry</groupId>
>> <artifactId>jakarta.xml.registry-api-parent</artifactId>
>>    <version>1.0.10-SNAPSHOT</version>
>>    </parent>
>> (which matches what is in mvnrepository.com
>> <http://mvnrepository.com>)
>>
>> And then the question is will modifying an re-building affect the
>> approvals for JAXR that have already been granted?
>>
>> On Fri, Sep 6, 2019 at 9:05 AM Kevin Sutter <sutter@xxxxxxxxxx
>> <mailto:sutter@xxxxxxxxxx>> wrote:
>>
>> Jim,
>> Something in our pom configuration for jaxr is preventing the
>> parent pom from deploying. So, either we need to figure out
>> how to properly deploy the parent pom:
>>
>> <parent>
>>    <groupId>jakarta.xml.registry</groupId>
>> <artifactId>xml.registry-api-parent</artifactId>
>>    <version>1.0.10-SNAPSHOT</version>
>> </parent>
>>
>> Or, we change the parent pom reference to something that exists:
>>
>> https://repo.maven.apache.org/maven2/org/eclipse/ee4j/project/1.0.5/
>>
>> I'd prefer that we go the first option. It could be something
>> simple in the pom that is preventing the parent from deploying.
>>
>> ---------------------------------------------------
>> Kevin Sutter
>> STSM, MicroProfile and Jakarta EE architect
>> e-mail: sutter@xxxxxxxxxx<mailto: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
>> <mailto:jckofbyron@xxxxxxxxx>>
>> To: EE4J build and releng discussions <ee4j-build@xxxxxxxxxxx
>> <mailto:ee4j-build@xxxxxxxxxxx>>, romain.grecourt@xxxxxxxxxx
>> <mailto:romain.grecourt@xxxxxxxxxx>, Dmitry Kornilov
>> <dmitry.kornilov@xxxxxxxxxx<mailto:dmitry.kornilov@xxxxxxxxxx>>
>> Date: 09/06/2019 08:35 AM
>> Subject: [EXTERNAL] Re: [ee4j-build] Problem releasing XML
>> Registries (JAXR)
>> Sent by: ee4j-build-bounces@xxxxxxxxxxx
>> <mailto:ee4j-build-bounces@xxxxxxxxxxx>
>> ------------------------------------------------------------------------
>>
>>
>>
>> Thanks Romain, however I'm confused on how to proceed with this.
>>
>> I am using jax-rpc-api as a model (which was successfully
>> released by Dmitry).   In JAX-RPC the parent is
>> <artifactId>rpc-api-parent</artifactId>, whereas the
>> artifactId for JAXR is
>> <artifactId>xml.registry-api-parent</artifactId>.
>>
>> Are you saying that both of these are wrong? Should the
>> artifactId for JAX-RPC be "jakarta.xml.rpc-api-parent" and
>> JAXR be "jakarta.xml.registry-api-parent"?
>>
>> Or maybe I should just remove the "xml." prefix from the
>> artifactId for JAXR to match what JAX-RPC is doing? Is there a
>> good place to verify these artifactId's?
>>
>> Thanks.
>>
>> On Thu, Sep 5, 2019 at 5:39 PM Romain Grecourt
>> <_romain.grecourt@oracle.com_
>> <mailto:romain.grecourt@xxxxxxxxxx>> wrote:
>> Seems like the nexus maven plugin choked itself ;)
>>
>> Looking at Maven Central, I see
>> jakarata.xml.registry:jakarta.xml.registry-api:1.0.10.
>> However its pom references a parent that doesn't exist:
>> _http://repo1.maven.org/maven2/jakarta/xml/registry/jakarta.xml.registry-api/1.0.10/jakarta.xml.registry-api-1.0.10.pom_
>>
>> Unless the parent pom is being synced from OSSRH to Maven
>> Central, the API artifact is not resolvable.
>> I suggest you wait for a couple hours and respin the release
>> of the parent pom.
>>
>> --
>>
>> Side notes.
>>
>> I don't understand why the parent pom is deployed separately.
>> Also the parent pom and spec artifactId don't use the
>> "jakarta." prefix, it feels inconsistent.
>>
>> On 9/5/19 3:15 PM, Jim Krueger wrote:
>> 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@eclipse.org_ <mailto: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_
>>
>> _______________________________________________
>> ee4j-build mailing list_
>> __ee4j-build@eclipse.org_ <mailto: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________________________________________________
>> ee4j-build mailing list
>> ee4j-build@xxxxxxxxxxx<mailto: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
>>
>>
>> _______________________________________________
>> ee4j-build mailing list
>> ee4j-build@xxxxxxxxxxx<mailto: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
>>
>>
>> _______________________________________________
>> 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
>
>
> _______________________________________________
> 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
>
_______________________________________________
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

_______________________________________________
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

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

References:
- [ee4j-build] Problem releasing XML Registries (JAXR)
  - From: Jim Krueger
- Re: [ee4j-build] Problem releasing XML Registries (JAXR)
  - From: Romain Grecourt
- Re: [ee4j-build] Problem releasing XML Registries (JAXR)
  - From: Jim Krueger
- Re: [ee4j-build] Problem releasing XML Registries (JAXR)
  - From: Kevin Sutter
- Re: [ee4j-build] Problem releasing XML Registries (JAXR)
  - From: Jim Krueger
- Re: [ee4j-build] Problem releasing XML Registries (JAXR)
  - From: Jim Krueger
- Re: [ee4j-build] Problem releasing XML Registries (JAXR)
  - From: Romain Grecourt
- Re: [ee4j-build] Problem releasing XML Registries (JAXR)
  - From: Lukas Jungmann
- Re: [ee4j-build] Problem releasing XML Registries (JAXR)
  - From: Jim Krueger
- Re: [ee4j-build] Problem releasing XML Registries (JAXR)
  - From: Romain Grecourt
- Re: [ee4j-build] Problem releasing XML Registries (JAXR)
  - From: Jim Krueger
- Re: [ee4j-build] Problem releasing XML Registries (JAXR)
  - From: Romain Grecourt

Prev by Date: Re: [ee4j-build] Problem releasing XML Registries (JAXR)
Next by Date: Re: [ee4j-build] [jakartaee-spec-project-leads] Can Maven Central artifacts be overwritten?
Previous by thread: Re: [ee4j-build] Problem releasing XML Registries (JAXR)
Next by thread: [ee4j-build] Jakarta Managemen.j2ee-api not releasing to MVNRepository
Index(es):
- Date
- Thread

Breadcrumbs