[jira] [Commented] (BEAM-11709) Beam BOM produces incorrect variant in Gradle module metadata

["Beam JIRA Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BEAM-11709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17293041#comment-17293041 ] 

Beam JIRA Bot commented on BEAM-11709:
--------------------------------------

This issue is assigned but has not received an update in 30 days so it has been labeled "stale-assigned". If you are still working on the issue, please give an update and remove the label. If you are no longer working on the issue, please unassign so someone else may work on it. In 7 days the issue will be automatically unassigned.

> Beam BOM produces incorrect variant in Gradle module metadata
> -------------------------------------------------------------
>
>                 Key: BEAM-11709
>                 URL: https://issues.apache.org/jira/browse/BEAM-11709
>             Project: Beam
>          Issue Type: Bug
>          Components: dependencies
>            Reporter: Kiley Sok
>            Assignee: Kiley Sok
>            Priority: P2
>              Labels: stale-assigned
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> Since 2.26, the Gradle module metadata[1] has been produced by default. Currently it lists 'library' as its category instead of 'platform', so Gradle users aren't able to depend on the BOM.
> We can stop generating the Gradle module metadata using: [https://docs.gradle.org/current/userguide/publishing_gradle_module_metadata.html#sub:disabling-gmm-publication]
> Or fix the BOM generation to produce the platform variant
>  
> [1]https://repo1.maven.org/maven2/org/apache/beam/beam-sdks-java-bom/2.26.0/beam-sdks-java-bom-2.26.0.module



--
This message was sent by Atlassian Jira
(v8.3.4#803005)