The Camel PMC is pleased to announce the release of Apache Camel 3.16.0.
Apache Camel is an open source integration framework that empowers you
to quickly and easily integrate various systems consuming or producing
data.
This release is a new minor release and contains 206 bug fixes and
Thanks for your feedback.
I verified it for queue and indeed subscriptionName is not required. It’s only
required for topics.
I have reverted the commit.
Babak
> On 28 Mar 2022, at 11:28, Andrea Cosentino wrote:
>
> Also, If you use a queue and not a topic, the subscriptionName is not
>
Hi
Thanks Zoran
I stopped and delete these PR jobs - its a waste of time when people
work on a draft PR.
The website is just updated with the 3.16 release blurb.
On Mon, Mar 28, 2022 at 11:30 AM Zoran Regvart wrote:
>
> Hi Cameleers,
> This reminds me of the "Are we the baddies"
On Mon, Mar 28, 2022 at 11:28 AM Andrea Cosentino wrote:
>
> Also, If you use a queue and not a topic, the subscriptionName is not
> mandatory.
>
> I think we should revert this.
>
+1
Also it would be good to have a JIRA ticket about such a change the
next time, so we can track this - end users
Hi Cameleers,
This reminds me of the "Are we the baddies" sketch/meme[1].
The reason why PR#800 is not built is because PR#809[2] is taking up
all the CI resources. I do wish that branches are not pushed to
camel-website git repository directly but built from forks using
GitHub Actions. For
Also, If you use a queue and not a topic, the subscriptionName is not
mandatory.
I think we should revert this.
Il giorno lun 28 mar 2022 alle ore 08:59 Claus Ibsen
ha scritto:
> Hi Babak
>
> Did you consider that the producer may not require this parameter? And
> if so then it cannot be
It's related to the other jobs. I don't think there is so much we could do.
Don't know of there is an ongoing issue on Jenkins, but i don't think so
Il lun 28 mar 2022, 10:27 Gregor Zurowski ha
scritto:
> Hi Everyone,
>
> I pushed some changes for the 3.16.0 release to the camel-website
>
Hi Everyone,
I pushed some changes for the 3.16.0 release to the camel-website
repository, but it seems that the build is stuck on "Waiting for next
available executor":
https://ci-builds.apache.org/job/Camel/job/Camel.website/job/main/800/console
Anything I can do there?
Thanks in advance,
Hi Babak
Did you consider that the producer may not require this parameter? And
if so then it cannot be marked as required.
You can only add this in its documentation, and have some code that
checks when creating the consumer that the option is present.
It's a limitation with @UriParam that we
Thanks for your participation in this vote.
The vote passes with the following results:
+1 binding: 10 (Alexandre Gallice, Andrea Cosentino, Babak Vahdat,
Claus Ibsen, Gregor Zurowski, Jean-Baptiste Onofré, Luca Burgazzoli,
Otavio Rodolfo Piske, Pascal Schumacher, Zoran Regvart)
+1 non-binding:
+1 (binding)
Gregor
On Wed, Mar 23, 2022 at 11:26 AM Gregor Zurowski
wrote:
>
> Hi Everyone:
>
> This is a vote to release Apache Camel 3.16.0, a new minor release
> with 206 fixes and improvements.
>
> Release notes:
>
11 matches
Mail list logo