[DISCUSS] Scala components in ASF Camel

classic Classic list List threaded Threaded
19 messages Options
Reply | Threaded
Open this post in threaded view
|

[DISCUSS] Scala components in ASF Camel

hekonsek
Hi,

We've been discussing lately [1] how should we handle components
referencing Scala libraries. The discussion seems to become suspended
without the final punchline, so I would like to rise this topic again
so we could settle some agreement for this issue.

As a reminder - the topic under the discussion is whether components
written in Scala should be maintained under the umbrella of ASF Camel.
Of course we are talking only about the cases when the subject of the
component is written is Scala (Akka, Scomp, etc.).

I'm the proponent of accepting the Scala-related contributions for ASF
Camel. In my opinion we shouldn't deter Scala people from our
community. I also think that we got enough Scala-enabled developers
here in Camel to handle the maintenance of the Scala components. On
the other side some of the committers got some doubts regarding our
ability to maintain Scala contributions on the sufficient level of
quality.

In the discussion thread [1] I mentioned at the beginning of my mail
the following propositions have been raised:
* create separated community for the Scala components (like Camel Extra)
* host Scala components on Camel-Extra
* accept components only if N committers would declare that they will
maintain the component
* create "Scala team" from the committers declaring to maintain the
Scala-related contributions
* use Java to write components referencing Scala libraries
* say "host it on github" to contributors :)

I would like us to discuss the proposed options and probably come with
some further ideas. There are people interested in the future of Scala
in Camel, so I believe that finally we should come up with a concrete
strategy for Scala contributions.

Best regards.

[1] http://camel.465427.n5.nabble.com/Re-Contributing-Scomp-Component-was-Contributing-Stomp-Component-td5726868.html

--
Henryk Konsek
http://henryk-konsek.blogspot.com
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Scala components in ASF Camel

Christian Mueller
Administrator
Hello Henryk,

thanks for revive this discussion.

+1 to host it outside from the official ASF Camel source repository
(GitHub, Google code, ...) from people with strong Scala knowledge and add
a link from our components site (external components section) [1].
+1 to host it at the official ASF Camel source repository if it's a Java
component and the license of the dependent library is Apache friendly.

[1] http://camel.apache.org/components.html

Best,
Christian

On Sun, Feb 17, 2013 at 11:25 AM, Henryk Konsek <[hidden email]> wrote:

> Hi,
>
> We've been discussing lately [1] how should we handle components
> referencing Scala libraries. The discussion seems to become suspended
> without the final punchline, so I would like to rise this topic again
> so we could settle some agreement for this issue.
>
> As a reminder - the topic under the discussion is whether components
> written in Scala should be maintained under the umbrella of ASF Camel.
> Of course we are talking only about the cases when the subject of the
> component is written is Scala (Akka, Scomp, etc.).
>
> I'm the proponent of accepting the Scala-related contributions for ASF
> Camel. In my opinion we shouldn't deter Scala people from our
> community. I also think that we got enough Scala-enabled developers
> here in Camel to handle the maintenance of the Scala components. On
> the other side some of the committers got some doubts regarding our
> ability to maintain Scala contributions on the sufficient level of
> quality.
>
> In the discussion thread [1] I mentioned at the beginning of my mail
> the following propositions have been raised:
> * create separated community for the Scala components (like Camel Extra)
> * host Scala components on Camel-Extra
> * accept components only if N committers would declare that they will
> maintain the component
> * create "Scala team" from the committers declaring to maintain the
> Scala-related contributions
> * use Java to write components referencing Scala libraries
> * say "host it on github" to contributors :)
>
> I would like us to discuss the proposed options and probably come with
> some further ideas. There are people interested in the future of Scala
> in Camel, so I believe that finally we should come up with a concrete
> strategy for Scala contributions.
>
> Best regards.
>
> [1]
> http://camel.465427.n5.nabble.com/Re-Contributing-Scomp-Component-was-Contributing-Stomp-Component-td5726868.html
>
> --
> Henryk Konsek
> http://henryk-konsek.blogspot.com
>



--
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Scala components in ASF Camel

iocanel
In reply to this post by hekonsek
I prefer having all sources in java, however not accepting scala
contributions in the community doesn't seem right to me.
I'd say let's try to keep everything java, but if there is a good reason
for people using scala and we have a good number of committers willing to
work in scala a scala-components module doesn't sound bad to me.


--
*Ioannis Canellos*
*

