Thanks, this worked. I was able to run through the whole prepare phase.
On Mon, Mar 6, 2023 at 11:31 AM Claus Ibsen wrote:
>
> Hi
>
> Damn, can you try with this commit
> https://github.com/apache/camel/commit/afa1a18c9abbe684218864c86bf817bdd29a5b54
>
>
>
> On Mon, Mar 6, 2023 at 11:17 AM
Maybe also adding
maven-surefire-plugin
${maven-surefire-plugin-version}
false
false
In the archetype resources might help
Il giorno lun 6 mar 2023 alle
Hi
Damn, can you try with this commit
https://github.com/apache/camel/commit/afa1a18c9abbe684218864c86bf817bdd29a5b54
On Mon, Mar 6, 2023 at 11:17 AM Gregor Zurowski
wrote:
> Unfortunately the issue still persists:
>
> ```
> [INFO]
>
Unfortunately the issue still persists:
```
[INFO]
[INFO] Reactor Summary for Camel Dummy Component Parent 0.0.1:
[INFO]
[INFO] Camel Dummy Component Parent ... SUCCESS [ 0.233 s]
[INFO] Camel Dummy
I will pull in your commits and try again.
Thanks,
Gregor
On Mon, Mar 6, 2023 at 6:46 AM Claus Ibsen wrote:
>
> Hi
>
> I pushed some commits to the main branch that re-orders the build so
> archetypes are built after the catalog.
> That could help at least that the dummy component has been
Hi
I pushed some commits to the main branch that re-orders the build so
archetypes are built after the catalog.
That could help at least that the dummy component has been generated before
the archetypes.
To disable the testing then yeah I am puzzled as well. We can also
temporarily remove those
I have created a ticket to make it easier to build catalog before archetypes
This requires to remove a little bit in CamelCatalog that we dont really
use for anything
https://issues.apache.org/jira/browse/CAMEL-19117
On Sun, Mar 5, 2023 at 9:22 PM Claus Ibsen wrote:
> Hi
>
> What would we
Hi
What would we need to do to try to reproduce this?
mvn verify
runs the integration tests and all archetypes succeeds the tests.
Even if we hack to disable something in api-component then it may just fail
at the next archetype.
Did we not have a similar problem like this in the past?
Ah it
Any update?
Il dom 5 mar 2023, 14:01 Andrea Cosentino ha scritto:
> Yeah, maybe
>
> Il dom 5 mar 2023, 13:43 Gregor Zurowski ha
> scritto:
>
>> It didn't really do anything. I assume because it would need to be
>> configured within the dummy project generated by the archetype?
>>
>> Thanks
>>
Yeah, maybe
Il dom 5 mar 2023, 13:43 Gregor Zurowski ha
scritto:
> It didn't really do anything. I assume because it would need to be
> configured within the dummy project generated by the archetype?
>
> Thanks
> Gregor
>
> On Sun, Mar 5, 2023 at 11:04 AM Gregor Zurowski
> wrote:
> >
> > I
It didn't really do anything. I assume because it would need to be
configured within the dummy project generated by the archetype?
Thanks
Gregor
On Sun, Mar 5, 2023 at 11:04 AM Gregor Zurowski
wrote:
>
> I have added a surefire plugin configuration to the release profile
> section and am trying
I have added a surefire plugin configuration to the release profile
section and am trying to prepare the release with that configuration.
I am wondering if that will help due to the message `[WARNING] The
requested profile "release" could not be activated because it does not
exist.`
Will post an
Good point, let me try.
On Sun, Mar 5, 2023 at 10:44 AM Andrea Cosentino wrote:
>
> I think you should add the configuration to surefire plugin and not
> failsafe only
>
> Il dom 5 mar 2023, 10:42 Andrea Cosentino ha scritto:
>
> > Ah no, already done..
> >
> > Il dom 5 mar 2023, 10:42 Andrea
I think you should add the configuration to surefire plugin and not
failsafe only
Il dom 5 mar 2023, 10:42 Andrea Cosentino ha scritto:
> Ah no, already done..
>
> Il dom 5 mar 2023, 10:42 Andrea Cosentino ha scritto:
>
>> Can you add also failIfNoTests?
>>
>> Il dom 5 mar 2023, 10:37 Gregor
Ah no, already done..
Il dom 5 mar 2023, 10:42 Andrea Cosentino ha scritto:
> Can you add also failIfNoTests?
>
> Il dom 5 mar 2023, 10:37 Gregor Zurowski ha
> scritto:
>
>> I am having an issue during the prepare phase building
>> camel-archetype-api-component. It runs the integration tests
Can you add also failIfNoTests?
Il dom 5 mar 2023, 10:37 Gregor Zurowski ha
scritto:
> I am having an issue during the prepare phase building
> camel-archetype-api-component. It runs the integration tests (although
> it shouldn't?) and fails as follows:
>
> ```
> [INFO]
>
I am having an issue during the prepare phase building
camel-archetype-api-component. It runs the integration tests (although
it shouldn't?) and fails as follows:
```
[INFO]
[INFO] Reactor Summary for Camel Dummy Component
Hi
Thanks Gregor.
The branches are ready for cutting M2 - good luck.
On Sat, Mar 4, 2023 at 2:54 AM Gregor Zurowski
wrote:
> I have created the following two PRs for the Spring Boot 3.0.4 upgrade:
>
> Camel Spring Boot: https://github.com/apache/camel-spring-boot/pull/771
> Camel core
I have created the following two PRs for the Spring Boot 3.0.4 upgrade:
Camel Spring Boot: https://github.com/apache/camel-spring-boot/pull/771
Camel core dependencies: https://github.com/apache/camel/pull/9467
On Thu, Mar 2, 2023 at 4:24 PM Claus Ibsen wrote:
>
> Hi Gregor
>
> Just a heads up
Hi Gregor
Just a heads up that we will aim to upgrade to spring boot 3.0.4 that is to
be released tomorrow
https://issues.apache.org/jira/browse/CAMEL-19110
When that is done then we would be ready for cutting the release
On Wed, Mar 1, 2023 at 8:11 PM Gregor Zurowski
wrote:
> I am available
19062 is on-going, but since we are talking about a milestone, it's fine to
go ahead with a release.
Thanks Gregor.
Il giorno gio 2 mar 2023 alle ore 09:23 Claus Ibsen
ha scritto:
> On Wed, Mar 1, 2023 at 8:11 PM Gregor Zurowski
> wrote:
>
> > I am available for cutting the release this
On Wed, Mar 1, 2023 at 8:11 PM Gregor Zurowski
wrote:
> I am available for cutting the release this weekend or next week.
>
>
That would be great. I think cutting this weekend is good. I have moved
JIRA tickets from M2 to M3.
Otavio is also leaving for PTO and he will therefore not be working
I am available for cutting the release this weekend or next week.
On Wed, Mar 1, 2023, 9:07 AM Claus Ibsen wrote:
> Hi
>
> We should close down for a M2 release.
> Lets try to get the last bits ready this week, and see if Gregor has time
> next week to cut M2.
>
>
>
> On Fri, Feb 17, 2023 at
Hi
We should close down for a M2 release.
Lets try to get the last bits ready this week, and see if Gregor has time
next week to cut M2.
On Fri, Feb 17, 2023 at 7:32 AM Claus Ibsen wrote:
> Hi
>
> In March we should aim to release M2.
> We should aim to get the CI server test failures a bit
Not that it's consequential to the release, but I'm hoping to
have CAMEL-18551 (salesforce Pub/Sub API) ready for M2.
On Fri, Feb 17, 2023 at 3:30 AM Otavio Rodolfo Piske
wrote:
> Hello,
>
> +1 from me. I am not sure if I will finish the entirety of CAMEL-15105
> before I go on PTO on March
Hello,
+1 from me. I am not sure if I will finish the entirety of CAMEL-15105
before I go on PTO on March 2nd, but I think I can submit a good chunk of
it (something like updated docs + 30% of the API changes)
Kind regards
On Fri, Feb 17, 2023 at 7:42 AM Andrea Cosentino wrote:
> I'm working
I'm working on the parent and i should finish next week I guess.
Sounds good to me +1
Il ven 17 feb 2023, 07:33 Claus Ibsen ha scritto:
> Hi
>
> In March we should aim to release M2.
> We should aim to get the CI server test failures a bit more fixed.
>
> I would also like to work on removing
Hi
In March we should aim to release M2.
We should aim to get the CI server test failures a bit more fixed.
I would also like to work on removing stuff that are deprecated and that we
should not carry forward in v4 - for example the InOptionalOut MEP and what
else.
There is also some more
28 matches
Mail list logo
