You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be good to provide projects with a way to make project-specific customizations to the Bom object, so we allow them to express facts about the software that are not picked up automatically yet (such as embedded/shaded artifacts).
Maybe we can refactor things so that creating the Bom object is a separate sbt task, that can then be overridden in the project, so the customized Bom object is picked up by the configuration that adds it to the published artifacts.
The text was updated successfully, but these errors were encountered:
raboof
added a commit
to raboof/sbt-bom
that referenced
this issue
Nov 14, 2024
We'll likely want to refactor the task structure when we
implement sbt#90 or sbt#91, it might be nice to explicitly set
expectations around this without making it a blocker for
doing earlier releases.
We'll likely want to refactor the task structure when we
implement sbt#89, sbt#90 or sbt#91, it might be nice to explicitly
set expectations around this without making it a blocker
for doing earlier releases.
raboof
added a commit
to raboof/sbt-bom
that referenced
this issue
Dec 12, 2024
We'll likely want to refactor the task structure when we
implement sbt#89, sbt#90 or sbt#91, it might be nice to explicitly
set expectations around this without making it a blocker
for doing earlier releases.
It would be good to provide projects with a way to make project-specific customizations to the
Bomobject, so we allow them to express facts about the software that are not picked up automatically yet (such as embedded/shaded artifacts).Maybe we can refactor things so that creating the
Bomobject is a separate sbt task, that can then be overridden in the project, so the customizedBomobject is picked up by the configuration that adds it to the published artifacts.The text was updated successfully, but these errors were encountered: