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

Kyle Weaver commented on BEAM-9765:
-----------------------------------

Marking this as a release blocker since IIUC this will be a problem when we try 
to publish artifacts.

It looks like there has been some back-and-forth on this line: 
https://github.com/apache/beam/blob/4a7eb329734131e1ef90419f405986de94a30846/buildSrc/src/main/groovy/org/apache/beam/gradle/VendorJavaPlugin.groovy#L142
Changing it to `exclude "**/module-info.class"` fixes the issue, however I am 
not sure if we should change this line or if we should somehow prevent 
module-info.class from entering the jar.

> :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
>            Priority: Major
>             Fix For: 2.21.0
>
>
> 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)

Reply via email to