You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/12/07 17:12:01 UTC

[jira] [Commented] (BEAM-11038) runShadow error: property 'mainClass' is final

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

Beam JIRA Bot commented on BEAM-11038:
--------------------------------------

This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.


> runShadow error: property 'mainClass' is final
> ----------------------------------------------
>
>                 Key: BEAM-11038
>                 URL: https://issues.apache.org/jira/browse/BEAM-11038
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-flink, runner-spark
>    Affects Versions: 2.25.0
>            Reporter: Kyle Weaver
>            Priority: P2
>              Labels: stale-P2
>
> This also happens for the :runners:flink:1.x:job-server:runShadow tasks. However, it does not affect the shadowJar task, which builds the jar, so it is still possible to build and run the jar, just not with runShadow.
> Looks like we were hit by https://github.com/johnrengelman/shadow/issues/574.
> > Task :runners:spark:job-server:runShadow FAILED
> FAILURE: Build failed with an exception.
> * What went wrong:
> Execution failed for task ':runners:spark:job-server:runShadow'.
> > The value for task ':runners:spark:job-server:runShadow' property 'mainClass' is final and cannot be changed any further.



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