Scala sbt 1.6.2 + dependency tree plugin error: Expected '--force'; dependencyList::toFile ... --append
See original GitHub issueHello. Thanks for this project, it’s very useful.
I have a problem using it with Scala project and sbt 1.6.2. Here is output:
$ cdxgen -r --server-url "${DEPS_SERVER_URL}" --api-key "${DEPS_API_KEY}" --project-name "${CI_PROJECT_PATH}" --project-version "${CI_COMMIT_REF_NAME}"
Executing sbt dependencyList in /builds/sonet/sonet-fullstack using plugins /tmp/cdxsbtg-pFmsI9
[info] welcome to sbt 1.6.2 (BellSoft Java 11.0.16)
[info] loading settings for project sonet-fullstack-build from plugins.sbt,dep-plugins.sbt ...
[info] loading project definition from /builds/sonet/sonet-fullstack/project
[info] loading settings for project sonet-fullstack from build.sbt ...
[info] set current project to sonet-fullstack (in build file:/builds/sonet/sonet-fullstack/)
[warn] there's a key that's not used by any other settings/tasks:
[warn]
[warn] * server / eclipsePreTasks
[warn] +- /builds/sonet/sonet-fullstack/build.sbt:51
[warn]
[warn] note: a setting might still be used by a command; to exclude a key from this `lintUnused` check
[warn] either append it to `Global / excludeLintKeys` or call .withRank(KeyRanks.Invisible) on the key
[info] __ __
[info] \ \ ____ / /____ _ __ __
[info] \ \ / __ \ / // __ `// / / /
[info] / / / /_/ // // /_/ // /_/ /
[info] /_/ / .___//_/ \__,_/ \__, /
[info] /_/ /____/
[info]
[info] Version 2.8.13 running Java 11.0.16
[info]
[info] Play is run entirely by the community. If you want to keep using it please consider donating:
[info] https://www.playframework.com/sponsors
[info]
[error] Expected '--force'
[error] dependencyList::toFile /tmp/cdxsbt-v0XsZc/dl-0.tmp --append
[error] ^
/builds/sonet/sonet-fullstack/build.sbt:14: warning: method in in trait ScopingSetting is deprecated (since 1.5.0): `in` is deprecated; migrate to slash syntax - https://www.scala-sbt.org/1.x/docs/Migrating-from-sbt-013x.html#slash
parallelExecution in Test := false,
^
/builds/sonet/sonet-fullstack/build.sbt:51: warning: method in in trait ScopingSetting is deprecated (since 1.5.0): `in` is deprecated; migrate to slash syntax - https://www.scala-sbt.org/1.x/docs/Migrating-from-sbt-013x.html#slash
EclipseKeys.preTasks := Seq(compile in Compile)
^
1. Check if scala and sbt is installed and available in PATH. Only scala 2.10 + sbt 0.13.6+ and 2.12 + sbt 1.0+ is supported for now.
2. Check if the plugin net.virtual-void:sbt-dependency-graph 0.10.0-RC1 can be used in the environment
3. Consider creating a lockfile using sbt-dependency-lock plugin. See https://github.com/stringbean/sbt-dependency-lock
BOM includes 0 components
I do not want to use lockfile. Any suggestions to make it work with dependencyList?
Issue Analytics
- State:
- Created a year ago
- Comments:7
Top Results From Across the Web
sbt plugin to create a dependency graph for your project
To add the plugin only to a single project, put this line into project/plugins.sbt of your project, instead. The plugin currently supports sbt...
Read more >How to See The Dependency Tree in SBT? | Baeldung on Scala
In this tutorial, we'll see why and how to use SBT to check our project dependency tree.
Read more >sbt Reference Manual — Combined Pages
Supports testing with ScalaCheck, specs, and ScalaTest. JUnit is supported by a plugin. Starts the Scala REPL with project classes and dependencies on...
Read more >How to see dependency tree in sbt? - scala - Stack Overflow
With sbt 1.4.0, dependencyTree task is available in sbt without using plugins. sbt dependencyTree.
Read more >jrudolph/sbt-dependency-graph - Gitter
adding it in this way to library dependencies libraryDependencies += ... /.ivy2/localorg.scala-sbt/sbt-dependency-tree/1.6.0-RC1/ivys/ivy.xml [error] not ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks!
4.0.38 includes the fix