Re: Invalid signature file digest for Manifest main attributes with spark job built using maven

2014-09-16 Thread Kevin Peng 
-${cdh.version}/version
  /dependency
  dependency
groupIdorg.apache.spark/groupId
artifactIdspark-streaming_2.10/artifactId
version1.0.0-${cdh.version}/version
  /dependency
  dependency
groupIdorg.apache.flume/groupId
artifactIdflume-ng-sdk/artifactId
version1.5.0-${cdh.version}/version
 
exclusions
  exclusion
groupIdio.netty/groupId
artifactIdnetty/artifactId
  /exclusion
/exclusions
  /dependency
  dependency
groupIdorg.apache.flume/groupId
artifactIdflume-ng-core/artifactId
version1.5.0-${cdh.version}/version
 
exclusions
  exclusion
groupIdio.netty/groupId
artifactIdnetty/artifactId
  /exclusion
/exclusions
  /dependency
  dependency
groupIdorg.apache.hbase/groupId
artifactIdhbase-client/artifactId
version0.98.1-${cdh.version}/version
 
exclusions
  exclusion
groupIdio.netty/groupId
artifactIdnetty/artifactId
  /exclusion
/exclusions
  /dependency
  dependency
groupIdorg.apache.hadoop/groupId
artifactIdhadoop-client/artifactId
version2.3.0-${cdh.version}/version
 
  /dependency
 
 
  dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
version4.11/version
scopetest/scope
  /dependency
  dependency
groupIdorg.specs2/groupId
artifactIdspecs2_${scala.tools.version}/artifactId
version1.13/version
scopetest/scope
  /dependency
  dependency
groupIdorg.scalatest/groupId
artifactIdscalatest_${scala.tools.version}/artifactId
version2.0.M6-SNAP8/version
scopetest/scope
  /dependency
/dependencies
 
build
  sourceDirectorysrc/main/scala/sourceDirectory
  testSourceDirectorysrc/test/scala/testSourceDirectory
  plugins
plugin
 
  groupIdnet.alchim31.maven/groupId
  artifactIdscala-maven-plugin/artifactId
  version3.1.3/version
  executions
execution
  goals
goalcompile/goal
goaltestCompile/goal
  /goals
  configuration
args
  arg-make:transitive/arg
  arg-dependencyfile/arg
  arg${project.build.directory}/.scala_dependencies/arg
/args
  /configuration
/execution
  /executions
/plugin
plugin
  groupIdorg.apache.maven.plugins/groupId
  artifactIdmaven-surefire-plugin/artifactId
  version2.13/version
  configuration
useFilefalse/useFile
disableXmlReporttrue/disableXmlReport
 
 
includes
  include**/*Test.*/include
  include**/*Suite.*/include
/includes
  /configuration
/plugin
plugin
  groupIdorg.apache.maven.plugins/groupId
  artifactIdmaven-shade-plugin/artifactId
  version2.2/version
  configuration
 
transformers
  transformer
 
 implementation=org.apache..plugins.shade.resource.ApacheLicenseResourceTransformer
  /transformer
  transformer
 
 implementation=org.apache.maven.plugins.shade.resource.AppendingTransformer
resourcereference.conf/resource
  /transformer
/transformers
  /configuration
  executions
execution
  phasepackage/phase
  goals
goalshade/goal
  /goals
/execution
  /executions
/plugin
  /plugins
/build
  /project
 
  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

Invalid signature file digest for Manifest main attributes with spark job built using maven

2014-09-15 Thread kpeng1 
  groupIdorg.apache.hbase/groupId
  artifactIdhbase-client/artifactId
  version0.98.1-${cdh.version}/version
  
  exclusions
exclusion
  groupIdio.netty/groupId
  artifactIdnetty/artifactId
/exclusion
  /exclusions
/dependency
dependency
  groupIdorg.apache.hadoop/groupId
  artifactIdhadoop-client/artifactId
  version2.3.0-${cdh.version}/version
  
/dependency


dependency
  groupIdjunit/groupId
  artifactIdjunit/artifactId
  version4.11/version
  scopetest/scope
/dependency
dependency
  groupIdorg.specs2/groupId
  artifactIdspecs2_${scala.tools.version}/artifactId
  version1.13/version
  scopetest/scope
/dependency
dependency
  groupIdorg.scalatest/groupId
  artifactIdscalatest_${scala.tools.version}/artifactId
  version2.0.M6-SNAP8/version
  scopetest/scope
