Hi Tom,
I already implemented and tested release on JSONP and JSONB API.
https://jenkins.eclipse.org/jsonp/job/nexus-staging/
https://jenkins.eclipse.org/jsonb/job/nexus-staging/
Will publish job content tomorrow on the wiki.
JTA project has also this nexus-staging job. I implemented
missing release) case there:
release)
if [ "${RELEASE}" = 'true' ]; then
if [ -n "${VERSION}" ]; then
echo '-[ Releasing Nexus staging repository for
JTA API ]-----------------------------'
mvn -B ${NEXUS_PLUGIN_PARAMS}
${NEXUS_PLUGIN}:rc-release \
-DstagingRepositoryId="${VERSION}"
fi
else
echo '-[ Release confirmation was not selected
]--------------------------------------'
fi
;;
You have 2 JTA deployments:
[INFO] jakartatransaction-1008 CLOSED jakarta.transaction:jakarta.transaction-api:1.3.1
[INFO] jakartatransaction-1009 CLOSED jakarta.transaction:jakarta.transaction-api:1.3.2
So for jakarta.transaction:jakarta.transaction-api:1.3.2 use
those values in the form:
- Branch: EE4J_8
- Action: release
- Version (Deployment ID): jakartatransaction-1009
- Release: checked
Tomas
Dne 07.01.19 v 22:13 Tom Jenkinson
napsal(a):
Thanks Bill!
You need to use
nexus-stagin:rc-release, as described at the end of my
writeup.
Tom
Jenkinson wrote on 1/7/19 8:21 AM:
Does anyone have some suggestion how to promote a
release from staging into Maven central?
Thanks,
Tom
_______________________________________________
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
