bvolpato opened a new issue, #25340:
URL: https://github.com/apache/beam/issues/25340

   ### What would you like to happen?
   
   Is it possible to provide a comprehensive [Bill of 
Materials/BOM](https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#bill-of-materials-bom-poms)
 with Beam?
   
   Beam / IOs contain many dependencies, which often conflict with other 
dependencies on the same project.
   Beam provides 
[beam-sdks-java-bom](https://mvnrepository.com/artifact/org.apache.beam/beam-sdks-java-bom)
 which is very helpful, but it can be prescriptive on many other dependencies.
   
   For example, every time that we update our reference to a version of Beam, 
we have to check 
[BeamModulePlugin.groovy](https://github.com/apache/beam/blob/master/buildSrc/src/main/groovy/org/apache/beam/gradle/BeamModulePlugin.groovy)
 so we can compare/match with our versions.
   
   The most notable one / source of issues is when 
`google_cloud_platform_libraries_bom` doesn't match - so I'm wondering if 
there's a way to provide a more comprehensive BOM so it becomes easier to stay 
up to date with Beam releases.
   
   ### Issue Priority
   
   Priority: 2 (default / most feature requests should be filed as P2)
   
   ### Issue Components
   
   - [ ] Component: Python SDK
   - [X] Component: Java SDK
   - [ ] Component: Go SDK
   - [ ] Component: Typescript SDK
   - [ ] Component: IO connector
   - [ ] Component: Beam examples
   - [ ] Component: Beam playground
   - [ ] Component: Beam katas
   - [ ] Component: Website
   - [ ] Component: Spark Runner
   - [ ] Component: Flink Runner
   - [ ] Component: Samza Runner
   - [ ] Component: Twister2 Runner
   - [ ] Component: Hazelcast Jet Runner
   - [ ] Component: Google Cloud Dataflow Runner


-- 
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]

Reply via email to