Hello Camel(K) Riders,
Happy new year!
We've just upgrade Golang to version 1.18 on main branch [1], so you may have
to upgrade your local tooling for development.
Cheers,
Antonin
[1] https://github.com/apache/camel-k/pull/3963
+1 (binding)
Thanks Andrea!
> On 21 Apr 2022, at 13:23, Andrea Cosentino wrote:
>
> Hello all:
>
> This is a combined vote to release Apache Camel K 1.9.0, Camel K Runtime
> 1.13.0 and Kamelets 0.8.0.
>
> This is a patch release based on Camel-Quarkus 2.8.0 and Camel 3.16.0 and
> contains sev
+1 (binding)
Thanks a lot Andrea for the release!
> On 3 Mar 2022, at 14:27, Andrea Cosentino wrote:
>
> Hello all,
>
> This is a vote to release Apache Camel K 1.8.2.
>
> This is a patch release containing an important fix:
> https://github.com/apache/camel-k/pull/3056
>
> This is a critica
+1 (binding)
Thanks a lot for the release Andrea!
Antonin
> On 21 Feb 2022, at 10:45, Andrea Cosentino wrote:
>
> Hello all:
>
> This is a combined vote to release Apache Camel K 1.8.1, Camel K Runtime
> 1.12.0 and Kamelets 0.7.1.
>
> This is a patch release based on Camel-Quarkus 2.7.0 and
+1 (non-binding)
Thanks a lot Andrea!
> On 19 Jan 2022, at 18:17, Andrea Cosentino wrote:
>
> Hello all:
>
> This is a combined vote to release Apache Camel K 1.8.0, Camel K Runtime
> 1.11.0 and Kamelets 0.7.0.
>
> This is a major release based on Camel-Quarkus 2.6.0 and Camel 3.14.0 and
> co
Hi David,
Thanks a lot for your initiative. I hesitated to comment, both because I'm
definitely foreign to the doc building process, and also as you did not mention
Camel K. However, this, if I understand it correctly would help solving the
following issue:
https://github.com/apache/camel-k/is
+1 (non binding)
Thanks a lot Nicola!
> On 10 Nov 2021, at 13:27, Nicola Ferraro wrote:
>
> Hello all:
>
> This is a combined vote to release Apache Camel K 1.7.0, Camel K Runtime
> 1.10.0 and Kamelets 0.5.0.
>
> This is a major release based on Camel-Quarkus 2.4.0 and Camel 3.12.0 and
> cont
Naively / intuitively, I would assume 'latest' points to the latest released
version, while 'next' points to what is going to be the next version released.
If I understand it correctly, 'latest' is redirected to 'next'.
That being said, I appreciate it may be more complex to implement, if that
+1 (non-binding)
Thanks Nicola!
> On 23 Oct 2021, at 20:27, Nicola Ferraro wrote:
>
> Hello all:
>
> This is a combined vote to release Apache Camel K 1.6.1 and Camel K Runtime
> 1.9.1.
>
> This is a minor release upgrading the runtime to Camel-Quarkus
> 2.3.0 and Camel 3.11.2 and contains so
Sounds good. Thanks Nicola.
> On 13 Oct 2021, at 10:19, Nicola Ferraro wrote:
>
> Hello,
> I was thinking of scheduling two new releases of Camel K this month.
>
> 1.6.1: upgrading the runtime to Camel-Quarkus 2.3.0 and Camel 3.11.2, plus
> fixes in the operator
> 1.7.0: targeting Camel 3.12 wh
Hi Luca, all,
+1 for Binding.
Users in the Kubernetes ecosystem may already be familiar with the term,
as it seems it's the choice made by projects like Knative and Service Binding,
to convey the general concept of "integrating" in their respective domain.
I find projecting that concept into the
Hi,
Thanks Nicola.
I've found an issue with the Prometheus trait, that registers a duplicated
container port if the Integration already exposes one, e.g. with HTTP endpoints.
It's fixed with https://github.com/apache/camel-k/pull/2216
Thanks,
Antonin
On 14 Apr 2021, at 00:01, Nicola Ferraro
Hi Alex,
That was supposed to get fixed by https://github.com/apache/camel-k/pull/2141.
Not sure why it's not working for the release binary.
On 14 Apr 2021, at 11:37, Alexandre Gallice
mailto:aldettin...@gmail.com>> wrote:
Hi guys,
Sorry, I was not able to test the kamel executable as it lo
+1 (non-binding)
On 30 Oct 2019, at 15:04, Andrea Cosentino
mailto:ancosen1...@yahoo.com.INVALID>> wrote:
Hello all:
This is a vote to release Apache Camel Quarkus 0.3.1
This release contains the new camel-pdf extension and has been updated to
Quarkus 0.27.0 which contains important fixes.
S
+1
> On 7 Oct 2019, at 07:33, Tadayoshi Sato wrote:
>
> Hi folks,
>
> I've just realised that this dev mailing list is receiving a huge amount of
> notifications from camel-k & camel-quarkus github repositories. I am a bit
> afraid that this overwhelms the actually discussions on camel developm
oran
>
> On Tue, Aug 20, 2019 at 10:04 AM Antonin Stefanutti
> wrote:
>>
>> Hi Zoran,
>>
>> I haven't found any blocking issue. There are only few broken links and
>> images and small layout discrepancies, that can be fixed later.
>>
>
Hi Zoran,
I haven't found any blocking issue. There are only few broken links and images
and small layout discrepancies, that can be fixed later.
I’m particularly impressed by this piece of work. The new design is both very
functional and looks gorgeous.
Congratulations to everyone involved!
Thanks a lot! Really great work.
I like 1 a lot.
> On 23 Apr 2019, at 17:15, Jason Brock wrote:
>
> Hello everyone!
>
> Here is a first round of design concepts to help refresh the look and feel
> of the Apache Camel website. Please let me know if you require a particular
> file format and I w
+1 (non binding)
> On 27 Feb 2019, at 09:30, Andrea Cosentino
> wrote:
>
> Hello all:
>
> This is a vote to release Apache Camel-K runtime 0.3.0
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1122
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=
+1
> On 26 Feb 2019, at 10:31, Andrea Cosentino
> wrote:
>
> Hello all:
>
> This is a vote to release Apache Camel-K runtime 0.3.0
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1121/
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=camel-k-runti
+1
> On 21 Feb 2019, at 09:32, Andrea Cosentino
> wrote:
>
> Hello all,
>
> We created a new repo https://github.com/apache/camel-k-runtime
>
> The aim of this repo is containing the runtime bits for Camel-k, so we may be
> able to release it as a separated entity and use it in the camel-k r
+1
> On 19 Feb 2019, at 13:13, Andrea Cosentino
> wrote:
>
> Hello all:
>
> This is a vote to release Apache Camel-K 0.2.1 (runtime bits)
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1120/
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=camel-
ant to
> make this UI available. Something like `kamel ui` to spin a web
> server perhaps? Maybe with the UI already set up to talk with the
> right backend?
I love the idea of having it deployed with `kamel ui`!
> Riccardo
>
> On Tue, Oct 9, 2018, at 12:41, Antonin Stefanutti wrote:
Hi Riccardo,
This looks very promising! I think having a Web UI for Camel-K would be very
valuable.
Here are my quick feedback:
- It’d be great to have the UI self-hosted. For it to work while avoiding to
configure CORS on the API server, it is possible to proxy the communication to
the API se
Hi Nicola,
I love the idea.
I just wonder whether YAML/JSON is an expressive enough format in the long
term. But as you’ve mentioned, starting simple would enable experimenting some
very interesting / promising optimisations. So it seems worth taking that path,
instead of trying to embed a com
Hi,
The dependency on DeltaSpike from Camel CDI has been removed starting Camel
2.17.0. So I would not expect it to be a problem with Camel / PAX CDI.
Antonin
> On 12 Apr 2017, at 20:59, Guillaume Nodet wrote:
>
> 2017-04-12 20:52 GMT+02:00 Ranx :
>
>> I'm not quite sure I follow the comment
> On 12 Apr 2017, at 15:22, Claus Ibsen wrote:
>
> Hi
>
> Just a heads up that we plan to cut the RC for Camel 2.19 next week.
>
> So we are closing down on the last tickets, bugs, features etc to get
> the code base in shape.
>
> The JIRA has 9 tickets
> https://issues.apache.org/jira/issues
> On 16 Jan 2017, at 10:28, Claus Ibsen wrote:
>
> 8)
> That CDI JEE transaction PR on github.
> Ideally we would have had a transaction API in camel-core and then one
> impl for camel-spring, and then another for camel-cdi-jee. But that
> may require too much work.
I may be able to work on it
That should be fine with that version of Weld. Though I realise for it to work
the qualifier need to be annotated with @Repeatable, which is missing. I’ve
just created https://issues.apache.org/jira/browse/CAMEL-10464. I’ll work on it
ASAP. In the meantime, you should be able to achieve the same
Hi,
What CDI runtime are you using? It may be that some older runtimes do not
support this. It has been discussed and is tracked in
https://issues.jboss.org/browse/CDI-471 though some Weld versions already
support it.
Antonin
> On 10 Nov 2016, at 09:59, a746076drdrb wrote:
>
> Hi Antonin,
>
Hi,
Would you think that makes sense to remove the 'throws Exception' from a number
of Camel API signatures as well as using unchecked exceptions instead?
While this may be a matter of opinion still debated, there are a couple
resources that gives some guidelines on the topic and that may help
that but that’s exactly what I had in mind ;-)
That being said, I don’t have the historic being this so there may be a good
reason.
> ---
> Luca Burgazzoli
>
>
> On Fri, Oct 14, 2016 at 2:25 PM, Antonin Stefanutti
> wrote:
>> Hi Luca,
>>
>> Make sense to
Hi Luca,
Make sense to me. As I refactored Camel CDI with Java 8 in Camel 2.18.0, I
found using Optional as return type of internal util methods quite useful in
term of client conciseness / readability compared to null handling.
I’m wondering whether that should be added to StringHelper instead
Hi,
There are multiple ways to achieve sharing routes across contexts in CDI. Maybe
the most simple example could be the following one:
@ContextName("foo")
@ContextName("bar")
class MySharedRouteBuilder extends RouteBuilder {
}
@ApplicationScoped
@ContextName("foo")
class FooCamelContext exten
+1
Tested CDI integration (PAX CDI / Karaf, Wildfly, Java SE) and everything’s OK.
Antonin
> On 05 Oct 2016, at 16:54, Gregor Zurowski wrote:
>
> Hi Everyone:
>
> This is a vote to release Apache Camel 2.18.0, the first release that
> requires Java 8, comes with a much-improved Spring Boot su
Hi Luca,
I’ve just encountered an issue when using the date function that gets
substituted by Log4j 2 and causes the exception below to be thrown.
It happens in a number of situations:
- when a route definition containing the date function get logged (in DEBUG
level)
- when an advice is being a
Hi,
+1 (Tested on Camel CDI and Netty HTTP examples).
Antonin
> On 06 May 2016, at 19:12, Gregor Zurowski wrote:
>
> Can we get any more votes for this release?
>
> Thanks,
> Gregor
>
>
> On Mon, May 2, 2016 at 9:24 AM, Gregor Zurowski
> wrote:
>> Hi Everyone:
>>
>> This is a vote to rele
Hi Claus,
Just in case for info, there is apparently a new BND Maven plugin [1] that is
supposed to alleviate some of the issues encountered with maven-bundle-plugin.
I haven’t tried it (nor am knowledgeable in the area) but that may be good to
know at some point for that piece of work.
[1]: h
+1
Tested CDI examples (standalone, PAX CDI / Karaf, WildFly).
> On 23 Mar 2016, at 08:15, Claus Ibsen wrote:
>
> +1
>
> Tested a number of examples both karaf, standalone and spring-boot and cdi.
>
>
>
> On Tue, Mar 22, 2016 at 3:22 PM, Claus Ibsen wrote:
>> Hi
>>
>> I tested the RC2 wit
Awesome, thanks Gregor!
> On 21 Mar 2016, at 09:10, Claus Ibsen wrote:
>
> Hi
>
> Yay that sounds great. Good to hear the 2.17 is on the way.
>
> On Mon, Mar 21, 2016 at 9:06 AM, Gregor Zurowski
> wrote:
>> Hi Everyone:
>>
>> I have created the RC and will make it available shorty. I will a
next week or a bit longer to
> finish up the other stuff.
> But sure any start of a test module for cdi is better than nothing.
>
> On Fri, Mar 4, 2016 at 5:13 PM, Antonin Stefanutti
> wrote:
>> Hi Claus,
>>
>> I’ve been working on a camel-test-cdi module lately.
Hi Claus,
I’ve been working on a camel-test-cdi module lately. It’s not full-fledge as I
want it to be yet, though I have a working thing that’d be a great addition to
the new Camel CDI component. I can polish up what I have quickly so that it’s
part of 2.17.0 and complete the work afterward.
gt; --
>> Andrea Cosentino
>> --
>> Apache Camel PMC Member
>> Apache Karaf Committer
>> Email: ancosen1...@yahoo.com
>> Twitter: @oscerd2
>> Github: oscerd
>>
>>
>>
>> On Wednesday, January 27,
> On 27 Jan 2016, at 13:51, Claus Ibsen wrote:
>
> On Wed, Jan 27, 2016 at 1:07 PM, Antonin Stefanutti
> wrote:
>> Yes I think we should add the comments.
>>
>> For the SJMS and Metrics components, it shows the need to be able to
>> categorise the
Yes I think we should add the comments.
For the SJMS and Metrics components, it shows the need to be able to categorise
the options. Obvious categories would be 'consumer' and 'producer' though for
components like Metrics, some options are only applicable to a certain URI
remaining that are com
ple cdi dependency injection framework.
>
> It would be cool to have a camel-test-cdi module separated from
> camel-cdi so we have similar "easy of testing" as with the other
> testing modules.
>
> On Thu, Jan 14, 2016 at 6:04 PM, Antonin Stefanutti
> wrote:
&g
Hi everyone,
I’ve just completed the work improving the Camel CDI component and open PR
https://github.com/apache/camel/pull/769.
As the open PR is quite large, I’ve documented the most important contributions
in https://issues.apache.org/jira/browse/CAMEL-9201.
For those interested, I’d like
Hi Camel Dev,
My ICLA have been received at Apache.
Could you please grant my username 'astefanutti' edit permission on Camel wiki.
Thanks,
Antonin
Hi All,
I’ve been working on improving the Camel CDI integration over the last couple
of months. As it happens that a redesign was required to make it more 'CDI
spirit', I’ve done the heavy work in a separate project and documented the
improvements over the existing component from the Apache Ca
49 matches
Mail list logo
