[jira] [Commented] (FLINK-2607) Shade plugin copies signature files from original jar into fat jar

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot commented on FLINK-2607:
---------------------------------------

GitHub user mxm opened a pull request:

    https://github.com/apache/flink/pull/1085

    [FLINK-2607][quickstart] ignore signature files when creating fat jar

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mxm/flink quickstart

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/1085.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1085
    
----
commit 9bc513129755b82a9b71b3b21c7ab4d6a0305cf8
Author: Maximilian Michels <mx...@apache.org>
Date:   2015-09-02T10:21:49Z

    [FLINK-2607][quickstart] ignore signature files when creating fat jar

----


> Shade plugin copies signature files from original jar into fat jar
> ------------------------------------------------------------------
>
>                 Key: FLINK-2607
>                 URL: https://issues.apache.org/jira/browse/FLINK-2607
>             Project: Flink
>          Issue Type: Bug
>          Components: Quickstarts
>    Affects Versions: 0.9, 0.10
>            Reporter: Maximilian Michels
>            Assignee: Maximilian Michels
>             Fix For: 0.10
>
>
> The Quickstart project contains a Maven configuration that builds a fat jar using the Maven Shade plugin. It copies the {{META-INF}} folder of the original jar into the fat jar as well. That can lead to a {{SecurityException}} when submitting jobs to the cluster because the signature file contained in the original jar is not suitable for the fat jar. 
> {noformat}
>  java.lang.SecurityException: Invalid signature file digest for Manifest main attributes
> {noformat}
> The solution is to change the configuration of the Shade plugin to ignore the signature files in the {{META-INF}} folder when copying the dependencies to the fat jar. 
> See also:
> http://zhentao-li.blogspot.ch/2012/06/maven-shade-plugin-invalid-signature.html
> http://stackoverflow.com/questions/999489/invalid-signature-file-when-attempting-to-run-a-jar



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)