Camel Karaf project generates JARs for what Camel components they support
only - the same is what we do for Spring Boot / Quarkus / Camel Kafka
Connector etc.
JB talks about Karaf 5 with a new way of deploying that sounds like this
can be done smarter and easier.
For example if Camel Karaf
Hi
Today we did some commits on main that updates parent/pom.xml and camel-bom/
pomx.ml, but it looks like if you build a single component locally it
updates the file due to we now include missing camel maven plugins from
components that are listed in the top.
We need to look at this tomorrow to
Hey folks,
On 26.11.2022 09:51, Andrea Cosentino wrote:
In more than one situation aligning OSGi stuff have been really hard. Less
and less community members are helping on the Karaf side and releasing
sometimes have been slow down by these troubles. Also OSGi have been drop
in a lot of 3rd
On Wed, Nov 30, 2022 at 3:56 PM Matt Pavlovich wrote:
> Hi All—
>
> What benefit comes from removing the OSGi manifest? Seems like repackaging
> for Karaf could be an option, but leaving the auto-gen osgi headers in is a
> good idea. A *ton* of large apps use OSGi runtimes b/c it is an effective
Hi All—
What benefit comes from removing the OSGi manifest? Seems like repackaging for
Karaf could be an option, but leaving the auto-gen osgi headers in is a good
idea. A *ton* of large apps use OSGi runtimes b/c it is an effective way to
allow third parties to provide extensions and plugins.
Hello,
If we move camel-karaf under the Karaf project, there is no reason from the
Camel point of view to provide OSGi manifests.
Karaf become a consumer of Camel releases like other projects.
Il mer 30 nov 2022, 15:56 Matt Pavlovich ha scritto:
> Hi All—
>
> What benefit comes from
On 30.11.2022 18:15, Claus Ibsen wrote:
For example if Camel Karaf support camel-ftp, then they can build and
release
org.apache.karaf.camel:camel-ftp-bundle:4.0.0
Sorry, but it this makes no point as class contents of that thing will
be 1:1 with camel-ftp. The only one difference are
Hi
On Mon, Nov 28, 2022 at 10:40 AM Jean-Baptiste Onofré
wrote:
> Hi guys,
>
> I understand that Karaf/OSGi is not in the Camel community target
> anymore, and it makes sense.
> I proposed a time ago to refactor the approach of Camel components for
> Karaf, using special packaging (embedded
Ok so we will have a camel-core.jar and
camel-core-with-manifest-osgi.jar just with the manifest file add-in for
each camel core jar.
On 30/11/2022 13:53, Andrea Cosentino wrote:
This would become something karaf-camel is responsible for.
Il giorno mer 30 nov 2022 alle ore 13:49 fpapon ha
Hi,
Actually removing the OSGi manifests from the bundles coming from the general
camel build would mean that we have to create an OSGi wrapper bundle for each
and every jar coming out of the general build, which looks like a lot of
maintenance effort to me.
Best regards
Stephan
Hi
I have done a couple of builds and it seems better now.
If anyone else have modified files then let me know
On Wed, Nov 30, 2022 at 7:26 PM Claus Ibsen wrote:
> Hi
>
> Today we did some commits on main that updates parent/pom.xml and
> camel-bom/pomx.ml, but it looks like if you build a
OSGi metadata in manifest is different than Karaf feature for managing
bundle dependencies in component integration.
I think that there is no effort from Camel team to keep the
maven-bundle-plugin from the main source modules.
On 30/11/2022 18:15, Claus Ibsen wrote:
Camel Karaf project
Hi,
For this point "Camel v4 core and component JARs will no longer generate
OSGi MANIFEST.MF" I'm not sure that removing the generation from the
core Camel is a good thing...
regards,
François
On 30/11/2022 10:44, Claus Ibsen wrote:
Hi
On Mon, Nov 28, 2022 at 10:40 AM Jean-Baptiste
This would become something karaf-camel is responsible for.
Il giorno mer 30 nov 2022 alle ore 13:49 fpapon ha
scritto:
> Hi,
>
> For this point "Camel v4 core and component JARs will no longer generate
> OSGi MANIFEST.MF" I'm not sure that removing the generation from the
> core Camel is a
Hi
Lets try to get ready for the 3.20 release by the end of next week.
There are about 20 JIRAs pending, but you can move to 3.21 if you dont have
time.
On Tue, Nov 22, 2022 at 7:17 AM Claus Ibsen wrote:
> Hi
>
> I have created v3.21 where we can move tickets that will not make it for
> 3.20.
Agree
On 30/11/2022 14:09, Siano, Stephan wrote:
Hi,
Actually removing the OSGi manifests from the bundles coming from the general
camel build would mean that we have to create an OSGi wrapper bundle for each
and every jar coming out of the general build, which looks like a lot of
16 matches
Mail list logo
