migration-tooling
migration-tooling copied to clipboard
Migration tools for Bazel
Bazel is fantastic and I am very happy with the characteristics of our Build. I am writing quite complex rules for our build now as we have specific packaging and...
Hi, I have tried the transitive_maven_jar. I find that the cost of re-fetching dependencies everytime is very heavy. It cost a lot of time. Are there any solution to speed...
# Migrated from [issue 989](https://github.com/bazelbuild/bazel/issues/989) in main repository ### Post 1 I see the generate WORKSPACE tool, which is useful. But an ongoing issue is the pain in transitively adding...
# Migrated from [issue 1573](https://github.com/bazelbuild/bazel/issues/1573) in main repository If generate_workspace is run with artifacts that depend on a common artifact, it will choose the version from whichever it encounters first....
The previous version of the tool appeared to allow one to specify various Bazel projects and a combined WORKSPACE file would be generated. Is that something that we might be...
# Migrated from issue [#1131](https://github.com/bazelbuild/bazel/issues/1131) in original repository. generate_workspace seems to be creating invalid sha1 entries of the form: ``` maven_jar( name = "net_java_dev_jets3t_jets3t", artifact = "net.java.dev.jets3t:jets3t:0.6.1", sha1 = "9f95b944ccbbbeedd397e8f62e5690fd735a45e5...
# Migrated from [issue #2310](https://github.com/bazelbuild/bazel/issues/2310) in main repository. ### Description When using `generate_workspace` transitive dependencies are not always included in the `exports` parameter of `java_library`. This does not always happen...
# Migrated from [issue 1782](https://github.com/bazelbuild/bazel/issues/1782) in main repository Either: * Picking it up from settings.xml * Give it a path to settings.xml * Or set a flag for Maven Central...
# Migrated from [issue 2316](https://github.com/bazelbuild/bazel/issues/2316) in main repository example: `bazel run //src/tools/generate_workspace -- --artifact=org.mockito:mockito-core:2.4.2` mockito-core has 4 runtime dependencies, none were generated. I believe the cause of this issue is...
# Migrated from [issue #1783 ](https://github.com/bazelbuild/bazel/issues/1783) in main repository. E.g., `generate_workspace --artifact=jetty:1,old_prod --artifact=jetty:2,prod` will create two maven_jars with the given suffixes and their dependencies, matching deps where possible and appending...