Happy to accept any help. I'm on the Jakarta EE development slack if you're still awake.
I made this PR so we can hopefully release from the root directory.
- https://github.com/eclipse-ee4j/jms-api/pull/234
Hi David,
For the JMS job, the workspace path needs to be set to api only, otherwise it'll try to deploy the spec, which of course won't work.
# Directory with project top level pom.xml BUILD_DIR="${WORKSPACE}"
should become:
# Directory with project top level pom.xml BUILD_DIR="${WORKSPACE}/api"
I'd make the change myself otherwise, but maybe you're also working on it right now.
After that you can update the version numbers for the newly staged artefact in 2_messaging-run-tck-against-staged-build
(it has already completed once against the previous 2.02 version)
Kind regards, Arjan
_______________________________________________ jakartaee-spec-project-leads mailing list jakartaee-spec-project-leads@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads
|