[BEAM-6178] Adding beam-sdks-java-bom, adding exportJavadoc flag for applyJavaNature #7197
swegner left a comment
If I understand correctly, this produces a new Maven artifact
Is this useful? It seems straightforward for Beam consumers to define a single
Your high-level understanding is correct. In isolation, using a beam version property works just fine. The problem is when you want to set up another BOM that specifies the modules of Beam. In that case, it's not sustainable for that aggregated BOM to specify each module of Beam; it's much more sustainable for Beam to generate a BOM with Beam's module versions, which adds dependency declarations automatically when new modules are added to Beam, and then have the aggregated BOM just import the Beam BOM. We are trying to set up such an aggregator BOM at https://github.com/GoogleCloudPlatform/cloud-opensource-java/blob/master/boms/cloud-oss-bom/pom.xml .