Re: Using scala-2.11 when making changes to spark source

The effects of changing the pom.xml extend beyond cases in which we wish to modify spark itself. In addition when git pull'ing from trunk we need to either stash or roll back the changes before rebase'ing. An effort to look into a better solution (possibly including evaluating Ted Yu's suggested

Re: Using scala-2.11 when making changes to spark source

Maybe the following can be used for changing Scala version: http://maven.apache.org/archetype/maven-archetype-plugin/ I played with it a little bit but didn't get far. FYI On Sun, Sep 20, 2015 at 6:18 AM, Stephen Boesch wrote: > > The dev/change-scala-version.sh [2.11]

Using scala-2.11 when making changes to spark source

The dev/change-scala-version.sh [2.11] script modifies in-place the pom.xml files across all of the modules. This is a git-visible change. So if we wish to make changes to spark source in our own fork's - while developing with scala 2.11 - we would end up conflating those updates with our own.