Hello, On Mon, Apr 6, 2020 at 3:31 PM Koert Kuipers <ko...@tresata.com> wrote:
> actually i might be wrong about this. did you declare scala to be a > provided dependency? so scala is not in your fat/uber jar? if so then maybe > it will work. > I declare spark to be a provided dependency, so Scala's not included in my artifact except for this single callsite. Thanks Andrew > On Mon, Apr 6, 2020 at 4:16 PM Andrew Melo <andrew.m...@gmail.com> wrote: > >> >> >> On Mon, Apr 6, 2020 at 3:08 PM Koert Kuipers <ko...@tresata.com> wrote: >> >>> yes it will >>> >>> >> Ooof, I was hoping that wasn't the case. I guess I need to figure out how >> to get Maven to compile/publish jars with different >> dependencies/artifactIDs like how sbt does? (or re-implement the >> functionality in java) >> >> Thanks for your help, >> Andrew >> >> >>> On Mon, Apr 6, 2020 at 3:50 PM Andrew Melo <andrew.m...@gmail.com> >>> wrote: >>> >>>> Hello all, >>>> >>>> I'm aware that Scala is not binary compatible between revisions. I have >>>> some Java code whose only Scala dependency is the transitive dependency >>>> through Spark. This code calls a Spark API which returns a Seq<Path>, which >>>> I then convert into a List<Path> with >>>> JavaConverters.seqAsJavaListConverter. Will this usage cause binary >>>> incompatibility if the jar is compiled in one Scala version and executed in >>>> another? >>>> >>>> I tried grokking >>>> https://docs.scala-lang.org/overviews/core/binary-compatibility-of-scala-releases.html, >>>> and wasn't quite able to make heads or tails of this particular case. >>>> >>>> Thanks! >>>> Andrew >>>> >>>> >>>>
