>>>>> Rob Spoor <[email protected]>: > I could see in your action logs that you're using Maven 3.10, which > means you're probably running into the issues described at > https://lists.apache.org/thread.html/6mn9yh5mj9bcfsbb4bkoxw2m5vybyjyk.
> If you cannot wait for a newer version of the plugin, you probably > need to (temporarily) change your job to use a different > Maven. Unfortunately that cannot be done using the actions/setup-java > action, see https://github.com/actions/setup-java/issues/457. There is > a comment that suggest using https://github.com/s4u/setup-maven-action > instead. Alternatively, use a Maven wrapper added to your repository. Thanks! Downgrading maven to 3.9.16 in the github action release workflow worked: I made a successful release to central portal https://github.com/steinarb/jdbc/actions/runs/38636567999 What I did was replace setup-java with s4u/setup-maven-action (which is what I waas using for the ci workflow) and use the most recent 3.9.x maven version: https://github.com/steinarb/jdbc/blob/880ff7135d6d50c1e3a7aedda2a8ab32b496b1c3/.github/workflows/jdbc-maven-release-ci-build.yml --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
