On Fri, Jan 25, 2013 at 5:05 PM, Henryk Konsek <hekon...@gmail.com> wrote: >> Totally agree. The Scala way to do is to build and publish camel-scala_2.9.2- >> 2.11.0.jar and camel-scala_2.10-2.11.0.jar > > I reopened the Scala 2.10 issue [1] so we might settle an agreement on > how Scala backwards compatibility should be handled in Camel. > > +1 for renaming existing Scala module to camel-scala_2.9.2 and > creating new camel-scala_2.10 module (by cloning). > > [1] https://issues.apache.org/jira/browse/CAMEL-6011 >
Yes we can take a look what is feasible to have both a 2.9 and 2.10 scala binary compatible of camel-scala for the upcoming 2.11 release of Camel. For the scalate project it looks as if they branched the source code and cut a release of the branch especially for 2.9 scala https://github.com/scalate/scalate/commit/c3fe71ed5418c9da35a62dbba4b77647f975b711 This is not possible with how we cut releases at ASF Camel as its one giant release cycle. So I dont think we have an easy way of doing this. There must be other project in the same unfortunate situation about Scala Anyone knows of other Maven based projects what they do? > -- > 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
