On Mon, Jan 28, 2013 at 10:52 AM, Claus Ibsen <claus.ib...@gmail.com> wrote: > On Mon, Jan 28, 2013 at 6:34 AM, Willem jiang <willem.ji...@gmail.com> wrote: >> +1 for the micro-branch for the camel-scala, and we can do the release it >> after major release of camel. >> > > I am wondering if we can add a camel-scala-2.9 module to the source code. > And this is a shallow module, that has some maven plugins, that copies > the src from the "real" camel-scala module > But just compiles against scala 2.9 > > Then I guess we can have both modules done in the same release. The > caveat is that the source must be compileable > for both 2.9 and 2.10 at the same time. But I dont think there is any > such problems. > > Also we cannot support older Scala releases forever. Camel 2.11 is > having a support lifecycle for about 18 months or so. > That is a long time to still support Scala 2.9 etc. >
I am just looking at the "king of all Scala projects" = Akka And they do not support Scala 2.9 for their latest stable release of Akka, eg 2.1.0 http://typesafe.com/stack/downloads/akka So if they do not do that, we may also consider not supporting Scala 2.9. > > > >> >> -- >> Willem Jiang >> >> Red Hat, Inc. >> FuseSource is now part of Red Hat >> Web: http://www.fusesource.com | http://www.redhat.com >> Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) >> (English) >> http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese) >> Twitter: willemjiang >> Weibo: 姜宁willem >> >> >> >> >> >> On Sunday, January 27, 2013 at 4:27 AM, Henryk Konsek wrote: >> >>> > There must be other project in the same unfortunate situation about Scala >>> > >>> > Anyone knows of other Maven based projects what they do? >>> >>> Camel is quite specific in this regards as it is not pure-Scala project. >>> >>> In my humble opinion the Camel way of handling Scala compatibility >>> issue is to fork only camel-scala module. This approach works like a >>> micro-branch. >>> >>> I would keep existing camel-scala module as a 2.9 branch, and created >>> forked camel-scala_2.10 module. By doing this, we will not force Scala >>> 2.9 users to change their dependencies. >>> >>> I also suggest to keep org.apache.camel.scala package name in both >>> modules. This will make easier for users to upgrade their routes to >>> the higher version of Scala. >>> >>> Any other ideas and approaches for the problem will be highly appreciated >>> :) . >>> >>> -- >>> Henryk Konsek >>> http://henryk-konsek.blogspot.com >> >> >> > > > > -- > Claus Ibsen > ----------------- > Red Hat, Inc. > FuseSource is now part of Red Hat > Email: cib...@redhat.com > Web: http://fusesource.com > Twitter: davsclaus > Blog: http://davsclaus.com > Author of Camel in Action: http://www.manning.com/ibsen -- Claus Ibsen ----------------- Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
