Hi
Camel 2.x is not active anymore. We only do security patch releases of
the 2.25.x branch.
2.x will be EOL in summer 2021 or later.
We do not accept new components or other development on Camel 2.x.
You can always build a custom component on your own and use it with Camel 2.x.
On Fri, Nov 6,
Hi Bennet
Yeah sure that sounds good, to have more validation at build time.
We have already a camel-maven-plugin that can do a bunch of stuff, but
it does not check properties files.
https://github.com/apache/camel/blob/master/tooling/maven/camel-maven-plugin/src/main/docs/camel-maven-plugin.ado
Hi Claus
Well I had the impression that 2.19 was about to close, so it would go into
the 2.20 release.
Didn't find the time to finish up the docs + features. I'll see if I can do
it do it in the coming day.
/Preben
--
View this message in context:
http://camel.465427.n5.nabble.com/Contributi
Hi Preben
Did you update your component? It would be good to get it in shape so
we can include it in the upcoming release.
On Fri, Apr 7, 2017 at 10:32 AM, Preben.Asmussen wrote:
> Sure I'll fix it + the doc and missing features during the weekend I hope.
>
> And thanks
>
> /Preben
>
>
>
> --
>
I started PR 1611 [1] as a base of discussion for "Camel Milo".
[1] https://github.com/apache/camel/pull/1611
On Fri, Apr 7, 2017 at 9:27 PM, Onder SEZGIN wrote:
> nice to hear that more iot support will come into camel.
>
> i'd be more than happy to contribute the. where i can.
>
> On Fri, 7 A
nice to hear that more iot support will come into camel.
i'd be more than happy to contribute the. where i can.
On Fri, 7 Apr 2017 at 11:32, Preben.Asmussen wrote:
> Sure I'll fix it + the doc and missing features during the weekend I hope.
>
> And thanks
>
> /Preben
>
>
>
> --
> View this mess
Sure I'll fix it + the doc and missing features during the weekend I hope.
And thanks
/Preben
--
View this message in context:
http://camel.465427.n5.nabble.com/Contributing-a-set-of-IoT-related-components-tp5797075p5797131.html
Sent from the Camel Development mailing list archive at Nabble.
Could it be an idea to start with the "milo" component. And push the other
two (of mine) two to 2.20.
I personally think that Milo is the most beneficial one anyway.
On Fri, Apr 7, 2017 at 9:39 AM, Claus Ibsen wrote:
> On Thu, Apr 6, 2017 at 2:34 PM, Jens Reimann wrote:
> > I personally don't
On Thu, Apr 6, 2017 at 2:34 PM, Jens Reimann wrote:
> I personally don't know this protocol. So I can't say much about it.
>
> But I guess adding a bunch of IoT related Camel components in one release
> would make sense.
>
We are closing down on Camel 2.19 and intend to cut the RC in week 16
so t
Hi Preben
Do you mind adding label = "security" etc and secret = true|false to
your @UriParam in that component, eg look at some of the other
components. We do this to provide more metadata for the options so
documentation, tooling etc knows more.
For example see
https://github.com/apache/camel/b
I upgraded and polished the component to the latest PubNub release here
https://github.com/pax95/camel/tree/pubnub
Still need to do the docs, and maybe add 1 or 2 missing features.
I'm a bit torn when it comes to adding IOT to camel. Is there bandwidth
enough to spread that wide ?
If so, and if
I personally don't know this protocol. So I can't say much about it.
But I guess adding a bunch of IoT related Camel components in one release
would make sense.
On Thu, Apr 6, 2017 at 1:52 PM, Claus Ibsen wrote:
> Hi
>
> Welcome to the Apache Camel community.
> Thanks for taking the time to exp
Hi
Welcome to the Apache Camel community.
Thanks for taking the time to explain this for us on the @dev mailing list.
If you guys can help support and maintain these IoT specific
components that would be really good.
AFAIR we only have Henryk Konsek as a Camel committer whom has been
playing and
Hi
I logged a ticket as well
https://issues.apache.org/jira/browse/CAMEL-10528
On Fri, Nov 25, 2016 at 9:48 AM, Claus Ibsen wrote:
> Hi
>
> I would like if we could add a CONTRIBUTING.adoc file in the root of
> Apache Camel source code as that is a common way of providing such
> information to u
+1
---
Luca Burgazzoli
On Fri, Nov 25, 2016 at 9:59 AM, Andrea Cosentino
wrote:
> +1.
>
> Love the idea.
> --
> Andrea Cosentino
> --
> Apache Camel PMC Member
> Apache Karaf Committer
> Apache Servicemix Committer
> Email: ancosen1...@yahoo.com
> Twitter: @osce
+1.
Love the idea.
--
Andrea Cosentino
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Friday, November 25, 2016 9:58 AM, Jean-Baptiste Onofré
wrote:
+1
Good idea.
+1
Good idea.
Regards
JB
On Nov 25, 2016, 09:49, at 09:49, Claus Ibsen wrote:
>Hi
>
>I would like if we could add a CONTRIBUTING.adoc file in the root of
>Apache Camel source code as that is a common way of providing such
>information to users, how they can contribute to the project.
>
>Proje
It takes some time to trigger a website update, so have patience.
On Sun, Dec 27, 2015 at 4:24 PM, Asaf Mesika wrote:
> I just edited my first page (http://camel.apache.org/kafka.html), saved,
> but I don't see my change. The edit was in Confluence, but it's not
> reflected in this HTML.
> What t
I just edited my first page (http://camel.apache.org/kafka.html), saved,
but I don't see my change. The edit was in Confluence, but it's not
reflected in this HTML.
What trigger it to be updated?
On Fri, Sep 25, 2015 at 10:34 AM, Claus Ibsen wrote:
> I have granted your user karma to edit the do
I have granted your user karma to edit the docs. Thanks for helping the project.
On Fri, Sep 25, 2015 at 9:23 AM, Asaf Mesika wrote:
> Ok. I have a user on the Confluence wiki page named "asafm" (Asaf Mesika).
>
> What's next?
>
>
> On Thu, Sep 24, 2015 at 5:03 PM, Claus Ibsen wrote:
>
>> Sorry
Ok. I have a user on the Confluence wiki page named "asafm" (Asaf Mesika).
What's next?
On Thu, Sep 24, 2015 at 5:03 PM, Claus Ibsen wrote:
> Sorry that was many years I did that. Click on the edit link in the
> bottom of a Camel web page, and it opens it in wiki, I assume it has
> some login
Sorry that was many years I did that. Click on the edit link in the
bottom of a Camel web page, and it opens it in wiki, I assume it has
some login / create account button somewhere.
For example:
https://cwiki.apache.org/confluence/pages/editpage.action?pageId=49116
Anyone who has recently done t
Thanks, I'm happy to help.
I searched in the wiki, but couldn't find any "Create user" button.
Can you send me a link to that?
On Mon, Sep 21, 2015 at 5:59 PM, Claus Ibsen wrote:
> Hi
>
> When your name is on this page
> http://people.apache.org/committer-index.html
>
> Then create an account o
Hi
When your name is on this page
http://people.apache.org/committer-index.html
Then create an account on the wiki and let us know your username and
post here again. Then we can grant karma.
Thanks for helping with the project.
On Mon, Sep 21, 2015 at 4:57 PM, Asaf Mesika wrote:
> Hi,
>
> I've
Ok, karma granted!
Looking forward to your first contribution.
Best,
Christian
-
Software Integration Specialist
Apache Member
V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
Apache Incubator PMC Member
https://www.linkedin.com/pub/christian-mueller/11/551/
Oh, silly me.
I am now "alvrod" in Confluence too.
Thanks
Alvaro.
On Thu, Feb 6, 2014 at 5:13 PM, Christian Müller
wrote:
> Both user names are not known in Confluence (Confluence is not JIRA ;-) ).
> You have to create an account in Confluence too, if you would like to edit
> our WIKI.
>
> Best,
Both user names are not known in Confluence (Confluence is not JIRA ;-) ).
You have to create an account in Confluence too, if you would like to edit
our WIKI.
Best,
Christian
-
Software Integration Specialist
Apache Member
V.P. Apache Camel | Apache Camel PMC Member | Apache Ca
Correction: Thanks to dkulp I've regained control of "alvrod" so I can
be myself :-)
Regards
Álvaro.
On Wed, Feb 5, 2014 at 10:32 PM, Alvaro Rodriguez
wrote:
> Hello, thanks everyone for the warm welcome.
> I happen to be "calefox" in JIRA because alvrod was already taken.
> Unless someone reserv
Hello, thanks everyone for the warm welcome.
I happen to be "calefox" in JIRA because alvrod was already taken.
Unless someone reserved it for me. :-)
Regards
Alvaro
On Wed, Feb 5, 2014 at 6:30 PM, Christian Müller
wrote:
> Welcome Alvaro!
>
> Looking forward to your first contribution. If you w
Welcome Alvaro!
Looking forward to your first contribution. If you want to get your hands
on the Camel code, have a look at the easy to resolve issues [1].
If you tell us your Confluence user name, we will grant the karma to edit
the WIKI.
[1] https://issues.apache.org/jira/browse/CAMEL-7156?filt
Hi
Welcome to the community and looking foward to any help of yours.
I assume you have read this page and the links it refer to about edit
the website and providing code patches etc.
http://camel.apache.org/contributing
On Wed, Feb 5, 2014 at 1:24 AM, Alvaro Rodriguez
wrote:
> Hello,
> I sent a
Woohoo! the more the merrier! look forward to your contributions...
pick some JIRAs (or create some) and send some pull requests/patches.
On Tue, Feb 4, 2014 at 5:24 PM, Alvaro Rodriguez
wrote:
> Hello,
> I sent an ICLA to Apache, received confirmation from jcarman, and I
> can see my name in the
Hallo Nerses!
Done. After a new login you should be able to edit the Camel WIKI. We are
looking for your contributions.
Best,
Christian Müller
-
Software Integration Specialist
Apache Camel committer: https://camel.apache.org/team
V.P. Apache Camel: https://www.apache.org/found
reposting because I forgot to subscribe to mailing list.
Hi Christian,
Can you also grant me access as well. I have already signed the icla. My
username is nerses_am.
Thanks :)
--
View this message in context:
http://camel.465427.n5.nabble.com/Contributing-tp5733544p5733641.html
Sent from
Hello Frank!
Karma is granted. After logout/login, you should be able to update the WIKI.
Thanks in advance for your contribution!
Best,
Christian Müller
-
Software Integration Specialist
Apache Camel committer: https://camel.apache.org/team
V.P. Apache Camel: https://www.apac
Hi Christian,
my username is frank_e.
Thanks in advance,
Frank
--
View this message in context:
http://camel.465427.n5.nabble.com/Contributing-tp5733544p5733565.html
Sent from the Camel Development mailing list archive at Nabble.com.
Hi Frank!
You have to create a Confluence Account, did you?
What's your user name? I will grant the karma to you, after I know to which
account.
Best,
Christian
Sent from a mobile device
Am 31.05.2013 10:37 schrieb "Frank Ertl" :
> Hi,
>
> I send a CLA which has been filed (see Unlisted CLAs
>
> Hiram:
> How about if we can get at least 3 committers to agree to help maintain the
> component then it should get accepted.
Maybe instead we could establish a kind of "Scala team" among the
Camel committers? These volunteers could declare that they would
handle Scala-related escalations in th
Hiram, that would be greet indeed.
Fwiw, my comment didn't refer to scala per se, but any component that we
don't have the ability to support ourselves. With java at least I
believe there are quite a few of us who could jump in and fix things,
with scala it's less the case. And socially, what
How about if we can get at least 3 committers to agree to help maintain the
component then it should get accepted. I think we should make efforts to
grow the camel community past just Java components if possible.
On Thu, Feb 7, 2013 at 7:51 PM, Willem jiang wrote:
> Putting the components int
> Hadrian:
> We know however from past experience that the community's ability to
> support scala based code was not at par with the rest of the code base.
This is changing. Scala is getting more popular among Java people. And
this trend is visible almost within our community. Year ago I wouldn't
Oh, I don't agree with that Scomp component is written in Scala we should find
other place to host it.
As an open source project we should alway encourage people to contribute, and
we can always find someone who willing to maintain the code, if we have lots of
users to use component.
--
Wi
Willem, I know all that. I understand it makes sense from the
contributor's point of view. It saves contributors time, effort and
costs. It ensures the their component will continue to work with future
versions of camel. That benefits the community too. Personally I applaud
that attitude.
How
Putting the components into Apache Camel umbral could save some work of
contributor when we release the Camel. We add the camel-extra due to the
license issue only. It is hard to say no for the contributing to Apache Camel
if the component has the ASF license already. That is way we have more th
I also believe Apache Camel the way it is organized now is not the place
for the scomp component. We are not debating the quality of the scomp
component. We know however from past experience that the community's
ability to support scala based code was not at par with the rest of the
code base.
Please find my comments inline.
Best,
Christian
On Thu, Feb 7, 2013 at 9:20 PM, Henryk Konsek wrote:
> > Because Camel and Camel-Extra are Java based projects, I don't think we
> > should integrate this component (even if it's a cool component for Scala
> > guys).
>
> I'm afraid I must disagree
> So once we have Scomp updated we are good to go.
First of all we need to figure out where the component should go, as
apparently there is some disagreement related to the proper place for
the Scala-related components.
BTW Camel Stomp definition made my day :P .
--
Henryk Konsek
http://henryk-
I have to say I kinda agree with this.
We could mark a component as possibly "less quickly patched",
but nixing contributions on a component level seems kinda wrong to me...
On Feb 7, 2013, at 1:20 PM, Henryk Konsek wrote:
>> Because Camel and Camel-Extra are Java based projects, I don't think
> Because Camel and Camel-Extra are Java based projects, I don't think we
> should integrate this component (even if it's a cool component for Scala
> guys).
I'm afraid I must disagree :) .
We support Scala as the 1st class citizen DSL language for Camel and I
don't see any reason why we should e
se.
>>>
>>> Great :) Just keep me in the loop.
>>>
>>> --
>>> Henryk Konsek
>>> http://henryk-konsek.blogspot.com
>>>
>>>
>>> If you reply to this email, your message will be added to the discussion
>> below:
>
nent-tp5726153p5726700.html
> > To unsubscribe from Contributing Apollo Component, click here.
> > NAML
>
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Re-Contributing-Scomp-Component-was-Contributing-Stomp-Component-tp5726868.html
> Sent from the Camel Development mailing list archive at Nabble.com.
--
> below:
> http://camel.465427.n5.nabble.com/Contributing-Apollo-Component-tp5726153p5726700.html
> To unsubscribe from Contributing Apollo Component, click here.
> NAML
--
View this message in context:
http://camel.465427.n5.nabble.com/Re-Contributing-Scomp-Component-was-Contri
> That is a good approach.
> ..
> I am waiting for a response.
Great :) Just keep me in the loop.
--
Henryk Konsek
http://henryk-konsek.blogspot.com
Hi Henryk
That is a good approach. I have already contacted the Scomp developer and I am
waiting for a response. Should that not be forthcoming I shall follow your
suggestion.
Regards
Ian
On 31 Jan 2013, at 9:55 AM, "hekonsek [via Camel]"
wrote:
> Hi Ian,
>
> > The original project has not
Hi Ian,
> The original project has not been maintained for more than a year.
> ...
> I have tried to contact Dejan to get his input in this regard.
> ...
> I am happy to collaborate with the original author but it might be simpler
> to work of the branch
In my opinion core Camel components shou
Hi
I shall do the refactoring over the next few days. As far as Scomp goes: The
original project has not been maintained for more than a year. It uses Scala
2.9.0. As a result a lot of changes were made. I am happy to collaborate with
the original author but it might be simpler to work of the br
> We would appreciate STOMP component written in Java.
Sorry, my mistake. I understood that you created Scala component for
STOMP Java library. However since Scomp is a pure Scala library I
think that Scomp component written in Scala can be safely committed to
the ASF Camel (after review process o
On Tue, Jan 29, 2013 at 1:57 PM, Ian de Beer wrote:
> Hi
> I have put the Camel-Stomp component onto Github:
> https://github.com/zenaptix/camel-stomp
> I have tested it against Apollo 1.5 and ActiveMQ 5.7.0.
> Regards
> Ian
>
Ian nice work. We can add a link to your component from the Camel
use
On Tue, Jan 29, 2013 at 8:21 PM, Henryk Konsek wrote:
Claus had some good arguments there not to use Scala.
Nevertheless, I think your code should be published at camel-extra or
github!
>
> Actually Camel Extra is not a right place to put there components
> written in Scala. I'
>>> Claus had some good arguments there not to use Scala.
>>>
>>> Nevertheless, I think your code should be published at camel-extra or
>>> github!
Actually Camel Extra is not a right place to put there components
written in Scala. I'm afraid this component need to be rewritten to
Java in order to
Hi
I have put the Camel-Stomp component onto Github:
https://github.com/zenaptix/camel-stomp
I have tested it against Apollo 1.5 and ActiveMQ 5.7.0.
Regards
Ian
On 25 Jan 2013, at 11:54 AM, iandebeer wrote:
> Hi Kai and Willem
> I have it in my private git repo, but I shall extricate the releva
Hi Kai and Willem
I have it in my private git repo, but I shall extricate the relevant packages
from my project and put it on github over the weekend.
An additional issue might be that I used SBT (0.12.2) whilst your build
environment is Maven. Not too much effort to change that though.
Regards
I
Hi Claus
Yes it is generic Stomp. I did all the testing against Apollo though - will run
the tests against ActiveMQ later today and let you know.
Regards
Ian
On 25 Jan 2013, at 9:14 AM, "Claus Ibsen-2 [via Camel]"
wrote:
> On Thu, Jan 24, 2013 at 1:20 PM, iandebeer <[hidden email]> wrote:
> >
Ian, just FYI: We had the discussion about Scala components some months
ago, when I thought about creating a Neo4j Scala component:
http://camel.465427.n5.nabble.com/Create-a-new-Camel-component-via-Scala-Component-Archetype-td5708543.html
Claus had some good arguments there not to use Scala.
Nev
On Thu, Jan 24, 2013 at 1:20 PM, iandebeer wrote:
> Hi
> I have developed a Stomp Component for use with Apollo. It supports in, out
> and in-out exchange patterns.
I assume its a generic stomp component, so you can use it with any
stomp compliant brokers,
eg also ActiveMQ. eg its not only for Ap
Hi Ian,
I think is not a big deal to host the component in Apollo or Camel.
But I'd like to help to review the code, did you have chance to push the code
into github?
If so, I could spend some time to have a look at the code :)
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Hi Christian
Unfortunately, I will not be able to find the time to rewrite it Java.
A large portion of Apollo is written in Scala. (as is HawtDispatch which is
also used in the project). Maybe it would be an option to provide the component
from the Apollo side, similar to the ActiveMQ component.
I know, we have a camel-scala component to integrate Scala. This make sense
to me.
I don't like the idea to add a comonent which is written in Scala to
integrate with other protocols like Stomp. Is it possible to (re-) write it
in Java?
Only a few committer are familiar with Scala and are able to m
It sounds cool.
Please take some time to go through the contributing page[1], you can fill a
JIRA and attach your patch into it.
[1]http://camel.apache.org/contributing.html
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat
Done. Thanks,
Hadrian
On 05/02/2012 05:03 AM, jkorab wrote:
Done. That should all match up now. Thanks,
Jakub
hadrian wrote
I can confirm that. However, the confluence (wiki) account address
points to another address. That's the one you need to update.
If you can log into the confluence wi
Done. That should all match up now. Thanks,
Jakub
hadrian wrote
>
> I can confirm that. However, the confluence (wiki) account address
> points to another address. That's the one you need to update.
>
> If you can log into the confluence wiki, click on your name (menu) at
> the top and selec
I can confirm that. However, the confluence (wiki) account address
points to another address. That's the one you need to update.
If you can log into the confluence wiki, click on your name (menu) at
the top and select Profile. On the right side, next to the Personal
widget there is an Edit lin
Never mind, I worked it out. The jkorab Jira account now points to my new
address. Thanks,
Jakub
jkorab wrote
>
> Hi Hadrian,
>
> I have a Jira account under jkorab but with a different (much older) email
> address. Is there any way that I can change that address?
>
> Jakub
>
>
> hadrian wr
Hi Hadrian,
I have a Jira account under jkorab but with a different (much older) email
address. Is there any way that I can change that address?
Jakub
hadrian wrote
>
> Jakub, create an account in jira, use the same email address as the one
> in the icla and let us know. We'll grant you the n
Jakub, create an account in jira, use the same email address as the one
in the icla and let us know. We'll grant you the necessary karma.
Thanks the offer,
Hadrian
On 05/01/2012 11:50 AM, jkorab wrote:
Hi,
I'd like an account in order to contribute to the Camel wiki. My ICLA has
been accepted
Hi,
Thanks for granting the editing rights! I'll start looking at some of the
component docs next week, though it looks like Claus has already made some
big improvements there in recent days.
Cheers,
Fintan
--
View this message in context:
http://www.nabble.com/Contributing-to-Camel-Component-
Hey, that was my responsibility! :)
I have verified the presence of the cla.
Thanks for helping Jon.
And many thanks to you Fintan for the contribution.
Hadrian
On Jun 25, 2009, at 11:40 AM, Jon Anstey wrote:
We'd appreciate any help you can give Fintan! Since you've already
signed a
CLA wit
Hi
Yeah cool you would like to help Fintan.
Just ask questions when something is unclear or if you want to have us help
with some review. Or if some feature/option etc. is missing to be
documented.
Camel have exceptionally many minor features and options here and there and
some of them are not to
We'd appreciate any help you can give Fintan! Since you've already signed a
CLA with Apache, I gave your fbolton account wiki privileges.
On Thu, Jun 25, 2009 at 11:23 AM, Fintan Bolton wrote:
>
> Hi,
>
> I'd like to contribute documentation for the Camel components and so, I
> guess I need an ac
79 matches
Mail list logo
