You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Steinar Bang <sb...@dod.no> on 2026/10/13 18:11:15 UTC
Failed deploy to central portal
I am trying to do a deploy to central portal from a github actions
workflow
https://github.com/steinarb/jdbc/blob/master/.github/workflows/jdbc-maven-release-ci-build.yml
The workflow fails when trying to deploy the BOM (which has been
detached from the maven pom parent by flatten-maven-plugin):
https://github.com/steinarb/jdbc/actions/runs/38435265512/job/115427465409#step:6:412
The error message is:
[INFO] Generate checksums for dir: no/priv/bang/jdbc/jdbc-bom/1.4.0
[INFO] Going to create /home/runner/work/jdbc/jdbc/target/central-publishing/central-bundle.zip by bundling content at /home/runner/work/jdbc/jdbc/target/central-staging
[INFO] Created bundle successfully /home/runner/work/jdbc/jdbc/target/central-staging/central-bundle.zip
[INFO] Going to upload /home/runner/work/jdbc/jdbc/target/central-publishing/central-bundle.zip
[INFO] Uploaded bundle successfully, deployment name: Deployment, deploymentId: e2bb252a-361e-44d8-ac08-35cc3681762a. Deployment will publish automatically
[INFO] Waiting until Deployment e2bb252a-361e-44d8-ac08-35cc3681762a is validated
[ERROR]
Deployment e2bb252a-361e-44d8-ac08-35cc3681762a failed
common:
- Bundle has content that does NOT have a .pom file: no/priv/bang/jdbc/jdbc-parent, no/priv/bang/jdbc/jdbc, no/priv/bang/jdbc/jacoco-coverage-report, no/priv/bang/jdbc/jdbc-bom, no/priv/bang/jdbc/jdbc.sqldumper, no/priv/bang/jdbc/jdbc.datasourceproxy
Why are the other projects mentioned when the failure is in jdbc-bom?
(And I am quite sure they all have pom files!)
I note that the error message is similar to this error, would downgrade
mvn work for me as well?
https://lists.apache.org/thread.html/1trdtdct2glycrzqo6xhbryns5o5pxno
Are there any other obvious things I could try?
I tried adding "-e -X" to the mvn command to get more debug info, but
the result was mostly noise:
https://github.com/steinarb/jdbc/actions/runs/38436279440
Thanks!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Failed deploy to central portal
Posted by Steinar Bang <sb...@dod.no>.
>>>>> "Daniel B. Widdis" <wi...@gmail.com>:
> This has been fixed in the latest version of the central publishing
> plugin: org.sonatype.central:central-publishing-maven-plugin
> version 0.12.0.
I can confirm that I have successfully deployed a project with a similar
BOM structure to the project that failed, using
central-publishing-maven-plugin 0.12.0 using this github action workflow
https://github.com/steinarb/authservice/blob/master/.github/workflows/authservice-maven-release-ci-build.yml
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Failed deploy to central portal
Posted by "Daniel B. Widdis" <wi...@gmail.com>.
This has been fixed in the latest version of the central publishing
plugin: org.sonatype.central:central-publishing-maven-plugin
version 0.12.0.
On Wed, Oct 14, 2026 at 2:20 PM Steinar Bang <sb...@dod.no> wrote:
> >>>>> Maxim Solodovnik <so...@gmail.com>:
>
> > this error seems to be from `central-publishing-maven-plugin`
> > I would check
> > - if most recent version of plugin is used
> > - manually unpack the archive being uploaded to
> > https://central.sonatype.com and check the contents
>
> Thanks for responding! What worked was downgrading maven from 3.10 to
> 3.9.16. No other config changes were necessary.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Dan Widdis
Re: Failed deploy to central portal
Posted by Steinar Bang <sb...@dod.no>.
>>>>> Maxim Solodovnik <so...@gmail.com>:
> this error seems to be from `central-publishing-maven-plugin`
> I would check
> - if most recent version of plugin is used
> - manually unpack the archive being uploaded to
> https://central.sonatype.com and check the contents
Thanks for responding! What worked was downgrading maven from 3.10 to
3.9.16. No other config changes were necessary.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Failed deploy to central portal
Posted by Rob Spoor <ap...@icemanx.nl>.
You can revert now if you want, see
https://github.com/sonatype-nexus-community/central-publishing-maven-plugin/issues/1
and
https://central.sonatype.org/publish/publish-portal-maven/#0120-13-oct-2026.
On 14/10/2026 23:16, Steinar Bang wrote:
>>>>>> Rob Spoor <ap...@icemanx.nl>:
>
>> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Failed deploy to central portal
Posted by Steinar Bang <sb...@dod.no>.
>>>>> Rob Spoor <ap...@icemanx.nl>:
> 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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Failed deploy to central portal
Posted by Rob Spoor <ap...@icemanx.nl>.
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.
On 14/10/2026 04:54, Maxim Solodovnik wrote:
> this error seems to be from `central-publishing-maven-plugin`
> I would check
> - if most recent version of plugin is used
> - manually unpack the archive being uploaded to
> https://central.sonatype.com and check the contents
>
> On Wed, 14 Oct 2026 at 01:11, Steinar Bang <sb...@dod.no> wrote:
>>
>> I am trying to do a deploy to central portal from a github actions
>> workflow
>> https://github.com/steinarb/jdbc/blob/master/.github/workflows/jdbc-maven-release-ci-build.yml
>>
>> The workflow fails when trying to deploy the BOM (which has been
>> detached from the maven pom parent by flatten-maven-plugin):
>> https://github.com/steinarb/jdbc/actions/runs/38435265512/job/115427465409#step:6:412
>>
>> The error message is:
>> [INFO] Generate checksums for dir: no/priv/bang/jdbc/jdbc-bom/1.4.0
>> [INFO] Going to create /home/runner/work/jdbc/jdbc/target/central-publishing/central-bundle.zip by bundling content at /home/runner/work/jdbc/jdbc/target/central-staging
>> [INFO] Created bundle successfully /home/runner/work/jdbc/jdbc/target/central-staging/central-bundle.zip
>> [INFO] Going to upload /home/runner/work/jdbc/jdbc/target/central-publishing/central-bundle.zip
>> [INFO] Uploaded bundle successfully, deployment name: Deployment, deploymentId: e2bb252a-361e-44d8-ac08-35cc3681762a. Deployment will publish automatically
>> [INFO] Waiting until Deployment e2bb252a-361e-44d8-ac08-35cc3681762a is validated
>> [ERROR]
>>
>> Deployment e2bb252a-361e-44d8-ac08-35cc3681762a failed
>> common:
>> - Bundle has content that does NOT have a .pom file: no/priv/bang/jdbc/jdbc-parent, no/priv/bang/jdbc/jdbc, no/priv/bang/jdbc/jacoco-coverage-report, no/priv/bang/jdbc/jdbc-bom, no/priv/bang/jdbc/jdbc.sqldumper, no/priv/bang/jdbc/jdbc.datasourceproxy
>>
>> Why are the other projects mentioned when the failure is in jdbc-bom?
>> (And I am quite sure they all have pom files!)
>>
>> I note that the error message is similar to this error, would downgrade
>> mvn work for me as well?
>> https://lists.apache.org/thread.html/1trdtdct2glycrzqo6xhbryns5o5pxno
>>
>> Are there any other obvious things I could try?
>>
>> I tried adding "-e -X" to the mvn command to get more debug info, but
>> the result was mostly noise:
>> https://github.com/steinarb/jdbc/actions/runs/38436279440
>>
>> Thanks!
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Failed deploy to central portal
Posted by Maxim Solodovnik <so...@gmail.com>.
this error seems to be from `central-publishing-maven-plugin`
I would check
- if most recent version of plugin is used
- manually unpack the archive being uploaded to
https://central.sonatype.com and check the contents
On Wed, 14 Oct 2026 at 01:11, Steinar Bang <sb...@dod.no> wrote:
>
> I am trying to do a deploy to central portal from a github actions
> workflow
> https://github.com/steinarb/jdbc/blob/master/.github/workflows/jdbc-maven-release-ci-build.yml
>
> The workflow fails when trying to deploy the BOM (which has been
> detached from the maven pom parent by flatten-maven-plugin):
> https://github.com/steinarb/jdbc/actions/runs/38435265512/job/115427465409#step:6:412
>
> The error message is:
> [INFO] Generate checksums for dir: no/priv/bang/jdbc/jdbc-bom/1.4.0
> [INFO] Going to create /home/runner/work/jdbc/jdbc/target/central-publishing/central-bundle.zip by bundling content at /home/runner/work/jdbc/jdbc/target/central-staging
> [INFO] Created bundle successfully /home/runner/work/jdbc/jdbc/target/central-staging/central-bundle.zip
> [INFO] Going to upload /home/runner/work/jdbc/jdbc/target/central-publishing/central-bundle.zip
> [INFO] Uploaded bundle successfully, deployment name: Deployment, deploymentId: e2bb252a-361e-44d8-ac08-35cc3681762a. Deployment will publish automatically
> [INFO] Waiting until Deployment e2bb252a-361e-44d8-ac08-35cc3681762a is validated
> [ERROR]
>
> Deployment e2bb252a-361e-44d8-ac08-35cc3681762a failed
> common:
> - Bundle has content that does NOT have a .pom file: no/priv/bang/jdbc/jdbc-parent, no/priv/bang/jdbc/jdbc, no/priv/bang/jdbc/jacoco-coverage-report, no/priv/bang/jdbc/jdbc-bom, no/priv/bang/jdbc/jdbc.sqldumper, no/priv/bang/jdbc/jdbc.datasourceproxy
>
> Why are the other projects mentioned when the failure is in jdbc-bom?
> (And I am quite sure they all have pom files!)
>
> I note that the error message is similar to this error, would downgrade
> mvn work for me as well?
> https://lists.apache.org/thread.html/1trdtdct2glycrzqo6xhbryns5o5pxno
>
> Are there any other obvious things I could try?
>
> I tried adding "-e -X" to the mvn command to get more debug info, but
> the result was mostly noise:
> https://github.com/steinarb/jdbc/actions/runs/38436279440
>
> Thanks!
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
--
Best regards,
Maxim
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org