As a side note, it's not only aligning the features, it's also upgrading
the servicemix bundles to be able to align, JB knows what I'm talking about.
I helped there a lot too (less in the last year or so) and it's really a
mess.
Il mer 18 gen 2023, 20:43 Romain Manni-Bucau ha
scritto:
> Le mer.
Le mer. 18 janv. 2023 à 20:17, Andrea Cosentino a
écrit :
> Il mer 18 gen 2023, 20:06 Romain Manni-Bucau ha
> scritto:
>
> > Le mer. 18 janv. 2023 à 19:43, Andrea Cosentino a
> > écrit :
> >
> > > Hello,
> > >
> > > The point is just one in relation to OSGi metadata. The components will
> > be
Il mer 18 gen 2023, 20:06 Romain Manni-Bucau ha
scritto:
> Le mer. 18 janv. 2023 à 19:43, Andrea Cosentino a
> écrit :
>
> > Hello,
> >
> > The point is just one in relation to OSGi metadata. The components will
> be
> > consumed, also, by runtimes that don't need OSGi metadata, so why all the
>
> On Jan 18, 2023, at 12:43 PM, Andrea Cosentino wrote:
>
> Hello,
>
> The point is just one in relation to OSGi metadata. The components will be
> consumed, also, by runtimes that don't need OSGi metadata, so why all the
> components should be with OSGi metadata and packaged as bundles?
Hi A
Le mer. 18 janv. 2023 à 19:43, Andrea Cosentino a
écrit :
> Hello,
>
> The point is just one in relation to OSGi metadata. The components will be
> consumed, also, by runtimes that don't need OSGi metadata, so why all the
> components should be with OSGi metadata and packaged as bundles?
>
I'm m
Hello,
The point is just one in relation to OSGi metadata. The components will be
consumed, also, by runtimes that don't need OSGi metadata, so why all the
components should be with OSGi metadata and packaged as bundles?
I don't see the reason why. At least the OSGi metadata should be generated
u
I have a similar question on this point--
> On Jan 18, 2023, at 12:02 PM, Łukasz Dywicki wrote:
>
> 6) I do not see any sign of what is going to happen with OSGi metadata which
> is present for Apache Camel 3.x components. Is Camel 4.x going to retain OSGi
> metadata?
How is maintaining OGSI
-1 from my side
Given the scope of work and possible improvements I do not see a strong
reason to move camel-karaf into karaf-camel hence my veto on the proposal.
This vote opens up a dangerous path where Karaf gains more fat and moves
into direction of integration product on its own while, til
+1 (binding as Karaf PMC member)
Freeman
On Wed, Jan 18, 2023 at 5:03 AM Jean-Baptiste Onofré
wrote:
> Hi guys,
>
> The Apache Camel community proposed to move Camel Karaf to the Apache
> Karaf project (as a new subproject).
>
> As a reminder, Camel Karaf provides:
> - support Camel Contexts/R
+1 (binding)
regards,
François
On 18/01/2023 11:03, Jean-Baptiste Onofré wrote:
Hi guys,
The Apache Camel community proposed to move Camel Karaf to the Apache
Karaf project (as a new subproject).
As a reminder, Camel Karaf provides:
- support Camel Contexts/Routes as OSGi services (camel-cor
+1 (binding)
On Wed, Jan 18, 2023 at 11:03 AM Jean-Baptiste Onofré
wrote:
> Hi guys,
>
> The Apache Camel community proposed to move Camel Karaf to the Apache
> Karaf project (as a new subproject).
>
> As a reminder, Camel Karaf provides:
> - support Camel Contexts/Routes as OSGi services (camel
+1 (binding)
Le mer. 18 janv. 2023 à 11:03, Jean-Baptiste Onofré a
écrit :
> Hi guys,
>
> The Apache Camel community proposed to move Camel Karaf to the Apache
> Karaf project (as a new subproject).
>
> As a reminder, Camel Karaf provides:
> - support Camel Contexts/Routes as OSGi services (cam
+1 (binding)
--
Andrea Cosentino
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Wednesday, January 18, 2023 at 11:03:27 AM GMT+1, Jean-Baptiste Onofré
wrote:
Any hope to evaluate the "bunch" of users which would move to this new
project and not spring-boot/quarkus/anything-hype-cause-$$?
Can be great to see if the community wants to focus on karaf or aggregation
on the long run due to available/active resources.
If we have proofs there is a need and c
Correct, I mentioned this in my previous email (camel-karaf to karaf-camel).
Regards
JB
On Wed, Jan 18, 2023 at 1:26 PM Claus Ibsen wrote:
>
> Hi
>
> And the source code java package names needs to be migrated as well
> org.apache.camel.karaf -> org.apache.karaf.camel
>
> And documentation is mo
Hi
And the source code java package names needs to be migrated as well
org.apache.camel.karaf -> org.apache.karaf.camel
And documentation is moved over to Apache Karaf, where the karaf camel
releases its own new set of documentation/website.
The existing Camel Karaf 3.x will be maintained as-is
Sounds like a plan. Will check in tomorrow.
Thanks,
Gregor
On Wed, Jan 18, 2023 at 12:09 PM Claus Ibsen wrote:
>
> Hi Gregor
>
> If you wait till tomorrow then Spring Boot 2.7.8 is to be released, it
> would be good to get that upgraded before cutting.
> https://calendar.spring.io/
>
> On Wed, J
Hi
This SHOULD also mean that the project should be known as karaf-camel
AND that the artifacts released for download and maven central should have
changed GAVs
groupId = org.apache.karaf.camel
artifactId = karaf-camel-xxx
version = x.y.z
For version then it may want to follow the Camel version,
Hi Gregor
If you wait till tomorrow then Spring Boot 2.7.8 is to be released, it
would be good to get that upgraded before cutting.
https://calendar.spring.io/
On Wed, Jan 18, 2023 at 11:02 AM Gregor Zurowski
wrote:
> Hi,
>
> Sounds good. We released 3.18.4 on December 1st, so it's probably a
>
Hi
It would be good to upgrade to spring 5.3.25 in the 3.18.x branch before
cutting the release.
On Wed, Jan 18, 2023 at 11:02 AM Gregor Zurowski
wrote:
> Hi,
>
> Sounds good. We released 3.18.4 on December 1st, so it's probably a
> good time to get the release started.
>
> I am taking a look
Hi,
Great news!
+1 (non-binding)
Regards,
Nicolas
From: Jean-Baptiste Onofr?
Sent: Wednesday, January 18, 2023 11:03
To: dev
Cc: dev
Subject: [VOTE] Accept karaf-camel as new Apache Karaf subproject
Hi guys,
The Apache Camel community proposed to move Camel
Hi Andrea,
yes, thanks. I forgot to mention that the move if for Camel 4.x (not
the existing branch/version).
Regards
JB
On Wed, Jan 18, 2023 at 11:05 AM Andrea Cosentino wrote:
>
> As as side note to what JB just wrote:
>
> as Apache Camel community we'll still maintain the 3.x side of the
> p
As as side note to what JB just wrote:
as Apache Camel community we'll still maintain the 3.x side of the
projects, for continuity, Karaf-camel will be the house for the Camel 4.x
OSGi support.
Thanks.
Il giorno mer 18 gen 2023 alle ore 11:03 Jean-Baptiste Onofré <
j...@nanthrax.net> ha scritto:
Hi guys,
The Apache Camel community proposed to move Camel Karaf to the Apache
Karaf project (as a new subproject).
As a reminder, Camel Karaf provides:
- support Camel Contexts/Routes as OSGi services (camel-core-osgi)
- Camel components specific to OSGi and Karaf (camel-blueprint, camel-scr, ..
Hi,
Sounds good. We released 3.18.4 on December 1st, so it's probably a
good time to get the release started.
I am taking a look now and can start cutting the release today.
Thanks,
Gregor
On Tue, Jan 17, 2023 at 10:16 AM Andrea Cosentino wrote:
>
> Hello,
>
> I think we should do a new 3.18.x
25 matches
Mail list logo