**
Blog: http://iocanel.blogspot.com
**
Twitter: iocanel
*
Ioannis Canellos
http://iocanel.blogspot.com
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Scala components in ASF Camel

Willem.Jiang
Administrator
In reply to this post by hekonsek
Hi,

Scala is hot, I'm willing to help the Scala related components in Apache camel repository.
Once we have more Scala components, we could attract more Scala developers :)

BTW, it doesn't spend us lots of time to maintain the camel-scala component.  

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, and we do the release as the more Scala project does. That could be a part of work in our Camel 3.0 plan.

Any thought?


--  
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, February 17, 2013 at 6:25 PM, Henryk Konsek wrote:

> Hi,
>  
> We've been discussing lately [1] how should we handle components
> referencing Scala libraries. The discussion seems to become suspended
> without the final punchline, so I would like to rise this topic again
> so we could settle some agreement for this issue.
>  
> As a reminder - the topic under the discussion is whether components
> written in Scala should be maintained under the umbrella of ASF Camel.
> Of course we are talking only about the cases when the subject of the
> component is written is Scala (Akka, Scomp, etc.).
>  
> I'm the proponent of accepting the Scala-related contributions for ASF
> Camel. In my opinion we shouldn't deter Scala people from our
> community. I also think that we got enough Scala-enabled developers
> here in Camel to handle the maintenance of the Scala components. On
> the other side some of the committers got some doubts regarding our
> ability to maintain Scala contributions on the sufficient level of
> quality.
>  
> In the discussion thread [1] I mentioned at the beginning of my mail
> the following propositions have been raised:
> * create separated community for the Scala components (like Camel Extra)
> * host Scala components on Camel-Extra
> * accept components only if N committers would declare that they will
> maintain the component
> * create "Scala team" from the committers declaring to maintain the
> Scala-related contributions
> * use Java to write components referencing Scala libraries
> * say "host it on github" to contributors :)
>  
> I would like us to discuss the proposed options and probably come with
> some further ideas. There are people interested in the future of Scala
> in Camel, so I believe that finally we should come up with a concrete
> strategy for Scala contributions.
>  
> Best regards.
>  
> [1] http://camel.465427.n5.nabble.com/Re-Contributing-Scomp-Component-was-Contributing-Stomp-Component-td5726868.html
>  
> --
> Henryk Konsek
> http://henryk-konsek.blogspot.com



Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Scala components in ASF Camel

hekonsek
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
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Scala components in ASF Camel

Łukasz Dywicki
I know there are some people who are able to support scala in Camel repositories. However the main problem I see is lack of organization in camel codebase. Camel has gazilion of similar components which doesn't share anything except core dependency. There is lack of any abstractions for queueing components. Introduction of scala may just make things worse since some functionality will be never ported to Java API. If you could take a look on JMS/SJMS components you will see same constants put in different utility classes. Both components do same things, support same syntax of destination selecting (another portion of duplicated code) and must use connection factory.

Now, when I see a Scala on horizon I am afraid that components written in Java will be slowly replaced by Scala. There is already an old camel-stomp component on github [1], but it was written without scala wrapper library. Quo vadis Camel?

[1] https://github.com/pedroteixeira/camel-stomp

Cheers, :-)
Łukasz Dywicki
--
[hidden email]
Twitter: ldywicki
Blog: http://dywicki.pl
Code-House - http://code-house.org

Wiadomość napisana przez Henryk Konsek <[hidden email]> w dniu 18 lut 2013, o godz. 11:18:

> 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

Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Scala components in ASF Camel

hekonsek
> However the main problem I see is lack of organization in camel codebase.
> Camel has gazilion of similar components which doesn't share anything except core dependency.

Actually I must disagree as in my humble opinion organization of Camel
code and it's internal reusability has nothing to do with writing
Scala-related components in Scala.

> There is lack of any abstractions for queueing components.
> Introduction of scala may just make things worse since some functionality will be never
> ported to Java API.

Unfortunately I must disagree again :) . If we come up with common
components utility, we will create Scala wrapper over it and use this
shared abstraction in Scala components as well.

> Now, when I see a Scala on horizon I am afraid that components written in Java will be slowly replaced by Scala.

Nobody suggested to use Scala to write components referencing Java
libraries. The subject of the discussion is focused only on components
over Scala libraries.

--
Henryk Konsek
http://henryk-konsek.blogspot.com
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Scala components in ASF Camel

hekonsek
This discussion seems to become stalled again. As we cannot settle a
clear agreement on this, maybe we should create a Scala components
community on GitHub? I would prefer to have Scala stuff under ASF
umbrella, but I don't want to push the idea when Hadrian and Christian
has some objections.

