Publish the bom along with the other artifacts #54
Comments
raboof
added a commit
to raboof/sbt-bom
that referenced
this issue
Jun 12, 2024
I'd have liked to add a scripted test, but it seems scripted doesn't allow referring to '$HOME' or '~' for checking files have been created. Implements sbt#54
raboof
added a commit
to raboof/sbt-bom
that referenced
this issue
Oct 17, 2024
I'd have liked to add a scripted test, but it seems scripted doesn't allow referring to '$HOME' or '~' for checking files have been created. Implements sbt#54
raboof
added a commit
to raboof/sbt-bom
that referenced
this issue
Oct 17, 2024
I'd have liked to add a scripted test, but it seems scripted doesn't allow referring to '$HOME' or '~' for checking files have been created. This produces artifact names consistent with the Maven plugin, e.g. `pekko-actor_2.13-cylonedx.xml` Implements sbt#54
raboof
added a commit
to raboof/sbt-bom
that referenced
this issue
Oct 18, 2024
I'd have liked to add a scripted test, but it seems scripted doesn't allow referring to '$HOME' or '~' for checking files have been created. This produces artifact names consistent with the Maven plugin, e.g. `pekko-actor_2.13-cylonedx.xml` Implements sbt#54
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be nice if the generated bom could be published to where-ever the project using sbt-bom is published, similar to cyclonedx-maven-plugin and cyclonedx-maven-plugin
The text was updated successfully, but these errors were encountered: