Hi folks,
I am writing to your project list as there have been submissions from your
project to the IoT track in the past, we have integration modules for your
project in PLC4X, you are listed as "IoT" category project, or I just thought
your project would be a good match for an IoT related
Hi all,
as I have been dealing with the email traffic generated by especially the
“discussions” integration, please also have a look at this:
https://community.apache.org/contributors/mailing-lists.html#configuring-the-subject-lines-of-the-emails-being-sent
We will be changing the defaults to
TL;DR: We’re updating how auto-generated email from Github will be
threaded on your mailing lists. If you want to keep the old defaults,
details are below.
We’re pleased to let you know that we’re tweaking the way that auto-
generated email from Github will appear on your mailing lists. This
will
Hi all,
being the Track Chair for the IoT Track this year, I was just going through the
proposals that have been submitted so-far.
The reason is, that I wanted to get an idea of the story we want to tell with
the track.
Unfortunately, there's close to nothing available yet.
I would strongly
Hi all,
So, the vote in the PLC4X Project has passed in favor of moving the PLC4X Camel
component here … so what happens now?
Chris
From: Christofer Dutz
Date: Wednesday, 19. October 2022 at 07:42
To: dev@camel.apache.org
Subject: Re: [DISCUSS] Moving the Apache PLC4X Camel components
kit.
--
Andrea Cosentino
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Wednesday, October 26, 2022 at 11:04:40 AM GMT+2, Christofer Dutz
wrote:
Hi all,
So, the v
and
also make it build like the other components, so it can generate the
metadata and what else we do.
Also the package name should be org.apache.camel.component.
On Wed, Oct 26, 2022 at 3:41 PM Andrea Cosentino wrote:
> Yeah.
>
> Il mer 26 ott 2022, 15:39 Christofer Dutz ha
project?
I meant to say someone from the PLC4x PMC.
But I can have a look too. I'll keep you posted.
Il giorno mer 26 ott 2022 alle ore 14:17 Christofer Dutz <
christofer.d...@c-ware.de> ha scritto:
> Sounds reasonable,
>
> And if you need any help with it, I’m happy to assist.
Hi all,
So, the Vote is on its way and looking good so far.
I’ll keep you posted.
Chris
From: Christofer Dutz
Date: Thursday, 13. October 2022 at 20:29
To: dev@camel.apache.org
Subject: Re: [DISCUSS] Moving the Apache PLC4X Camel components into the Apache
Camel project?
Yeah,
It’s a pretty
;
> We might help with the migration for sure.
>
> Thanks for reaching out to us.
>
> Il giorno mer 12 ott 2022 alle ore 16:06 Christofer Dutz <
> christofer.d...@c-ware.de> ha scritto:
>
> > Hi all,
> >
> > after a few chats at last week’s ApacheCon, I
Hi all,
after a few chats at last week’s ApacheCon, I would like to start a discussion
on moving the Apache PLC4X Camel components into the Apache Camel project.
With these components, we are able to read data from industrial programmable
logic controllers or other hardware and stream that
Hi all,
I’m currently playing around with using Nats in combination with Camel and was
trying to configure it to communicate with one of our companies Nats servers.
Unfortunately, it seems that I can’t do this as the Nats component doesn’t seem
to support authentication.
Is there an
Source/Sink don't seem to support authentication
Hi Christopher,
The camel documentation has this topic:
https://camel.apache.org/components/3.18.x/nats-component.html#_configuring_username_and_password_or_token
I've never tested though.
Alex
On Wed, Oct 12, 2022 at 4:16 PM Christofer Dutz
; Thanks for reaching out to us.
> >
> > Il giorno mer 12 ott 2022 alle ore 16:06 Christofer Dutz <
> > christofer.d...@c-ware.de> ha scritto:
> >
> > > Hi all,
> > >
> > > after a few chats at last week’s ApacheCon, I would like to start
This was exactly what I noticed when reviewing the RC for the 3.20.0 release.
I think I even left some comments on how to fix the problems.
In this case I think the integration-tests failed because the pom in the test
referenced artifacts that weren’t built yet.
A simple fix should be to simply
Hi all,
Would be cool if anyone could at least acknowledge some of the things I
reported in my vote on 4.20.0.
Or are such thorough release checks not expected or desired?
It’s usually a lot of work to do such checks … so if they are not wanted, I’ll
just stop doing them ;-)
Chris
From:
aS service.
In that case, camel leverages Kafka to persist received messages. I
don't think the in-memory queue could address the problem.
@ Chris, Can you share more information about your use case?
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Wed, Dec 7, 2022 at 11:16 PM Christofer D
+1 (non-binding)
Chris
[OK] Download all staged artifacts under the url specified in the release vote
email.
[OK] Verify the signature is correct.
A link to the Apache Camel KEYS file in the VOTE email would be great
[OK] Check if the signature references an Apache email address.
[MINOR] Verify
Hi,
we’re currently discussing potentially using Apache Camel for building a
product based on Apache PLC4X, Apache IoTDB to build a Historian solution for
industrial use-cases.
We’re planning on making this less a framework, but more a product, based on
open-source frameworks and as soon as we
22 at 8:59 PM Christofer Dutz
wrote:
> Hi,
>
> we’re currently discussing potentially using Apache Camel for building a
> product based on Apache PLC4X, Apache IoTDB to build a Historian solution
> for industrial use-cases.
> We’re planning on making this less a framework, but mor
Thanks for this … instantly tried it out for PLC4X :-)
You might want to add an “false” if you want it only
executed in the reactor root for the entire project.
If you run it for every module, it does make the build take a LOT longer ;-)
Chris
From: Andrea Cosentino
Date: Thursday, 19.
I guess the subject says it all ;-)
Please be sure to submit your proposals is available at:
https://communityovercode.org/call-for-presentations/
And open till July 13th.
Please do me a huge favor: If you plan on submitting something, don’t do it on
the last minute.
Not only do you make it
umber of builds on git-websites
> nodes concurrently.
>
> Il giorno lun 19 feb 2024 alle ore 13:30 Christofer Dutz <
> christofer.d...@c-ware.de> ha scritto:
>
> > Hi,
> >
> > as the PLC4X build also uses that, perhas what we did would be also an
> >
ration. We don't have other way of
publishing the website except using that mechanism.
Il lun 19 feb 2024, 13:13 Christofer Dutz ha
scritto:
> Hi all,
>
> I’m currently trying to finish up some stuff for the upcoming PLC4X
> release. However am having problems because every tim
Hi all,
I’m currently trying to finish up some stuff for the upcoming PLC4X release.
However am having problems because every time I want to update our website, I
have to wait a long, long time, because all 3 runners in the “git-websites”
class (websites1, websites2 and websites3) are blocked
Hi folks,
I was contacted by some of my friends in the IoT Space at the Eclipse
Foundation.
They are planning this year's EclipseCon to work closer together with the other
foundations in this space and proposed an Apache IoT Track in paralel to the
EclipseCon. This will be happening in Mainz
enkins.
>
> Thoughts?
>
Yes that is a good idea
> zoran
>
> On Tue, Feb 20, 2024 at 11:13 AM Christofer Dutz
> wrote:
> >
> > Hi all,
> >
> > Guess our release is out and the website was updated before that … so
> guess I’m fine.
> > And if you
Hi all,
So, in the last few months we have worked really hard on exposing a lot of
information about PLC4X drivers and connections to tools using it.
With these changes you can now provide a lot of assistance for configuring PLC
connections with PLC4X.
I remember that in Karavan you had to
28 matches
Mail list logo