I want to have a single place where we can put Scala components for
Camel. The place we can refer to when somebody propose Scala-based
contribution. If at some point of time we decide that Scala should be
hosted here at ASF, then we can move GitHub contributions to ASF.

I can organize this repository. Just want to have some more opinions about it.

Best regards.

--
Henryk Konsek
http://henryk-konsek.blogspot.com
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Scala components in ASF Camel

Willem.Jiang
Administrator
+1 for put the Scala related components in ASF Camel repo, but we can start the initial work in GitHub.
It is not hard to move the code from GitHub to ASF Camel repo if the license is OK.


--  
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 Thursday, February 21, 2013 at 8:38 PM, Henryk Konsek wrote:

> This discussion seems to become stalled again. As we cannot settle a
> clear agreement on this, maybe we should create a Scala components
> community on GitHub? I would prefer to have Scala stuff under ASF
> umbrella, but I don't want to push the idea when Hadrian and Christian
> has some objections.
>  
> I want to have a single place where we can put Scala components for
> Camel. The place we can refer to when somebody propose Scala-based
> contribution. If at some point of time we decide that Scala should be
> hosted here at ASF, then we can move GitHub contributions to ASF.
>  
> I can organize this repository. Just want to have some more opinions about it.
>  
> Best regards.
>  
> --  
> Henryk Konsek
> http://henryk-konsek.blogspot.com



Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Scala components in ASF Camel

Christian Mueller
Administrator
In reply to this post by hekonsek
+1 I like this proposal.

Sent from a mobile device
Am 21.02.2013 13:38 schrieb "Henryk Konsek" <[hidden email]>:

> This discussion seems to become stalled again. As we cannot settle a
> clear agreement on this, maybe we should create a Scala components
> community on GitHub? I would prefer to have Scala stuff under ASF
> umbrella, but I don't want to push the idea when Hadrian and Christian
> has some objections.
>
> I want to have a single place where we can put Scala components for
> Camel. The place we can refer to when somebody propose Scala-based
> contribution. If at some point of time we decide that Scala should be
> hosted here at ASF, then we can move GitHub contributions to ASF.
>
> I can organize this repository. Just want to have some more opinions about
> it.
>
> Best regards.
>
> --
> Henryk Konsek
> http://henryk-konsek.blogspot.com
>
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Scala components in ASF Camel

hekonsek
> +1 I like this proposal.

I'll create the GitHub organization called 'camel-marketplace'. Then
I'll create 'camel-scala' and 'camel-scala-extra' projects under its
umbrella. If anybody of you want to be added as an administrator to
the 'camel-marketplace' organization, please just drop me a line.

All the contributions to the 'camel-scala' will be released under
Apache license. Contributions under incompatible licenses will be
committed to 'camel-scala-extra'.

After I create the projects together with some nice homepages for
them, I'll add appropriate references to the Camel Contributing [1]
and Camel Components [1] pages. From this point forward we could refer
to these projects as to the official home for the Camel components
written in Scala.

The versioning and the life cycle of Scala communities will be
synchronized with ASF Camel release the same way as Camel Extra is.

What do you think?

[1] http://camel.apache.org/contributing.html
[2] http://camel.apache.org/components.html

--
Henryk Konsek
http://henryk-konsek.blogspot.com
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Scala components in ASF Camel

