Hi
An integration track would be great, but I very likely will not be
able to attend an in-person conference this year.
On Tue, Mar 15, 2022 at 11:34 AM Zoran Regvart wrote:
>
> Hi Cameleers,
> this year's ApacheCon will be an in-person event in New Orleans,
> Louisiana from October 3-7, 2022.
Hi
Okay so I have fixed this on main branch and a PR with the set of
commits to fix this which can be merged on the 3.16.0 branch you use
for the release
https://github.com/apache/camel-spring-boot/pull/479
On Tue, Mar 22, 2022 at 10:06 PM Claus Ibsen wrote:
>
> Hi
>
> Okay so its related to all
Hello Zoran,
I would like to help but I have never participated in in-person ApacheCon.
What does volunteering mean in this context? I did not find any information
on https://www.apachecon.com
Also I'm thinking about making a presentation/demo of Apache Camel Karavan,
but again need some guidance
Hi
Okay so its related to all the tests added to the -starter JARs where
they have added test dependencies, but it seems this requires to add
so it can pickup the correct Camel version.
org.apache.camel
camel-test-spring-junit5
+ ${camel-version}
On Tue, Mar 22, 2022 at 10
Hi
Okay got a step further
[ERROR] org.apache.camel:camel-test-spring-junit5:jar:3.16.0-SNAPSHOT:test
[ERROR] in project 'Camel SB Starters :: Avro'
(org.apache.camel.springboot:camel-avro-starter:jar:3.16.0-SNAPSHOT)
On Tue, Mar 22, 2022 at 9:14 PM Claus Ibsen wrote:
>
> Hi
>
> If I try to
Hi
If I try to run the dry run prepare for the release tag on CSB I can see
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.4.2:prepare
(default-cli) on project spring-boot: Can't release project due to non
released dependencies :
[ERROR]
org.apache.camel:bom-g
Hi Cameleers,
asking once again, without volunteers helping to organize this there
will be no Integration track at ApacheCon this year and we are
approaching final moments in which the organizers will accept tracks.
zoran
On Tue, Mar 15, 2022 at 11:33 AM Zoran Regvart wrote:
>
> Hi Cameleers,
>
What are the deps with snapshot?
Il mar 22 mar 2022, 19:35 Gregor Zurowski ha
scritto:
> I am having another problem when preparing camel-spring-boot. There
> are dependencies with snapshot versions in
> `tooling/camel-spring-boot-dependencies/pom.xml` and I vaguely recall
> we went through this
I am having another problem when preparing camel-spring-boot. There
are dependencies with snapshot versions in
`tooling/camel-spring-boot-dependencies/pom.xml` and I vaguely recall
we went through this before... Claus, do you remember this?
Thanks,
Gregor
On Sun, Mar 20, 2022 at 12:09 PM Claus Ib
Hi again,
It should be good now; it is enabled only with the maven profile plugin-itest
like other maven plugins.
Thank you for your patience,
Regards,
Nicolas
From: Gregor Zurowski
Sent: Tuesday, March 22, 2022 10:17
To: dev@camel.apache.org
Subject: Re: Camel
Hi Nicolas,
You can apply on `main` and I can cherry-pick it onto the
`release/3.16.0` branch.
Thanks,
Gregor
On Tue, Mar 22, 2022 at 10:13 AM Nicolas Filotto wrote:
>
> Hi Claus,
>
> OK, I do it now. In which branch(es) main only or also in the release branch?
> ___
On Tue, Mar 22, 2022 at 10:13 AM Nicolas Filotto wrote:
>
> Hi Claus,
>
> OK, I do it now. In which branch(es) main only or also in the release branch?
main and
https://github.com/apache/camel/tree/release/3.16.0
>
> From: Claus Ibsen
> Sent: Tuesday, March 22,
Hi Claus,
OK, I do it now. In which branch(es) main only or also in the release branch?
From: Claus Ibsen
Sent: Tuesday, March 22, 2022 10:09
To: dev
Subject: Re: Camel 3.16.0 Release
!---|
This M
Hi Nicolas
Can you move this integration test to root/tests where we have itests
- then they are run at the end - as this problem will bite us again
and again.
On Tue, Mar 22, 2022 at 10:04 AM Nicolas Filotto wrote:
>
> Hi,
>
> In a nutshell, it is an integration test that I added which fails b
Hi,
In a nutshell, it is an integration test that I added which fails because of a
chicken and egg problem. It will pass once the new version will actually be
published.
If possible, can you use the option the maven profile "fastinstall" to skip it?
Otherwise you will need to comment it like t
I was able to prepare the release in dry run, but getting the
following error now when starting it without dry run:
```
[INFO] --- maven-invoker-plugin:3.2.2:integration-test
(integration-test) @ camel-package-maven-plugin ---
[INFO] Building: HeaderSupport/pom.xml
[INFO] run post-build script ver
16 matches
Mail list logo
