t; On Thu, Jul 27, 2023 at 10:23 AM Nicolas Filotto
> wrote:
>
> > +1 to use GitHub Discussion too
> >
> > From: Andrea Cosentino
> > Sent: Thursday, July 27, 2023 10:13
> > To: dev
> > Subject: Re: Using ca
Kind regards
On Thu, Jul 27, 2023 at 10:23 AM Nicolas Filotto
wrote:
> +1 to use GitHub Discussion too
>
> From: Andrea Cosentino
> Sent: Thursday, July 27, 2023 10:13
> To: dev
> Subject: Re: Using camel-test-infra-core vs regular testing
>
&
+1 to use GitHub Discussion too
From: Andrea Cosentino
Sent: Thursday, July 27, 2023 10:13
To: dev
Subject: Re: Using camel-test-infra-core vs regular testing
I'm +1 to use discussions and I think we could to enable it to INFRA.
--
Andrea Cose
I'm +1 to use discussions and I think we could to enable it to INFRA.
--
Andrea Cosentino
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Thursday, July 27, 2023 at
Hi
I had a talk with Otabio about this subject.
There has been some misunderstanding and miscommunication on my part, and
this mail thread may also have a few related subjects conflated.
In the short term we should focus on bringing Camel 4.0 to GA.
After this release then I think there is time
On Mon, Jul 24, 2023 at 3:45 PM Nicolas Filotto wrote:
> > One problem, IMHO, camel-test-junit5 already has a dependency chain that
> is
> > pretty complex, which is one of the things I wanted to solve ... But,
> more
>
> Sorry if it is a naive question but can't it be solved or at least
> improv
> One problem, IMHO, camel-test-junit5 already has a dependency chain that is
> pretty complex, which is one of the things I wanted to solve ... But, more
Sorry if it is a naive question but can't it be solved or at least improved
directly at camel-test-junit5 level? But please note this artifact
Hi,
On Mon, Jul 24, 2023 at 9:37 AM Nicolas Filotto wrote:
> Hi,
>
> I tend to agree with Claus, camel-test-infra should be used only for
> integration tests for the reasons raised by Claus but also due to its name.
> It would be really misleading for the community to have to depend on an
> arti
Hi,
I tend to agree with Claus, camel-test-infra should be used only for
integration tests for the reasons raised by Claus but also due to its name. It
would be really misleading for the community to have to depend on an artifact
called camel-test-infra for a unit test don't you agree?
In came
Hi,
On Thu, Jul 20, 2023 at 10:08 AM Claus Ibsen wrote:
> Hi
>
> Sorry at this time I cannot support these kinds of changes.
>
> We have a standard practice in Camel on how to do unit tests (camel-test)
> which we had for 15+ years.
> We should dog food our own standard, and it's also a way for
Hi
Sorry at this time I cannot support these kinds of changes.
We have a standard practice in Camel on how to do unit tests (camel-test)
which we had for 15+ years.
We should dog food our own standard, and it's also a way for end users to
see existing src/test code, how to use a given Camel compo
Hi Claus,
test infra solves a few problems that we have in camel-test-support-junit5:
- it has a simpler dependency chain (it depends only on core)
- it allows managing the service ordering explicitly (i.e.: it's possible
to define in which order services can be initialized)
- it is much simpler a
12 matches
Mail list logo
