jbonofre closed issue #42: `minho-spring-boot` application manager should look
for `spring-boot` type
URL: https://github.com/apache/karaf-minho/issues/42
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to
jbonofre merged PR #43:
URL: https://github.com/apache/karaf-minho/pull/43
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
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
>
Hello
I don't know much about SMX distributions (except SMX bundles), but having
a Karaf distro with ready-to-use Camel + CXF + ActiveMQ sounds like a good
idea.
regards
Grzegorz Grzybek
śr., 18 sty 2023 o 13:44 Jean-Baptiste Onofré napisał(a):
> Hi guys,
>
> The ServiceMix community is
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
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
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
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 guys,
The ServiceMix community is discussing about moving most of the SMX
parts into Karaf (the useful parts ;) ).
As part of this move, the "main" ServiceMix distribution is mainly a
Karaf assembly.
Currently, we have two distributions: "standard"
(apache-karaf-x.x.x.tar.gz) and "minimal"
Hi JB,
Is there a community behind or did people already moved to Karaf so this is
just about killing smix project officially.
Trying to see if it is mainly about having really itests and enriching
features.xml (theorically nothing new) or creating a new distro and almost
a subproject.
Le mer.
+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:
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
jbonofre opened a new issue, #44:
URL: https://github.com/apache/karaf-minho/issues/44
With the `minho-spring-boot` application manager, the user can load several
spring-boot application via the `ConfigService#Applications`. For instance, he
can define spring-boot applications via
+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
+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
+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
+1 (non-binding)
From: Jean-Baptiste Onofr?
Sent: Wednesday, January 18, 2023 13:44
To: dev ; user ;
d...@servicemix.apache.org ;
us...@servicemix.apache.org
Subject: [PROPOSAL] Create integration (ServiceMix like) distribution in Karaf
OSGi runtime
Hi guys,
Sounds good.
+1
regards,
François
On 18/01/2023 13:44, Jean-Baptiste Onofré wrote:
Hi guys,
The ServiceMix community is discussing about moving most of the SMX
parts into Karaf (the useful parts ;) ).
As part of this move, the "main" ServiceMix distribution is mainly a
Karaf assembly.
+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
> 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
-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,
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
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
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
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
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
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
+1
I think this could be a good solution to get a "ready to use" platform
as SMX was. Many customers and I had been using SMX for years, for this
rich integrated quality.
Nevertheless, I'm not sure this will be a "miracle" solution. My last
and current works are all about migrating a
28 matches
Mail list logo
