bleep import
import an existing sbt build by reading the Bloop JSON files in .bloop (run after sbt bloopInstall)
Synopsis
bleep import [flags]
Flags
| Flag | Description |
|---|---|
--ignore-when-templating, -i <string> (repeatable) | some projects may differ much from the rest, for instance documentation and examples. considering these when computing templates may negatively affect the result |
--skip-sbt | use if you already have generated bloop files and want to reimport from them |
--skip-generated-resources-script | disable creating a script to regenerate discovered generated sources/resources |
--jvm <metavar-jvm> | pick JVM to use for import. Valid nam in index file at https://github.com/coursier/jvm-index/raw/master/index.json |
--sbt-path <string> | optional path to sbt executable if sbt provided by coursier can not be used. |
--xmx <string> | JVM heap size for sbt processes (e.g., '4g', '8g'). Default is '4g'. |
--exclude-project, -x <string> (repeatable) | exclude specific projects from import and all their downstream dependencies (can be specified multiple times) |
--platform, -p <platform> (repeatable) | only import projects for specified platform(s) |
--scala, -s <scala version> (repeatable) | only import projects for specified scala version(s) |
Getting in and out
Mechanical paths in: bleep import (sbt) and
bleep import-maven (Maven). Mechanical path out:
bleep export-maven, a proof-of-concept script — see the
exit strategy.
Gradle has neither. There is no Gradle importer and no Gradle exporter, so a Gradle build is hand-ported in, and would be hand-ported out. There is no sbt exporter either.