Spark currently only provides pre-builds for 2.10 and requires custom build
for 2.11.
Not sure whether this is the best idea, but I can see the benefits from a
project management point of view...
Would you prefer to have a {scala_version} × {hadoop_version} integrated on
the website?
2015-03-02 16:57 GMT+01:00 Aljoscha Krettek <aljos...@apache.org>:
> +1 I also like it. We just have to figure out how we can publish two
> sets of release artifacts.
>
> On Mon, Mar 2, 2015 at 4:48 PM, Stephan Ewen <se...@apache.org> wrote:
> > Big +1 from my side!
> >
> > Does it have to be a Maven profile, or does a maven property work?
> (Profile
> > may be needed for quasiquotes dependency?)
> >
> > On Mon, Mar 2, 2015 at 4:36 PM, Alexander Alexandrov <
> > alexander.s.alexand...@gmail.com> wrote:
> >
> >> Hi there,
> >>
> >> since I'm relying on Scala 2.11.4 on a project I've been working on, I
> >> created a branch which updates the Scala version used by Flink from
> 2.10.4
> >> to 2.11.4:
> >>
> >> https://github.com/stratosphere/flink/commits/scala_2.11
> >>
> >> Everything seems to work fine and the PR contains minor changes
> compared to
> >> Spark:
> >>
> >> https://issues.apache.org/jira/browse/SPARK-4466
> >>
> >> If you're interested, I can rewrite this as a Maven Profile and open a
> PR
> >> so people can build Flink with 2.11 support.
> >>
> >> I suggest to do this sooner rather than later in order to
> >>
> >> * the number of code changes enforced by migration small and tractable;
> >> * discourage the use of deprecated or 2.11-incompatible source code in
> >> future commits;
> >>
> >> Regards,
> >> A.
> >>
>