hadrian
I would give this a bit more time, maybe after apachecon. While Willem
stated that it's easy to move code back and forth, his statement is not
correct. It would be if there were no external contributors, otherwise
you have ip issues (which is different than the way it's licensed).

I think a marketplace is a good idea, but personally I will not spend
time on the scala ecosystem. It's not clear to me if we all understand
the solution you propose the same way. I am not even sure if we all
understand/agree on the problem the same way.

My $0.02,
Hadrian



On 02/22/2013 09:55 AM, Henryk Konsek wrote:

>> +1 I like this proposal.
>
> I'll create the GitHub organization called 'camel-marketplace'. Then
> I'll create 'camel-scala' and 'camel-scala-extra' projects under its
> umbrella. If anybody of you want to be added as an administrator to
> the 'camel-marketplace' organization, please just drop me a line.
>
> All the contributions to the 'camel-scala' will be released under
> Apache license. Contributions under incompatible licenses will be
> committed to 'camel-scala-extra'.
>
> After I create the projects together with some nice homepages for
> them, I'll add appropriate references to the Camel Contributing [1]
> and Camel Components [1] pages. From this point forward we could refer
> to these projects as to the official home for the Camel components
> written in Scala.
>
> The versioning and the life cycle of Scala communities will be
> synchronized with ASF Camel release the same way as Camel Extra is.
>
> What do you think?
>
> [1] http://camel.apache.org/contributing.html
> [2] http://camel.apache.org/components.html
>
> --
> Henryk Konsek
> http://henryk-konsek.blogspot.com
>
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Scala components in ASF Camel

Claus Ibsen-2
In reply to this post by hekonsek
On Fri, Feb 22, 2013 at 3:55 PM, Henryk Konsek <[hidden email]> wrote:

>> +1 I like this proposal.
>
> I'll create the GitHub organization called 'camel-marketplace'. Then
> I'll create 'camel-scala' and 'camel-scala-extra' projects under its
> umbrella. If anybody of you want to be added as an administrator to
> the 'camel-marketplace' organization, please just drop me a line.
>
> All the contributions to the 'camel-scala' will be released under
> Apache license. Contributions under incompatible licenses will be
> committed to 'camel-scala-extra'.
>
> After I create the projects together with some nice homepages for
> them, I'll add appropriate references to the Camel Contributing [1]
> and Camel Components [1] pages. From this point forward we could refer
> to these projects as to the official home for the Camel components
> written in Scala.
>
> The versioning and the life cycle of Scala communities will be
> synchronized with ASF Camel release the same way as Camel Extra is.
>
> What do you think?
>

Got a little wifi time. I think you are jumping to action too fast.
Since this is about setting up new project sites which would be
affiliated with ASF Camel.
Then with my PMC hat I would like to reconsider this, and as well gime
more time for people
and PMC members to think about this as well.

At first though this seems also overkill to do all this work for a few
Scala components.
I do not mind hosting and supporting Scala components at ASF if these
components is
natural Scala libraries and frameworks.

For example a camel-play component to integrate with the Scala Play
Framework etc.



> [1] http://camel.apache.org/contributing.html
> [2] http://camel.apache.org/components.html
>
> --
> Henryk Konsek
> http://henryk-konsek.blogspot.com



--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: [hidden email]
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Scala components in ASF Camel

Claus Ibsen-2
In reply to this post by iocanel
On Sun, Feb 17, 2013 at 8:52 PM, Ioannis Canellos <[hidden email]> wrote:
> I prefer having all sources in java, however not accepting scala
> contributions in the community doesn't seem right to me.
> I'd say let's try to keep everything java, but if there is a good reason
> for people using scala and we have a good number of committers willing to
> work in scala a scala-components module doesn't sound bad to me.
>

+1

I dont see much interrest in creating Scala based components for
Camel, just because its Scala programming language. Though having a
number of Camel components using Scala because they integrate with
Scala
based libraries is OKAY with me. Though if someone creates a new Camel
component to integration with Facebook, then I would favor that being
Java based.

I guess what triggered this was that Stomp component that was Scala
based, because it uses a Scala library for the STOMP communication. If
I had a choice and there was a pure Java stomp client I would favor
that over the Scala based. But I guess there is not, so I am okay with
the camel-stomp being Scala based for now.

The only concern for Scala based components is the bad backwards
compatability Scala has. eg the Scala 2.9 vs 2.10 debacle. I think for
Scala based components we cannot dual support both Scala 2.9 and 2.10
binary releases. And therefore they would be Scala 2.10 based for now.

>
> --
> *Ioannis Canellos*
> *
>
> **
> Blog: http://iocanel.blogspot.com
> **
> Twitter: iocanel
> *



--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: [hidden email]
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Scala components in ASF Camel

hekonsek
In reply to this post by Claus Ibsen-2
> I think you are jumping to action too fast.

Fear not, I won't perform anything without your acceptance. Just
wanted to animate the discussion a little bit :) .

--
Henryk Konsek
http://henryk-konsek.blogspot.com
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Scala components in ASF Camel

Christian Mueller
Administrator
In reply to this post by hekonsek
Hello Henryk,

please find my comments inline.

Best,
Christian

On Fri, Feb 22, 2013 at 3:55 PM, Henryk Konsek <[hidden email]> wrote:

