[
https://issues.apache.org/jira/browse/BEAM-9765?focusedWorklogId=423127&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-423127
]
ASF GitHub Bot logged work on BEAM-9765:
----------------------------------------
Author: ASF GitHub Bot
Created on: 15/Apr/20 23:13
Start Date: 15/Apr/20 23:13
Worklog Time Spent: 10m
Work Description: amaliujia commented on issue #11429: [BEAM-9765]
Exclude module-info.class from vendored Calcite.
URL: https://github.com/apache/beam/pull/11429#issuecomment-614325133
LGTM
Also cc @lukecwik in case there is other opinion.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 423127)
Time Spent: 20m (was: 10m)
> :vendor:calcite-1_20_0:validateVendoring fails
> ----------------------------------------------
>
> Key: BEAM-9765
> URL: https://issues.apache.org/jira/browse/BEAM-9765
> Project: Beam
> Issue Type: Bug
> Components: dsl-sql
> Reporter: Kyle Weaver
> Assignee: Kyle Weaver
> Priority: Major
> Fix For: 2.21.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This error was reported on Slack:
> https://the-asf.slack.com/archives/C9H0YNP3P/p1586911958184200
> "I encountered this error when I built Beam from master branch. Is it a known
> issue? It happens in beam 2.21 and master branch, but the build works fine in
> 2.20."
> -----------
> * What went wrong:
> Execution failed for task ':vendor:calcite-1_20_0:validateVendoring'.
> > /home/yangzhan/oss/beam/vendor/calcite-1_20_0/build/libs/beam-vendor-calcite-1_20_0-0.2.jar
> > exposed classes outside of org.apache.beam namespace:
> > [/home/yangzhan/oss/beam/vendor/calcite-1_20_0/build/tmp/expandedArchives/beam-vendor-calcite-1_20_0-0.2.jar_ee40b0aab4e7709d8d80d205ee8852ba/module-info.class]
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or
> --debug option to get more log output. Run with --scan to get full insights.
> ==============================================================================
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
