Abacn commented on issue #34694:
URL: https://github.com/apache/beam/issues/34694#issuecomment-4603953764
I think what happens is that YAML documentation generation depends on Java
expansion services:
```
WARNING:apache_beam.utils.subprocess_server: WARNING: Apache Beam is
downloading dependencies from a public repository at runtime.
This may pose security risks or cause instability due to repository
availability.
URL:
https://repo.maven.apache.org/maven2/org/apache/beam/beam-sdks-java-extensions-sql-expansion-service/2.74.0/beam-sdks-java-extensions-sql-expansion-service-2.74.0.jar
Destination:
/home/runner/.apache_beam/cache/jars/beam-sdks-java-extensions-sql-expansion-service-2.74.0.jar
Consider pre-staging dependencies or using a private repository mirror.
For more information, see:
https://beam.apache.org/documentation/sdks/python-dependencies/
WARNING:apache_beam.utils.subprocess_server: WARNING: Apache Beam is
downloading dependencies from a public repository at runtime.
```
at build_release_candidate, the jars are not yet published to maven central,
and the content is empty.
After release finalized, running the same command, the content is no longer
empty because the jars are now present.
I think we need a fallback mechanism to either download staging / snapshot
jars at build_release_candidate time
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
