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 approach) might be considered? 2015-09-20 9:12 GMT-07:00 Ted Yu <yuzhih...@gmail.com>: > 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 <java...@gmail.com> wrote: > >> >> 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. >> >> A possible scenario would be to update .gitignore - by adding pom.xml. >> However I can not get that to work: .gitignore is tricky. >> >> Suggestions appreciated. >> > >
