bleep import-maven
import an existing Maven build by reading pom.xml (uses mvn help:effective-pom to resolve parent POMs and dependencyManagement)
Synopsis
bleep import-maven [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-mvn | skip running mvn, use existing effective-pom.xml in .bleep/import/maven/ |
--skip-generated-resources-script | disable creating a script to regenerate discovered generated sources/resources |
--mvn-path <string> | optional path to mvn executable |
--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.