> > +1 I like this proposal.
>
> I'll create the GitHub organization called 'camel-marketplace'. Then
> I'll create 'camel-scala' and 'camel-scala-extra' projects under its
> umbrella. If anybody of you want to be added as an administrator to
> the 'camel-marketplace' organization, please just drop me a line.
>
> All the contributions to the 'camel-scala' will be released under
> Apache license. Contributions under incompatible licenses will be
> committed to 'camel-scala-extra'.
>
I would be lazy. Only create the "camel-scala-extra" project if needed...

>
> After I create the projects together with some nice homepages for
> them, I'll add appropriate references to the Camel Contributing [1]
> and Camel Components [1] pages. From this point forward we could refer
> to these projects as to the official home for the Camel components
> written in Scala.
>
Be careful. What do you mean with "the official home for the Camel
components written in Scala"?
This is not an ASF project! There are may Apache (Camel) committers who
also will work in this project. And this project is related to an Apache
project because it provides some "extensions" for it. But nothing more.
It's ok to add it to the Camel Components page. But it's not ok to put it
on the Camel Contributing page for the reason I mentioned before.


>
> The versioning and the life cycle of Scala communities will be
> synchronized with ASF Camel release the same way as Camel Extra is.
>
Bit of work but sounds good.



--
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Scala components in ASF Camel

dkulp@apache.org
In reply to this post by Claus Ibsen-2

The other issue *I* have with Scala stuff in the main camel build is the difficulty in getting those modules into the various IDEs. (eclipse in particular)

I'm wondering if it makes sense to put Scala stuff at Apache, but into a Camel sub-project type of thing.    camel/scala-components/trunk type thing.  It could have it's own releases (with whatever Scala version is popular at the time), etc…   This could also be a kind of "pilot" program for possibly having individual component releases so in the future, we could get away from  the "release every component" thing, if we decide to go that way.

Anyway, just a though.   If we can do it at Apache, I'd definitely prefer it, but mixing the Scala and Java stuff together into a single build just feels weird and has issues.


Dan


On Feb 22, 2013, at 10:16 AM, Claus Ibsen <[hidden email]> wrote:

> On Sun, Feb 17, 2013 at 8:52 PM, Ioannis Canellos <[hidden email]> wrote:
>> I prefer having all sources in java, however not accepting scala
>> contributions in the community doesn't seem right to me.
>> I'd say let's try to keep everything java, but if there is a good reason
>> for people using scala and we have a good number of committers willing to
>> work in scala a scala-components module doesn't sound bad to me.
>>
>
> +1
>
> I dont see much interrest in creating Scala based components for
> Camel, just because its Scala programming language. Though having a
> number of Camel components using Scala because they integrate with
> Scala
> based libraries is OKAY with me. Though if someone creates a new Camel
> component to integration with Facebook, then I would favor that being
> Java based.
>
> I guess what triggered this was that Stomp component that was Scala
> based, because it uses a Scala library for the STOMP communication. If
> I had a choice and there was a pure Java stomp client I would favor
> that over the Scala based. But I guess there is not, so I am okay with
> the camel-stomp being Scala based for now.
>
> The only concern for Scala based components is the bad backwards
> compatability Scala has. eg the Scala 2.9 vs 2.10 debacle. I think for
> Scala based components we cannot dual support both Scala 2.9 and 2.10
> binary releases. And therefore they would be Scala 2.10 based for now.
>
>>
>> --
>> *Ioannis Canellos*
>> *
>>
>> **
>> Blog: http://iocanel.blogspot.com
>> **
>> Twitter: iocanel
>> *
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Email: [hidden email]
> Web: http://fusesource.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen

--
Daniel Kulp
[hidden email] - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com

Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Scala components in ASF Camel

hekonsek
In reply to this post by Christian Mueller
> Christian:
> Be careful. What do you mean with "the official home for the Camel
> components written in Scala"?
> This is not an ASF project! There are may Apache (Camel) committers who
> also will work in this project.

Camel Scala would be "official" the same way as Camel Extra is.
Formally it is not managed by ASF, but in fact Camel Extra maintainers
are ASF people.

I'll try to be politically correct here. Instead of "official" I would
say "endorsed by the majority of ASF committers" :) .

--
Henryk Konsek
http://henryk-konsek.blogspot.com
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSS] Scala components in ASF Camel

hekonsek
In reply to this post by dkulp@apache.org
> I'm wondering if it makes sense to put Scala stuff at Apache, but into a Camel sub-project type of thing.
> camel/scala-components/trunk type thing.  It could have it's own releases

Sounds perfect for me. As long as Scala goodies have their own place,
I'm be more than happy :) .

Best regards.

--
Henryk Konsek
http://henryk-konsek.blogspot.com