Some extra thoughts from my side. -1 for writing Scala-related components in Java Using Java to write components referencing Scala libraries is a bad idea in my humble opinion. Such code is hard to maintain and will not encourage Scala people to contribute. I also believe that if somebody doesn't know Scala, then he won't help us to maintain for example Akka anyway, even if the component itself is written in Java.
It would be nice if our community could communicate that we are open for Scala contributors here at Camel. I don't want us to create the vicious circle rejecting possible Scala committers from our community. I also think that creating another community will generate unnecessary release and maintenance burden. Take a look at Camel Extra and all the additional effort it requires. I understand that we need to keep Camel Extra separated due to the licensing reasons, so this burden is unavoidable. However this is avoidable in the case of Scala. Willem: > Scala is hot, I'm willing to help the Scala related components in Apache > camel repository. That makes two of us. Anybody else interested in showing Scala some extra love ? :) Willem: > As Scala has some back compatible issue, I think we can consider to create a > sub project in camel which can host the Scala related components The first (successful) attempt to settle strategy for handling binary compatibility has been done in camel-scala module. But I would defer this topic to another discussion, as Scala binary compatibility is a larger subject itself :) . Anybody any further thoughts? -- Henryk Konsek http://henryk-konsek.blogspot.com
