+1 to avoid ip clearance for me.
Il mar 3 dic 2019, 20:49 Jon Anstey ha scritto:
> Yeah, IMO we don't need to go through the incubator grant/ip-clearance. All
> 5 contributors are from Red Hat so we don't need to track down anybody else
> to give a +1. Would it help if all contributors chimed in
Yeah, IMO we don't need to go through the incubator grant/ip-clearance. All
5 contributors are from Red Hat so we don't need to track down anybody else
to give a +1. Would it help if all contributors chimed in here with a +1?
On Tue, Dec 3, 2019 at 4:06 PM Andrea Cosentino wrote:
> Frankly I do
Frankly I don't think an IP clearance is needed, I don't know what the
other contributors think, but it's a PoC actually
Il mar 3 dic 2019, 20:04 Daniel Kulp ha scritto:
>
> >
> > +1, yeah lets first create a JIRA ticket in CAMEL and then lets work
> > with INFRA to get a new sub project for Apa
Hello,
excited about having the Camel Kafka Connector as a sub-project of Camel.
Looking forward contributing to it!
I'd like to step in and offer help. I've already been contributing to this
project to some extent. I'm more than happy to extend it to anything that
can help the project to get sta
>
> +1, yeah lets first create a JIRA ticket in CAMEL and then lets work
> with INFRA to get a new sub project for Apache Camel.
> So we have a git repo ready that is mirrored to github, so we can work
> on this just like camel-k, camel-quarkus etc.
>
> Whom can help with this?
The INFRA part o
On Tue, Dec 3, 2019 at 5:44 PM Omar Al-Safi wrote:
>
> Hi Claus,
>
> I can help on this one with INFRA to get this project to asf. Does it have
> to be a PMC to do this?
>
No I would imagine so. Anyone can help. So thanks for stepping up.
There are things besides the initial source code dump, is
created the initial JIRA https://issues.apache.org/jira/browse/CAMEL-14249
On Tue, Dec 3, 2019 at 5:43 PM Omar Al-Safi wrote:
> Hi Claus,
>
> I can help on this one with INFRA to get this project to asf. Does it have
> to be a PMC to do this?
>
>
>
> On Tue, Dec 3, 2019 at 5:38 PM Claus Ibsen w
Hi Claus,
I can help on this one with INFRA to get this project to asf. Does it have
to be a PMC to do this?
On Tue, Dec 3, 2019 at 5:38 PM Claus Ibsen wrote:
> Hi
>
> +1, yeah lets first create a JIRA ticket in CAMEL and then lets work
> with INFRA to get a new sub project for Apache Camel.
Hi
+1, yeah lets first create a JIRA ticket in CAMEL and then lets work
with INFRA to get a new sub project for Apache Camel.
So we have a git repo ready that is mirrored to github, so we can work
on this just like camel-k, camel-quarkus etc.
Whom can help with this?
On Thu, Nov 28, 2019 at 11:1
davsclaus merged pull request #119: fix(typo): camel-bean
URL: https://github.com/apache/camel-website/pull/119
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and
davsclaus commented on issue #119: fix(typo): camel-bean
URL: https://github.com/apache/camel-website/pull/119#issuecomment-561248360
Thanks
This is an automated message from the Apache Git Service.
To respond to the message,
benoitf opened a new pull request #119: fix(typo): camel-bean
URL: https://github.com/apache/camel-website/pull/119
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub
Yes. I know and my own components use this. But it seems spring or flowable
needs this class there.
-Ursprüngliche Nachricht-
Von: Andrea Cosentino
Gesendet: Dienstag, 3. Dezember 2019 13:01
An: us...@camel.apache.org
Cc: dev
Betreff: Re: DefaultComponent
In Camel 3 the DefaultCompo
Hi,
I got this error. What is missing?
java.lang.NoClassDefFoundError: org/apache/camel/impl/DefaultComponent
Stacktrace:
java.lang.NoClassDefFoundError: org/apache/camel/impl/DefaultComponent
at java.base/java.lang.ClassLoader.defineClass1(Native Method) ~[na:na]
at java.base
In Camel 3 the DefaultComponent is located at
org.apache.camel.support
It is reported in the migration guide
https://camel.apache.org/manual/latest/camel-3-migration-guide.html#_migrating_custom_components
Il giorno mar 3 dic 2019 alle ore 12:59 ha
scritto:
> Hi,
>
> I got this error. What is
zregvart merged pull request #118: fix: allow the logo to resize with font sizes
URL: https://github.com/apache/camel-website/pull/118
This is an automated message from the Apache Git Service.
To respond to the message, pleas
zregvart opened a new pull request #118: fix: allow the logo to resize with
font sizes
URL: https://github.com/apache/camel-website/pull/118
By using the `rem` unit we're able to scale the logo with respect to the
any changes to the font size that the user might customize.
For instanc
On Tue, Dec 3, 2019 at 10:23 AM Andrea Cosentino wrote:
>
> I'm available to cut the release once it is ready.
>
> +1.
>
Great
> Do we plan to add more extensions before this release?
>
I dont think so. There is a native testing with tagsoup extension that
are running, and if its good, then we
I'm available to cut the release once it is ready.
+1.
Do we plan to add more extensions before this release?
Il giorno mar 3 dic 2019 alle ore 10:22 Claus Ibsen
ha scritto:
> Hi
>
> I think we should get a new camel-quarkus release out that is upgraded
> to Camel 3 GA and the new quarkus 1.0.
Hi
I think we should get a new camel-quarkus release out that is upgraded
to Camel 3 GA and the new quarkus 1.0.1 release - so they both are GA.
--
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
oscerd merged pull request #114: Added missing xsds for camel-spring
URL: https://github.com/apache/camel-website/pull/114
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
oscerd merged pull request #113: Added missing camel-blueprint xsd after 3.0.0
release
URL: https://github.com/apache/camel-website/pull/113
This is an automated message from the Apache Git Service.
To respond to the message
22 matches
Mail list logo
