Skip to content

fix: Default sbtPluginPublishLegacyMavenStyle to false#8148

Merged
eed3si9n merged 1 commit intosbt:1.11.xfrom
eed3si9n:wip/plugin
Jun 2, 2025
Merged

fix: Default sbtPluginPublishLegacyMavenStyle to false#8148
eed3si9n merged 1 commit intosbt:1.11.xfrom
eed3si9n:wip/plugin

Conversation

@eed3si9n
Copy link
Copy Markdown
Member

@eed3si9n eed3si9n commented Jun 2, 2025

Fixes #8137

Problem

Central Portal no longer supports the legacy sbt plugin layout.

Solution

Make the default more friendly by setting sbtPluginPublishLegacyMavenStyle to false.

**Problem**
Central Portal no longer supports the legacy sbt plugin layout.

**Solution**
Make the default more friendly by setting sbtPluginPublishLegacyMavenStyle to false.
@eed3si9n eed3si9n merged commit ac397d9 into sbt:1.11.x Jun 2, 2025
16 of 17 checks passed
@eed3si9n eed3si9n deleted the wip/plugin branch June 2, 2025 03:09
@mkurz
Copy link
Copy Markdown
Member

mkurz commented Jun 5, 2025

Given that from now on sbt plugins under com.github.sbt published to maven central can only be consumed by sbt 1.9.0 or newer, I guess from now on we can set the minimal crossSbtVersions to 1.9.0? (I did see some plugins setting the minimal sbt version to 1.5.0 or similar)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Sonatype central publish fails for sbt plugin

2 participants