Re: Invalid signature file digest for Manifest main attributes with spark job built using maven
; spark-streaming_2.10
> > 1.0.0-${cdh.version}
> >
> >
> > org.apache.flume
> > flume-ng-sdk
> > 1.5.0-${cdh.version}
> >
> >
> >
> > io.netty
> > netty
> >
> >
> >
> >
> > org.apache.flume
> > flume-ng-core
> > 1.5.0-${cdh.version}
> >
> >
> >
> > io.netty
> > netty
> >
> >
> >
> >
> > org.apache.hbase
> > hbase-client
> > 0.98.1-${cdh.version}
> >
> >
> >
> > io.netty
> > netty
> >
> >
> >
> >
> > org.apache.hadoop
> > hadoop-client
> > 2.3.0-${cdh.version}
> >
> >
> >
> >
> >
> > junit
> > junit
> > 4.11
> > test
> >
> >
> > org.specs2
> > specs2_${scala.tools.version}
> > 1.13
> > test
> >
> >
> > org.scalatest
> > scalatest_${scala.tools.version}
> > 2.0.M6-SNAP8
> > test
> >
> >
> >
> >
> > src/main/scala
> > src/test/scala
> >
> >
> >
> > net.alchim31.maven
> > scala-maven-plugin
> > 3.1.3
> >
> >
> >
> > compile
> > testCompile
> >
> >
> >
> > -make:transitive
> > -dependencyfile
> > ${project.build.directory}/.scala_dependencies
> >
> >
> >
> >
> >
> >
> > org.apache.maven.plugins
> > maven-surefire-plugin
> > 2.13
> >
> > false
> > true
> >
> >
> >
> > **/*Test.*
> > **/*Suite.*
> >
> >
> >
> >
> > org.apache.maven.plugins
> > maven-shade-plugin
> > 2.2
> >
> >
> >
> > >
> implementation="org.apache..plugins.shade.resource.ApacheLicenseResourceTransformer">
> >
> > >
> implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer">
> > reference.conf
> >
> >
> >
> >
> >
> > package
> >
> > shade
> >
> >
> >
> >
> >
> >
> >
> >
> > Was wondering what I am missing, since the jar built and a MANIFEST.MF
> file
> > is created, not sure why it is looking for a signature file digest, am I
> > missing some exclusion clause maybe?
> >
> > I saw a thread based on SBT and tried using the --deploy-mode client
> option;
> > even though, my understanding is by default it would use that mode
> anyway.
> >
> >
> >
> >
> > --
> > View this message in context:
> http://apache-spark-user-list.1001560.n3.nabble.com/Invalid-signature-file-digest-for-Manifest-main-attributes-with-spark-job-built-using-maven-tp14299.html
> > Sent from the Apache Spark User List mailing list archive at Nabble.com.
> >
> > -
> > To unsubscribe, e-mail: user-unsubscr...@spark.apache.org
> > For additional commands, e-mail: user-h...@spark.apache.org
> >
>
Re: Invalid signature file digest for Manifest main attributes with spark job built using maven
>
>
>
> junit
> junit
> 4.11
> test
>
>
> org.specs2
> specs2_${scala.tools.version}
> 1.13
> test
>
>
> org.scalatest
> scalatest_${scala.tools.version}
> 2.0.M6-SNAP8
> test
>
>
>
>
> src/main/scala
> src/test/scala
>
>
>
> net.alchim31.maven
> scala-maven-plugin
> 3.1.3
>
>
>
> compile
> testCompile
>
>
>
> -make:transitive
> -dependencyfile
> ${project.build.directory}/.scala_dependencies
>
>
>
>
>
>
> org.apache.maven.plugins
> maven-surefire-plugin
> 2.13
>
> false
> true
>
>
>
> **/*Test.*
> **/*Suite.*
>
>
>
>
> org.apache.maven.plugins
> maven-shade-plugin
> 2.2
>
>
>
> implementation="org.apache..plugins.shade.resource.ApacheLicenseResourceTransformer">
>
> implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer">
> reference.conf
>
>
>
>
>
> package
>
> shade
>
>
>
>
>
>
>
>
> Was wondering what I am missing, since the jar built and a MANIFEST.MF file
> is created, not sure why it is looking for a signature file digest, am I
> missing some exclusion clause maybe?
>
> I saw a thread based on SBT and tried using the --deploy-mode client option;
> even though, my understanding is by default it would use that mode anyway.
>
>
>
>
> --
> View this message in context:
> http://apache-spark-user-list.1001560.n3.nabble.com/Invalid-signature-file-digest-for-Manifest-main-attributes-with-spark-job-built-using-maven-tp14299.html
> Sent from the Apache Spark User List mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: user-unsubscr...@spark.apache.org
> For additional commands, e-mail: user-h...@spark.apache.org
>
-
To unsubscribe, e-mail: user-unsubscr...@spark.apache.org
For additional commands, e-mail: user-h...@spark.apache.org
Invalid signature file digest for Manifest main attributes with spark job built using maven
reference.conf package shade Was wondering what I am missing, since the jar built and a MANIFEST.MF file is created, not sure why it is looking for a signature file digest, am I missing some exclusion clause maybe? I saw a thread based on SBT and tried using the --deploy-mode client option; even though, my understanding is by default it would use that mode anyway. -- View this message in context: http://apache-spark-user-list.1001560.n3.nabble.com/Invalid-signature-file-digest-for-Manifest-main-attributes-with-spark-job-built-using-maven-tp14299.html Sent from the Apache Spark User List mailing list archive at Nabble.com. - To unsubscribe, e-mail: user-unsubscr...@spark.apache.org For additional commands, e-mail: user-h...@spark.apache.org
