You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Tomo Suzuki (Jira)" <ji...@apache.org> on 2019/12/13 19:53:00 UTC

[jira] [Comment Edited] (BEAM-8967) Maven artifact beam-sdks-java-core does not have dependencies specified as "compile"

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

Tomo Suzuki edited comment on BEAM-8967 at 12/13/19 7:52 PM:
-------------------------------------------------------------

Suspecting around this piece of code in BeamModulePlugin.groovy:

{noformat}
                // TODO: Should we use the runtime scope instead of the compile scope
                // which forces all our consumers to declare what they consume?
                generateDependenciesFromConfiguration(
                        configuration: (configuration.shadowClosure ? 'shadow' : 'compile'), scope: 'compile')
                generateDependenciesFromConfiguration(configuration: 'provided', scope: 'provided')
{noformat}

ShadowClosure field of a project?


{noformat}
    /**
     * If unset, no shading is performed. The jar and test jar archives are used during publishing.
     * Otherwise the shadowJar and shadowTestJar artifacts are used during publishing.
     *
     * The shadowJar / shadowTestJar tasks execute the specified closure to configure themselves.
     */
    Closure shadowClosure;
{noformat}




was (Author: suztomo):
Suspecting around this piece of code in BeamModulePlugin.groovy:

{noformat}
                // TODO: Should we use the runtime scope instead of the compile scope
                // which forces all our consumers to declare what they consume?
                generateDependenciesFromConfiguration(
                        configuration: (configuration.shadowClosure ? 'shadow' : 'compile'), scope: 'compile')
                generateDependenciesFromConfiguration(configuration: 'provided', scope: 'provided')

{noformat}


> Maven artifact beam-sdks-java-core does not have dependencies specified as "compile"
> ------------------------------------------------------------------------------------
>
>                 Key: BEAM-8967
>                 URL: https://issues.apache.org/jira/browse/BEAM-8967
>             Project: Beam
>          Issue Type: Improvement
>          Components: build-system
>            Reporter: Tomo Suzuki
>            Priority: Major
>
> Maven artifact beam-sdks-java-core does not have dependencies specified as "compile".
> This is a followup of [~iemejia]'s finding:
> {quote}
> Just double checked with today's SNAPSHOTs after the merge and the pom of core is not modified, however the deps look good in master, not sure if the change was applied before the SNAPSHOT generation, but still to double check.
> https://repository.apache.org/content/repositories/snapshots/org/apache/beam/beam-sdks-java-core/2.19.0-SNAPSHOT/beam-sdks-java-core-2.19.0-20191213.072102-9.pom
> {quote} 
> in [jsr305 dependency declaration for Nullable class|https://github.com/apache/beam/pull/10324#issuecomment-565516004]



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