You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2021/05/15 17:58:02 UTC

[jira] [Updated] (BEAM-8862) Dependency on io.grpc-all allows test-only dependencies on runtimeClasspath

     [ https://issues.apache.org/jira/browse/BEAM-8862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kenneth Knowles updated BEAM-8862:
----------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Resolved)

Hello! Due to a bug in our Jira configuration, this issue had status:Resolved but resolution:Unresolved.

I am bulk editing these issues to have resolution:Fixed

If a different resolution is appropriate, please change it. To do this, click the "Resolve" button (you can do this even for closed issues) and set the Resolution field to the right value.

> Dependency on io.grpc-all allows test-only dependencies on runtimeClasspath
> ---------------------------------------------------------------------------
>
>                 Key: BEAM-8862
>                 URL: https://issues.apache.org/jira/browse/BEAM-8862
>             Project: Beam
>          Issue Type: Wish
>          Components: io-java-gcp
>            Reporter: Weimin Yu
>            Priority: P3
>             Fix For: 2.25.0
>
>
> The java-io-gcp module (maybe others too) has a compile dependency on io.grpc-all, which includes io.grpc-testing. This allows test-only dependencies (such as junit, mockito, and hamcrest etc) to get on compileClasspath and runtimeClasspath in downstream users. In our project we have to explicitly exclude them so that they do not get added to the release artifacts.
> Is it possible for your module to exclude io.grpc-testing from compile?



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