/dependency
  /dependencies

  build
sourceDirectorysrc/main/scala/sourceDirectory
testSourceDirectorysrc/test/scala/testSourceDirectory
plugins
  plugin

groupIdnet.alchim31.maven/groupId
artifactIdscala-maven-plugin/artifactId
version3.1.3/version
executions
  execution
goals
  goalcompile/goal
  goaltestCompile/goal
/goals
configuration
  args
arg-make:transitive/arg
arg-dependencyfile/arg
arg${project.build.directory}/.scala_dependencies/arg
  /args
/configuration
  /execution
/executions
  /plugin
  plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
version2.13/version
configuration
  useFilefalse/useFile
  disableXmlReporttrue/disableXmlReport
  
  
  includes
include**/*Test.*/include
include**/*Suite.*/include
  /includes
/configuration
  /plugin
  plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-shade-plugin/artifactId
version2.2/version
configuration
  
  transformers
transformer
implementation=org.apache..plugins.shade.resource.ApacheLicenseResourceTransformer
/transformer
transformer
implementation=org.apache.maven.plugins.shade.resource.AppendingTransformer
  resourcereference.conf/resource
/transformer
  /transformers
/configuration
executions
  execution
phasepackage/phase
goals
  goalshade/goal
/goals
  /execution
/executions
  /plugin
/plugins
  /build
/project

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

2014-09-15 Thread Sean Owen 
/groupId
   artifactIdflume-ng-sdk/artifactId
   version1.5.0-${cdh.version}/version

   exclusions
 exclusion
   groupIdio.netty/groupId
   artifactIdnetty/artifactId
 /exclusion
   /exclusions
 /dependency
 dependency
   groupIdorg.apache.flume/groupId
   artifactIdflume-ng-core/artifactId
   version1.5.0-${cdh.version}/version

   exclusions
 exclusion
   groupIdio.netty/groupId
   artifactIdnetty/artifactId
 /exclusion
   /exclusions
 /dependency
 dependency
   groupIdorg.apache.hbase/groupId
   artifactIdhbase-client/artifactId
   version0.98.1-${cdh.version}/version

   exclusions
 exclusion
   groupIdio.netty/groupId
   artifactIdnetty/artifactId
 /exclusion
   /exclusions
 /dependency
 dependency
   groupIdorg.apache.hadoop/groupId
   artifactIdhadoop-client/artifactId
   version2.3.0-${cdh.version}/version

 /dependency


 dependency
   groupIdjunit/groupId
   artifactIdjunit/artifactId
   version4.11/version
   scopetest/scope
 /dependency
 dependency
   groupIdorg.specs2/groupId
   artifactIdspecs2_${scala.tools.version}/artifactId
   version1.13/version
   scopetest/scope
 /dependency
 dependency
   groupIdorg.scalatest/groupId
   artifactIdscalatest_${scala.tools.version}/artifactId
   version2.0.M6-SNAP8/version
   scopetest/scope
 /dependency
   /dependencies

   build
 sourceDirectorysrc/main/scala/sourceDirectory
 testSourceDirectorysrc/test/scala/testSourceDirectory
 plugins
   plugin

 groupIdnet.alchim31.maven/groupId
 artifactIdscala-maven-plugin/artifactId
 version3.1.3/version
 executions
   execution
 goals
   goalcompile/goal
   goaltestCompile/goal
 /goals
 configuration
   args
 arg-make:transitive/arg
 arg-dependencyfile/arg
 arg${project.build.directory}/.scala_dependencies/arg
   /args
 /configuration
   /execution
 /executions
   /plugin
   plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-surefire-plugin/artifactId
 version2.13/version
 configuration
   useFilefalse/useFile
   disableXmlReporttrue/disableXmlReport


   includes
 include**/*Test.*/include
 include**/*Suite.*/include
   /includes
 /configuration
   /plugin
   plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-shade-plugin/artifactId
 version2.2/version
 configuration

   transformers
 transformer
 implementation=org.apache..plugins.shade.resource.ApacheLicenseResourceTransformer
 /transformer
 transformer
 implementation=org.apache.maven.plugins.shade.resource.AppendingTransformer
   resourcereference.conf/resource
 /transformer
   /transformers
 /configuration
 executions
   execution
 phasepackage/phase
 goals
   goalshade/goal
 /goals
   /execution
 /executions
   /plugin
 /plugins
   /build
 /project

 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