Anatolii Kmetiuk e00efb9d9c [2.x] Fix ivyless sbt plugin publish cross paths (#9416) ...

Problem:
When useIvy := false, ivyless publishing dropped the optional
scala_[scalaVersion]/ and sbt_[sbtVersion]/ path segments from Ivy-style
plugin publish patterns. This caused sbt 1 plugins published from sbt 2 builds
to land under non-plugin Ivy paths, so consumers looking under
scala_2.12/sbt_1.0/ could not resolve them.

Solution:
Read the plugin cross-version attributes from the CsrProject module and use
them when constructing ivyless Ivy-layout publish paths. Apply the same
substitution for local/file Ivy publishing and remote Ivy-style URL publishing,
while continuing to omit those optional segments when the attributes are absent.
Add scripted regressions for local and HTTP Ivy-style publishing of an sbt 1
plugin with useIvy := false.

2026-07-12 22:28:10 -04:00

..

main

[2.x] Fix ivyless sbt plugin publish cross paths (#9416)

2026-07-12 22:28:10 -04:00

test

[2.x] fix: Discard a cancelled task's output backlog on cancel (#9411)

2026-07-12 21:27:57 -04:00