Closed greggdonovan closed 7 years ago
Running bazel run //generate_workspace -- '--artifact=org.apache.beam:beam-sdks-java-core:2.0.0' took >1hr and generated a >100k bzl file.
bazel run //generate_workspace -- '--artifact=org.apache.beam:beam-sdks-java-core:2.0.0'
If I remove the JARs pulled in via the parent POMs dependencyManagement, the result appears reasonable.
dependencyManagement
Should generate_workspace pull in every dependency specified in the full set of parent POMs or just use their versions to override the child POMs versions? Or should only a certain set of JARs brought in through dependencyManagement be used?
generate_workspace
This issue is being solved here #44.
@kchodorow can you close this as well?
Fixes by #44.
Running
bazel run //generate_workspace -- '--artifact=org.apache.beam:beam-sdks-java-core:2.0.0'
took >1hr and generated a >100k bzl file.If I remove the JARs pulled in via the parent POMs
dependencyManagement
, the result appears reasonable.Should
generate_workspace
pull in every dependency specified in the full set of parent POMs or just use their versions to override the child POMs versions? Or should only a certain set of JARs brought in through dependencyManagement be used?