50 Add cross compilation ability#52
Conversation
dk1844
left a comment
There was a problem hiding this comment.
Will it play nice with the release plugin?
We probably want to release both 2.11 & 2.12 versions with the same version number, so at-once somehow. I wonder if we can.
| <scala.binary.version>2.11</scala.binary.version> | ||
|
|
||
| <!-- Frameworks and libraries --> | ||
| <json4s.version>3.5.3</json4s.version> <!-- This version is set to be compatible with Spark 2.4.5 --> |
There was a problem hiding this comment.
The comment scares me a bit.
I have a hunch that we don't know if this will work with Spark 3, yet.
There was a problem hiding this comment.
Yeah, I am trying to take it one problem at a time. Also, I think this was a problem from 2.2 to 2.4. Version 3 could be fine.
There was a problem hiding this comment.
Spline agent is being tested with Spark 3.0. AFAIK our commons Json4s wrapper works fine in all versions
This is a setup used by our commons so it should |
If we're talking about The actual deployment is than done from the tag by running several builds, one per Scala version. |
| # syntax: regexp | ||
| # ^\.pc/ | ||
|
|
||
| pom.xml.bkp |
There was a problem hiding this comment.
A side effect of the cross compilation plugin
Co-authored-by: David Benedeki <14905969+benedeki@users.noreply.github.com>
Uses @wajda 's cross-compilation plugin adds 2.11 and 2.12 compilations
Fixes #50