Hello @menishmueli,
So - my PR was closed with your comment "Already did it few days ago, will be added in the next version"
OK - so - I do not see any change in the build.sbt and also the scala library is still included in the plugin although it is present in the spark/jars directory as well. Funny things can happen when both versions are present.
Could you just simply add the flag assembly / assemblyPackageScala / assembleArtifact := false, as I did in the PR so that the scala library itself is not added to the fat jars, because this messes up the class path a little, please! In most scenarios the current setup shouldn't be a problem with spark but in our case it is/was.
Or is there any good reason to supply your own version of the scala library along with your plugin that I do not know about?
Thanks!
Hello @menishmueli,
So - my PR was closed with your comment "Already did it few days ago, will be added in the next version"
OK - so - I do not see any change in the
build.sbtand also the scala library is still included in the plugin although it is present in the spark/jars directory as well. Funny things can happen when both versions are present.Could you just simply add the flag
assembly / assemblyPackageScala / assembleArtifact := false,as I did in the PR so that the scala library itself is not added to the fat jars, because this messes up the class path a little, please! In most scenarios the current setup shouldn't be a problem with spark but in our case it is/was.Or is there any good reason to supply your own version of the scala library along with your plugin that I do not know about?
Thanks!