[
https://issues.apache.org/jira/browse/BEAM-8621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16972907#comment-16972907
]
Yifan Zou commented on BEAM-8621:
---------------------------------
The problem is that Jenkins runs `gradle :runBeamDependencyCheck`. When the
Gradle runs tasks with colons (aka. qualified names), then the path is resolved
relative to the root project. In our case, it only checks dependencies defined
in the root directory. Removing the ":" from the task name will lead to a
multi-project build. [https://github.com/apache/beam/pull/10079] will fix this
issue.
> [Java] beam_Dependency_Check reads smaller number of dependencies than
> expected
> -------------------------------------------------------------------------------
>
> Key: BEAM-8621
> URL: https://issues.apache.org/jira/browse/BEAM-8621
> Project: Beam
> Issue Type: Bug
> Components: build-system
> Reporter: Tomo Suzuki
> Assignee: Yifan Zou
> Priority: Major
> Attachments: O0Mv0emfgA3.png
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> beam_Dependency_Check reads smaller number of dependencies than expected.
> Email thread: [Completeness of Beam Java Dependency Check Report
> .|https://lists.apache.org/thread.html/834072b5829317f788d9d02f266bdc4aaa494639f73be2c1e1e72640@%3Cdev.beam.apache.org%3E]
> [https://builds.apache.org/job/beam_Dependency_Check/232/console
> |https://builds.apache.org/job/beam_Dependency_Check/232/console]shows the
> execution log when it runs "gradlew runBeamDependencyCheck". The output of
> gradle is different from my development environment.
>
> !O0Mv0emfgA3.png! )
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
