sbt-license-report
sbt-license-report copied to clipboard
sbt
Report on licenses used in an sbt project.
## About this PR 📦 Updates [org.scala-sbt:sbt](https://github.com/sbt/sbt) from `1.9.9` to `1.10.0` 📜 [GitHub Release Notes](https://github.com/sbt/sbt/releases/tag/v1.10.0) - [Version Diff](https://github.com/sbt/sbt/compare/v1.9.9...v1.10.0) ## Usage ✅ **Please merge!** I'll automatically update this PR to resolve...
## About this PR 📦 Updates [org.scalameta:scalafmt-core](https://github.com/scalameta/scalafmt) from `3.8.0` to `3.8.1` 📜 [GitHub Release Notes](https://github.com/scalameta/scalafmt/releases/tag/v3.8.1) - [Version Diff](https://github.com/scalameta/scalafmt/compare/v3.8.0...v3.8.1) ## Usage ✅ **Please merge!** I'll automatically update this PR to resolve...
Currently, the plugin resolves the dependencies using ivy resolver. Our builds only work with coursier, therefore we noticed sbt failing to resolve the dependencies. The plugin seems not maintained anymore....
Having a pom such as this https://repo1.maven.org/maven2/org/keycloak/keycloak-adapter-core/23.0.0/keycloak-adapter-core-23.0.0.pom ``` org.keycloak ${keycloak.crypto.artifactId} ```` Will lead to : ``` (updateLicenses) sbt.librarymanagement.ResolveException: unresolved dependency: org.keycloak#${keycloak.crypto.artifactId};working@company: java.net.URISyntaxException: Illegal character in path at index 64: https://nexus.io/repository/company-central/org/keycloak/${keycloak.crypto.artifactId}/working@company/${keycloak.crypto.artifactId}[email protected]...
As explained in https://github.com/sbt/sbt-license-report/pull/86 it would be ideal to just use the `update` task in order to retrieve the dependencies from the report however we are blocked by https://github.com/coursier/coursier/issues/1790 (tl;dr...
Currently there is a `Notes` column which lets you add custom notes when a report is generated. Ideally if there is no data in the `Notes` column then we should...
Currently when sbt-license-report generates a report, it only uses the current Scala version where as ideally we should aggregate the dependencies from all Scala versions as its possible for projects...
See https://github.com/apache/incubator-pekko-http/pull/147/files#r1194719727 for a case where this occurs. While sbt's `.from` can support arbitrary URL's, we can make our job easier if we restrict this to github.
Ideally this should have originally been typed to use `Configuration` rather than `String` since SBT already provides this abstraction as its own type. This is obviously a breaking change so...