doma-spring-boot icon indicating copy to clipboard operation
doma-spring-boot copied to clipboard

Could not find org.seasar.doma.boot:doma-spring-boot-starter:2.5.0-SNAPSHOT

Open chivosss opened this issue 7 months ago • 11 comments

The sonatype nexus can not access maven info about doma-spring-boot-starter:2.5.0-SNAPSHOT

chivosss avatar Sep 22 '25 05:09 chivosss

@nakamura-to Could you please check whether the SNAPSHOT for doma-spring-boot is enabled on central.sonatype.com? https://central.sonatype.org/publish/publish-portal-snapshots/#enabling-snapshot-releases-for-your-namespace

backpaper0 avatar Sep 22 '25 05:09 backpaper0

@backpaper0 The setting for -SNAPSHOT Releases is enabled for the org.seasar namespace.

Image

Have you enabled snapshot support in the central-publishing-maven-plugin configuration? you will need to configure a <snapshotRepository> or a <repository> with <snapshots><enabled>true</enabled></snapshots>. https://central.sonatype.org/publish/publish-portal-snapshots/#publishing-with-the-central-publishing-maven-plugin

Moreover, since the URL at the time of consumption has changed, the README needs to be updated. Please see the following link. https://central.sonatype.org/publish/publish-portal-snapshots/#consuming-via-maven

nakamura-to avatar Sep 22 '25 06:09 nakamura-to

@backpaper0 Please try adding the centralSnapshotsUrl setting.

<plugin>
    <groupId>org.sonatype.central</groupId>
    <artifactId>central-publishing-maven-plugin</artifactId>
    <version>0.8.0</version>
    <extensions>true</extensions>
    <configuration>
        <publishingServerId>central</publishingServerId>
        <autoPublish>true</autoPublish>
        <!-- Add this setting -->
        <centralSnapshotsUrl>https://central.sonatype.com/repository/maven-snapshots/</centralSnapshotsUrl>
    </configuration>
</plugin>

See https://central.sonatype.org/publish/publish-portal-maven/#centralsnapshotsurl

nakamura-to avatar Sep 22 '25 08:09 nakamura-to

@nakamura-to Thank you. But it still doesn’t work. In my personal repository, I can deploy SNAPSHOT versions with just the following settings, so I don’t understand why it doesn’t work with doma-spring-boot. https://github.com/backpaper0/hello-maven-central/blob/main/pom.xml#L89-L97

To isolate the cause, I’m thinking of spinning up a local Nexus and trying a deployment.

backpaper0 avatar Sep 23 '25 06:09 backpaper0

In the JaCoCo report aggregation project, I’ve set skipPublishing, but I suspect that’s causing the deployment of all artifacts to be skipped. https://github.com/domaframework/doma-spring-boot/blob/master/doma-spring-boot-jacoco-aggregate/pom.xml#L16

On my local Nexus, I was able to deploy successfully after removing the skipPublishing setting from doma-spring-boot-jacoco-aggregate, so I’m planning to apply the same change here. This does result in unnecessary doma-spring-boot-jacoco-aggregate artifacts being deployed, but I don’t think it’s harmful (though ideally we should fix it later so they’re not deployed at all).

backpaper0 avatar Sep 23 '25 07:09 backpaper0

@kidvon It was resolved in #337. Please try again to see if you can obtain doma-spring-boot-starter:2.5.0-SNAPSHOT.

backpaper0 avatar Sep 23 '25 07:09 backpaper0

@backpaper0 Thank you for your work. I was able to download the SNAPSHOT using Gradle.

@kidvon When using SNAPSHOTs with Maven or Gradle, please make sure to configure the settings described at the following link: https://central.sonatype.org/publish/publish-portal-snapshots/#consuming-snapshot-releases-for-your-project

nakamura-to avatar Sep 23 '25 07:09 nakamura-to

@backpaper0 @nakamura-to Thanks, it’s working now. I’m using Gradle.

chivosss avatar Sep 24 '25 06:09 chivosss

This issue is stale because it has been open for 60 days with no activity.

github-actions[bot] avatar Nov 24 '25 03:11 github-actions[bot]

I believe this issue has been resolved. Shall we close it?

nakamura-to avatar Dec 22 '25 20:12 nakamura-to

I believe this issue has been resolved. Shall we close it?

ok Thanks for confirming.

chivosss avatar Dec 24 '25 05:12 chivosss

This issue is stale because it has been open for 60 days with no activity.

github-actions[bot] avatar Feb 23 '26 04:02 github-actions[bot]