Hi Cédric
It's something that I plan for Karaf 4.5.0 and backport on 4.4.7. The
H6 feature requires a few wrappers. I will create the Jira to track
this.
Regards
JB
On Mon, Oct 7, 2024 at 5:26 PM Cedric Jonas wrote:
>
> Hi,
>
> We are currently building applications based on OSGi / Karaf and ca
Hi
As discussed together, that's more a camel-karaf issue. We now have a
GitHub Issue about that, I will fix this.
Regards
JB
On Sun, Sep 22, 2024 at 1:33 AM michael e wrote:
>
> Hello,
>
> I'm facing issue with karaf 4.4.5 & 4.4.6 i try using camel-debzium-mysql
>
> and i got this one
>
>
> 01
Hi
Actually, the plan is to remove the Camel and CXF version by default
(it's only used in the examples and tests).
I did camel-karaf 4.7.0 now and I will update CXF to support OSGi/Karaf back.
Regards
JB
On Tue, Jul 16, 2024 at 10:07 PM Paul Spencer
wrote:
>
> Karaf 4.4.6
>
> Should the Camel
Hi
It seems jaxb-api dependency is in a decommissioned repository.
jaxb-api 2.3.0 is available on Maven Central
(https://repo1.maven.org/maven2/javax/xml/bind/jaxb-api/).
So maybe you have a custom repositories list ? The netbeans.org (that
you are using) seems to be problematic.
Regards
JB
On F
Hi Greg
I will update EclipseLink version, there were some required features
to update, which is now the case.
If you can't wait, you can create your own EclipseLink feature. I can
share the PR with the upgrade asap.
Regards
JB
On Thu, Jul 25, 2024 at 6:38 PM Greg Logan wrote:
>
> Hi all,
>
> I
Hi Paul,
Sorry I didn't see your last email.
Do you mind to create a Jira with your features repo ? I will check
your features XML and try to reproduce.
Regards
JB
On Fri, Jul 12, 2024 at 5:59 PM Paul Spencer wrote:
>
> I have done some more testing and realized the install attribute allowable
Hi Paul
The value should be auto or manual.
Auto means that the features will be automatically installed as soon
as the repository is added, either using feature:repo-add or via the
deployer (dropping the feature repo in the deploy folder).
Regards
JB
On Thu, Jul 11, 2024 at 8:31 PM Paul Spence
Hi
If you had the Camel collector/event collector, yes.
FYI, I have several fixes/updates heading to a new Decanter release.
Regards
JB
On Mon, Jun 17, 2024 at 5:57 PM Ephemeris Lappis
wrote:
>
> Hello.
>
> Good news !
>
> Could you confirm that metrics from the adapter "jmx camel" are
> handl
Hi
CXF 4.x doesn’t ship OSGi headers and Karaf features. I created a Jira to
readd it (as we did for camel-Karaf).
I have to find time to work on this.
Regards
JB
Le ven. 7 juin 2024 à 07:15, James Bushell a écrit :
> Hi
>
> I’m upgrading an older camel blueprint project to the latest karaf u
g in the custom distribution maven plugin. Startup features should
> not be added to the boot feature list.
>
> br,
> Matthias
>
> On Sat, 25 May 2024 at 08:09, Jean-Baptiste Onofré wrote:
>>
>> For the record, we also have a example in Karaf directly:
>> https://g
Hi,
You can remove the management feature from the bootFeatures.
Regards
JB
On Fri, May 17, 2024 at 9:07 PM Bernd Eckenfels wrote:
>
>
> Hello,
>
> I want to harden the default installations and reduce the
> needed port footprints. karaf-magement adds a RMI Registry
> and a RMI Server for the J
About this issue, to avoid confusion, I will re-add spring 5.x
features in spring features repository (in addition of spring 6.x) for
Karaf 4.4.7.
Regards
JB
On Sat, May 18, 2024 at 8:38 PM Matthias Leinweber
wrote:
>
> Yes, I missed the spring-legacy feature. Nvm, problem solved
>
> On Sat, 18
Hi,
Maybe you missed my message on the camel mailing list, but camel-karaf
main branch supports Karaf 4.4.6 and Camel 4.x:
https://github.com/apache/camel-karaf
I plan to cut the first camel-karaf release soon.
Regards
JB
On Sat, May 18, 2024 at 6:56 PM Matthias Leinweber
wrote:
>
> Hi Karaf
Hi
We are a bit involved but today it's "decoupled", we have a kind of
different vision between the specs and the Karaf features service (in
terms of functionality).
So, no direct relation :)
Regards
JB
On Wed, May 22, 2024 at 1:13 PM Pavel Perikov wrote:
>
> Hi, list!
>
> What is the current
For the record, we also have a example in Karaf directly:
https://github.com/apache/karaf/tree/main/examples/karaf-log-appender-example
Regards
JB
On Fri, May 17, 2024 at 4:26 PM Matthias Leinweber
wrote:
>
> Hello Karaf Team,
>
> is it possible to directly add a custom log4j2 appender via wrap
Hi Steinar
as replied on the shiro mailing list, I gonna take a look.
Regards
JB
On Fri, May 24, 2024 at 7:54 PM Steinar Bang wrote:
>
> I am trying to get shiro 2.x (snapshot built from the current main)
> working in karaf:
> https://lists.apache.org/thread/b7lr44sqc352s4yx65xrjkf25jvhfr92
>
Hi,
I would say it's "half issue": just to feature:repo-add spring-legacy
and it will work out of the box. You can also add spring-legacy
features repository by default in the
etc/org.apache.karaf.features.cfg.
For Karaf 4.4.7, I will re-add spring 5 (in addition of spring 6)
features in spring "
Hi Steinar
There's not "core/compendium" services spec about that.
You can create your own easily :)
NB: Cave provided a storage layer for artifacts in the past, if you
wanna take a look.
Regards
JB
On Mon, May 6, 2024 at 6:50 PM Steinar Bang wrote:
>
> Is there an OSGi, or karaf specific file
Hi Cédric
You can provide the security schema via blueprint or programmatically,
overriding the karaf realm.
Or you can create a new realm and update all services (ssh, etc) with
this realm (more changes to do).
I would go more with the overriding karaf realm, probably easier (the
overriding bund
Hi
I will take a look.
Thanks
Regards
JB
Le sam. 20 avr. 2024 à 23:21, michael e a écrit :
> I wasn't clear so I just open a ticket here
> https://issues.apache.org/jira/browse/KARAF-7826?orderby=affectedVersion+DESC%2C+cf%5B12310271%5D+ASC%2C+priority+DESC%2C+updated+DESC
>
> Michael.
>
> ---
Hi Michael
It's because of bnd: it can detect the import based on byte code. The
problem is that wildcard matches only for clearly defined import and
sometime failed to find the package (especially with split package).
Using a fully qualified package actually import the package.
Regards
JB
On S
g to see if it
> was the one modifying the files, though.
>
> I've seen the problem happen with jmx, command, logging, feature service, and
> our own configuration files.
>
> Hopefully you can identify the problem.
>
> Thanks again!
>
> Jim Ziesig
>
> On Thu, M
similar
> (same?) issue: https://issues.apache.org/jira/browse/KARAF-7389
>
> regards
> Grzegorz Grzybek
>
> czw., 28 mar 2024 o 06:23 Jean-Baptiste Onofré napisał(a):
>>
>> Hi Jim
>>
>> We did some improvements of potential race conditions between features
&
Hi Jim
We did some improvements of potential race conditions between features
and config admin services. Remember some files in etc are not managed
by config admin (for instance startup.properties is used before the
services are actually started and not managed by config admin).
Let me try to rep
Hi Anthony
Good catch.
A simple workaround is to update bc bundles in the system repo and
update the features (a little painful but do-able).
I will fix that for 4.4.6 (I will create a Jira).
Thanks !
Regards
JB
On Thu, Mar 21, 2024 at 2:45 AM Anthony Wood wrote:
>
> Hi,
>
> There seems to be a
Hi,
Yes, it' possible to have several services by component (imho, it
should be avoided when possible to avoid unexpected cascading
refresh).
A component can implement multiple interfaces, and the @Component
annotation accepts the list of exposed interfaces.
Regards
JB
On Sat, Mar 16, 2024 at 7
Hi Steinar,
You can create a controller for instance by leveraging event admin (to
send an event triggering the reload, and the bundle decides what he
wants to reload). Pros, you control exactly what you want to reload.
Cons, you need to implement your Event handler.
Another option would be to def
Hi Michael
It looks like a ClassLoading issue (the import is there but the class
comes from another classloader).
Did you try to set the TCCL just before creating the vertx HttpServer ?
Regards
JB
On Sun, Mar 17, 2024 at 5:54 PM Michael Elbaz wrote:
>
> Hello i use vertx on Karaf everything is
Hi Matthias,
By default, the features are installed asynchronously (in different threads).
1/
The prerequisite flag "forces" the dependency feature to be fully
installed before continuing the current feature.
So it means basically, that:
bar
b
The bar feature will be fully installed and st
Hi Chandan,
I would not recommend the wrapper with large heap and new JDK. The
reason is because the Tanuki Java Wrapper used by the Karaf wrapper is
super old (due to license issue).
Do you see the same problem using the bin/karaf script ?
I would also recommend using G1 GC instead of CMS with
Hi Will
Did you take a look on
https://github.com/apache/karaf/tree/main/examples/karaf-log-appender-example
?
Generally speaking, the org.apache.logging* packages should be
imported in your bundle. The fragment would extend an existing bundle
classloader with your classes.
Maybe if you share a
Hi Jose
Karaf 4.2.14 is pretty old :) Assuming you have a JDK8 on your Windows
Server 2022, bin/karaf should work fine.
However, I don't think the wrapper will work out of the box.
Regards
JB
On Thu, Mar 7, 2024 at 5:25 PM jose.garn...@toshibagcs.com
wrote:
>
> Hi Karaf team,
>
>
>
> Do you kno
how to upgrade just PAxweb/Jetty in the 4.3.10 version?
> We are already in prod and I cannot upgrade to a new Karaf version .
>
> Regards
> Chandan
>
> On Fri, Mar 1, 2024 at 12:41 PM Jean-Baptiste Onofré
> wrote:
>>
>> Hi
>>
>> You can create you
Hi
You can create your own custom Karaf distribution upgrading PaxWeb/Jetty.
Or you can update to the latest Karaf version.
Regards
JB
On Tue, Feb 27, 2024 at 12:57 PM Chandan Singh <
mailbox.chandansi...@gmail.com> wrote:
> Is there any way we can upgrade the jetty version in Karaf 4.3.10 to
Hi Paul
It's not a bug, that's an expected behavior: the JAAS configuration
created by the commands is stored "in memory".
If you want to persist, you have to use blueprint jaas namespace (in
the deploy folder for instance).
I plan to remove this "requirement" for Karaf 4.5.x using another
storag
Hi Martin
I think we already have a Jira about that. Let me find it.
I will reproduce and fix that.
Thanks,
Regards
JB
On Wed, Jan 24, 2024 at 2:25 PM Martin Lichtin via user
wrote:
>
> Hi all, I noticed a change in SSH server session close behavior, as I
> upgraded from 4.3.10 to 4.4.5.
> Doi
.
>
> Le mar. 16 janv. 2024 à 10:29, Jean-Baptiste Onofré a
> écrit :
> >
> > Hi
> >
> > I guess you missed my message on the Camel dev mailing list.
> > If today Camel 4 doesn't support OSGi/Karaf anymore, I'm working to re-add
> >
Hi
I guess you missed my message on the Camel dev mailing list.
If today Camel 4 doesn't support OSGi/Karaf anymore, I'm working to re-add it.
I'm working on the branch:
https://github.com/jbonofre/camel-karaf/tree/REFACTORE
So, please, give me some time, and we will have Camel 4 working on Kara
>
>
>
>
> And this is the error I'm facing while running karaf.
> org.apache.felix.resolver.reason.ReasonException: Unable to resolve root:
> missing requirement [root] osgi.identity;
> osgi.identity=7db4b9c9-5d8b-4144-a2b3-2162c2867296; type=karaf.feature;
> version="
Hi
By default, the authentication (user) is disabled in Karaf standard
distribution. Did you uncommment the karaf user in
etc/users.properties ?
Regards
JB
On Sat, Jan 13, 2024 at 1:17 AM jose.garn...@toshibagcs.com
wrote:
>
> I am trying to deploy a bundle using the Karaf maven plugin to my lo
Hi Cédric,
You have the documentation about custom distributions:
https://karaf.apache.org/manual/latest/#_custom_distributions
FYI, the karaf distribution is built this way:
https://github.com/apache/karaf/tree/main/assemblies/apache-karaf
So you can mimic the Karaf distribution to match your ne
The Apache Karaf team is pleased to announce the Apache Karaf OSGi
Runtime 4.4.5 release.
Apache Karaf runtime 4.4.5 is a maintenance release, bringing a lot of
dependency updates and fixes, especially:
-i solate config shell commands in a dedicated bundle to avoid refresh
and race condition at st
Hi,
yes, the docker image is arm based. I'm adding multi-arch image
support (to have x86 images as well).
I will upload new images soon.
Regards
JB
On Mon, Jan 8, 2024 at 7:36 PM Steinar Bang wrote:
>
> >>>>> Jean-Baptiste Onofré :
>
> > Hi Steinar
&g
your assistance.
>
> Best regards,
>
> Yunji Lee
>
>
>
>
> From: Jean-Baptiste Onofré
> Sent: Wednesday, December 13, 2023 8:36 AM
> To: user@karaf.apache.org
> Subject: Re: Karaf version with Jdk 21
>
> CAUTION: Thi
Hi Steinar
Let me check about the image type.
Regards
JB
On Fri, Dec 22, 2023 at 5:44 PM Steinar Bang wrote:
>
> > Steinar Bang :
> [snip!]
> > Or try out the, completely different, docker-maven-plugin that comes up
> > first on google searches?
> > https://github.com/fabric8io/docker-mave
Hi Yunji
I'm preparing 4.4.5 right now, but a better JDK 21 support (but not
yet complete due to third parties like Aries *).
About Karaf 4.5.0, I plan to submit it to release just after Christmas.
Regards
JB
On Mon, Dec 11, 2023 at 5:03 PM yunji@toshibagcs.com
wrote:
>
> Hello good day,
>
Hi,
You can use a ConfigListener, similar to what we do in Cellar Config:
https://github.com/apache/karaf-cellar/blob/main/config/src/main/java/org/apache/karaf/cellar/config/LocalConfigurationListener.java
Regards
JB
On Thu, Nov 30, 2023 at 9:19 AM Ephemeris Lappis
wrote:
>
> Hello.
>
> To ma
le to use Karaf 4.3.x or 4.4.x with
> Java 8?
> I am curious if there is a version that supports both Java 8 and 17.
>
> Appreciate your assistance.
> Regards,
> Yunji Lee
> ------
> *From:* Jean-Baptiste Onofré
> *Sent:* Wednesday, November 15,
Hi Yunji
Karaf 4.2.x only supports Java up to 11 (mostly due to the third parties).
If you need JDK17, you have to upgrade to Karaf 4.3.x or 4.4.x (even
better).
Karaf 4.5.0 will be released soon with additional JDK 20 & 21 support.
Regards
JB
On Mon, Nov 13, 2023 at 7:32 PM yunji@toshibag
Hi,
Do you want to watch remote repositories ?
Currently, Karaf is only to watch local repository. We have a Jira about that.
Regards
JB
On Thu, Nov 2, 2023 at 2:55 PM Pavel Perikov wrote:
>
> I’d like to comment on what my goal is.
>
> I’d like to have a bunch of Karaf instances running in a
hours ago, so I'm releasing new Pax Web today.
> > But I found new version of Log4j2 (2.21.0) and I'm releasing Pax Logging
> > first.
> >
> > kind regards
> > Grzegorz Grzybek
> >
> > śr., 18 paź 2023 o 07:43 Jean-Baptiste Onofré
> > napisał
Hey guys
As we have new pax web releases now, I’m resuming fixes and upgrade in
preparation for releases.
Regards
JB
Le dim. 1 oct. 2023 à 18:39, Jean-Baptiste Onofré a
écrit :
> Hi Robert
>
> Sure, I will (I have other stuff to include anyway :)).
>
> Regards
> JB
>
>
Hi Luis
Let me try to reproduce. It seems Hibernate is not able to retrieve
the meta from the database (especially for the dialect and so). The
database is h2 (via pax-jdbc-h2) in the example.
It could be related to h2 wrapping in pax-jdbc.
Regards
JB
On Mon, Oct 9, 2023 at 11:20 PM Luis Lozano
b,
>>
>> I was sick and on vacation, do you have a link to a running example? Maybe I
>> can see my mistake, directly.
>>
>> br,
>> Matthias
>>
>> Am So., 16. Juli 2023 um 14:30 Uhr schrieb Matthias Leinweber
>> :
>>>
>>
my Galaxy
> Original message ----From: Jean-Baptiste Onofré
> Date: 10/1/23 07:33 (GMT+01:00) To: dev
> , user Subject: [UPDATE] Karaf
> WebConsole has issues with Karaf 4.4.4 Hi guys,I created
> https://issues.apache.org/jira/browse/KARAF-7769Since the Felix WebCons
Hi guys,
I created https://issues.apache.org/jira/browse/KARAF-7769
Since the Felix WebConsole update, the Karaf WebConsole plugins
(features, gogo, ...) don't load correctly.
I'm fixing that and I will quickly submit Karaf 4.4.5 to vote.
Sorry for the inconvenience;
Regards
JB
log output at least on WARN level would be helpful.
>
> Thanks & Regards
> Jochen
>
>
>
> Am 21. September 2023 10:41:19 MESZ schrieb "Jean-Baptiste Onofré"
> :
>>
>> Hi,
>>
>> I think you have two options:
>> - you can blacklis
The Karaf team is pleased to announce Apache Karaf OSGi runtime 4.3.10 release.
This is a maintenance release, bringing fixes, new features and
dependency updates:
- fix race condition between the FeaturesService and FeatureDeploymentListener
- fix --patch-module on Instance startup
- add exec:gro
Hi,
I think you have two options:
- you can blacklist from the features.
- you can override the features
Generally speaking, it would be great that third parties features
leverage the Karaf spec features to avoid such kind of issue.
I will do a pass (it's weird that our unit tests passed without
Hi John,
IMHO, Camel 4 dropped OSGi support because we lack contributors and
it's very hard to "maintain" the dependencies in the OSGi way. I plan
to work on Camel 4 OSGi support but I can't take any commitment
because I'm doing it in my spare time only :)
I agree with Greg's points anyway.
Rega
Hi Andre
Thanks for the update, we gonna fix that.
Regards
JB
On Tue, Sep 19, 2023 at 2:52 PM Andre Schlegel-Tylla
wrote:
>
> I have created an issue for pax-web
> https://github.com/ops4j/org.ops4j.pax.web/issues/1895
>
> Without this feature we can't use the RewriteHandler.
>
> regards
> And
Hi,
If you talk about the "pure" spring deployer, it's still there:
https://github.com/apache/karaf/tree/main/deployer/spring (and you can
install it via feature).
On the other hand, the Spring DM "deployer" doesn't exist anymore as
it has been replaced by Blueprint.
Regards
JB
On Tue, Sep 19,
The Karaf team is pleased to announce Apache Karaf OSGi runtime 4.4.4 release.
This is a a maintenance release, bringing a lot of dependency updates
and fixes, especially:
- fix race condition between the FeatureService and FeatureDeploymentListener
- fix --patch-module on Instance startup
- add e
Hi Paul,
Yes, that's the idea: having a central/shared registry gathering beans
from OSGi, Spring Boot, CDI, whatever.
The "dynamic" approach (adding/removing applications managed by a app
manager like Spring Boot, OSGi, ...) is also a target.
To be honest, currently, Minho is not moving forward
an earlier
> 4.3.x and would like to know what moving to 4.3.10 will give us. Thanks!
>
> On Wed, Sep 6, 2023 at 2:38 AM Jean-Baptiste Onofré wrote:
>>
>> Hi,
>>
>> Yes, Karaf 4.3.x supports Java 17. I recommend to wait Karaf 4.3.10
>> (currently in pre
Hi,
Yes, Karaf 4.3.x supports Java 17. I recommend to wait Karaf 4.3.10
(currently in preparation) that includes few improvements for JDK17+.
Regards
JB
On Tue, Sep 5, 2023 at 2:09 PM Chandan Singh
wrote:
>
> Hi Team ,
>
> Can anyone please confirm if Karaf 4.3.7 supports Java 17 . We are
>
Hi Jérémie
I'm working on 4.4.x and 4.3.x next releases. I think I will be ready
by the end of next week, so with the vote period, hopefully 4.3.10
should be available in 2 or 3 weeks.
Regards
JB
On Tue, Aug 22, 2023 at 5:03 PM Jérémie wrote:
>
> Hello,
>
> Is there an ETA for a release of Kara
Hi,
It sounds like a change in exports command between Karaf 2 & 3.
Can you please create a ticket ? I will re-add the option on the shell
command (and probably corresponding MBean).
Thanks !
Regards
JB
On Tue, Aug 15, 2023 at 9:44 PM Anthony Wood wrote:
>
> Hi Paul,
>
> I am looking for a way
Hi Jaap
Can you please create a ticket on issue.apache.org ? We can add some
utils methods in the JAAS module.
Thanks !
Regards
JB
On Mon, Aug 21, 2023 at 8:17 PM f...@gordijn.org wrote:
>
> Hi Matt,
>
>
>
> Can you enlighten me?
>
> What is a JIRA?
>
>
>
> I know Jira from Atlassian very well,
Hi,
Yes, you can take a look on https://karaf.apache.org/community.html in
the "Commercial Support" section.
Yupiik provides training for instance about Karaf.
Regards
JB
On Wed, Aug 2, 2023 at 6:28 PM jose.garnica.lomeli
wrote:
>
> Do you know if exists any official Karaf training offered for
Hi
Do you have the jasypt feature installed ?
Regards
JB
On Fri, Jul 21, 2023 at 10:35 AM Patange, Sneha via user
wrote:
>
> Hello Team,
>
> I am using Karaf 4.4.3 version for my application. My
> application is java(17) based which is using the karaf osgi environment for
> d
Hi Matthias
Using private package, yes I'm using it with Cellar. Can you share the
exception and eventually the test case ? I will reproduce and improve
this.
Regards
JB
On Fri, Jul 14, 2023 at 9:20 AM Matthias Leinweber
wrote:
>
> Hello Karaf User,
>
> I tried to get camel-kubernetes component
Hi,
I would need the full trace but it seems the problem is not about the
import/export packages, but more about a service requirement.
It seems your bundle MANIFEST contains a required service
(JaxRsEventAdapter) but no bundle provides this capability.
I would suggest to check your headers (and
Hi,
You can provide Bundle-SymbolicName on the wrap URL (provided by
features or manually).
Instead of using wrap, you have basically two options:
1. You create a "real" OSGi bundle for the dependencies (or you ask
ServiceMix to do so)
2. You embed the dependency as private package in your bundle
Hi,
I guess you didn't follow the latest discussion.
Karaf5 (as the initial intention) changed to Karaf Minho:
https://github.com/apache/karaf-minho
The latest fixes/improvements has been made on Minho (Karaf "runtime"
stays the OSGi runtime).
Can you please try with Minho ?
Regards
JB
On Mon
Is it clearer ?
>
> Thanks.
>
> Regards.
>
> Le jeu. 29 juin 2023 à 14:04, Jean-Baptiste Onofré a
> écrit :
> >
> > Hi,
> >
> > What's the flag "x" ? :)
> >
> > Can you please elaborate a bit ?
> >
> > Thanks,
&
Hi Ash,
What kind of datasource are you using ?
Regards
JB
On Wed, Jun 28, 2023 at 7:58 PM Ash Williams wrote:
> Hi,
>
>
>
> We have an issue where sql statements executed by hibernate are being
> immediately committed, despite the fact that the entity manager is managed
> by a (local) transac
Hi Steinar,
do you use the default etc/org.ops4j.pax.maven.url.cfg ?
Regards
JB
On Wed, Jun 28, 2023 at 8:56 PM Steinar Bang wrote:
>
> I am working on version 1.15.8-SNAPSHOT of authservice:
> https://github.com/steinarb/authservice
>
> My problem with testing release 1.15.8-SNAPSHOT is that
Hi,
What's the flag "x" ? :)
Can you please elaborate a bit ?
Thanks,
Regards
JB
On Wed, Jun 28, 2023 at 3:49 PM Ephemeris Lappis
wrote:
>
> Hello.
>
> If I'm not wrong, it seems that Karaf (4.4.3 in our last works)
> ignores new files copied into the folder "etc" if these files do not
> have
config .cfg.json all will have the same pid.
>
> Jakub
>
> On Wed, Jun 14, 2023 at 7:30 AM Jean-Baptiste Onofré
> wrote:
> >
> > Hi
> >
> > Yes, by default the suffix is .cfg.json
> > (https://github.com/apache/karaf/blob/main/config/src/main/java/org/a
Hi
it depends what you do in your activator. If the activator doesn't
start by default, you can check a config in the activator and start or
not.
Regards
JB
On Mon, Jun 12, 2023 at 6:00 PM jose.garnica.lomeli
wrote:
>
> Hello everyone,
>
> Currently I have some bundles in my karaf solution star
Hi
Yes, by default the suffix is .cfg.json
(https://github.com/apache/karaf/blob/main/config/src/main/java/org/apache/karaf/config/core/impl/JsonConfigInstaller.java#L49).
You can override the suffix by using karaf.json.config.extension
system property (in the etc/config.properties for instance)
Hi
In blueprint, a bean () is searched inside the blueprint container.
If you want to use a service declared outside of the blueprint
container (DS in your case), you have to use : it will
create a bean proxying the OSGi service available in the OSGi registry
(registered with OSGi "classic" code,
Hi,
As pax-exam can fork the JVM to start Karaf, you need remote debugger.
Is it what you are doing ?
Regards
JB
On Sat, Jun 3, 2023 at 4:41 PM Steinar Bang wrote:
>
> Platform: debian 11.7 "bullseye", amd64
> openjdk-17-jdk:amd64 17.0.6+10-1~deb11u1 (ie. java 17)
> karaf 4.
Hi,
you have the KarService where you can control Kar provisioning.
Regards
JB
On Wed, May 31, 2023 at 5:57 PM jose.garnica.lomeli
wrote:
>
> Hi everyone,
>
> In my current solution I have a maven submodule providing KAR in my custom
> Karaf distribution
>
>
>
> com.company.mysolution
> mysol
Good catch.
I remember we investigated some race condition issues with Greg.
Let me check if the name matches.
Regards
JB
On Wed, May 31, 2023 at 4:45 PM Jesse White wrote:
>
> Good find Ben, and thanks Grzegorz.
>
> Reverting that commit does solve the problem, so it must be related.
>
> I al
Sorry I missed the answer from Greg :)
I second obviously :)
Regards
JB
On Wed, May 31, 2023 at 1:55 PM Grzegorz Grzybek wrote:
>
> Hello
>
> Initially (and more precisely 1-2 years ago) when the javax → jakarta
> migration started to get momentum (partially because of Spring Boot 3 /
> Sprin
Hi Jochen,
That's a fair question.
OSGi group is working on the OSGi version of the spec as part of the
cmpn scope. In the past, we also wrapped some specs in ServiceMix
Specs bundle.
So, even if it's long process, there are several works around the
specs that will help CXF, Vaadin, etc.
Regard
Hi,
you can use kar:uninstall which is basically doing feature:repo-remove -u.
Regards
JB
On Sat, May 13, 2023 at 8:44 PM jose.garnica.lomeli
wrote:
>
> I have a karaf application Where is deployed a kar file and everything works
> fine, I would like to know what is the best way to uninstall t
the generate mojo as some point."
>
> Please do not remove it, it is most useful when using Vaadin which pulls in
> many bundles.
>
> Paul Fraser
>
> On 12/05/2023 3:00 am, Jean-Baptiste Onofré wrote:
> > Hi Ryan
> >
> > IMHO, it's always better to crea
Hi,
The best option is probably to use directly features instead of kar.
For kar, you can use the deploy folder or directly the kar service.
So, IMHO:
1. You app should provide a features repo XML and upload artifacts on a repo
2. You can create a custom karaf distro including your features repo
Hi Ryan
IMHO, it's always better to create the features XML by hand (and verify).
I'm thinking about removing the generate mojo as some point.
Regards
JB
On Tue, May 9, 2023 at 3:58 PM Ryan Moquin wrote:
>
> I've been getting the same error as mentioned in KARAF-5999
> (https://issues.apache.
Hi,
Sorry, I'm traveling this week and I have limited time to answer. I
will reply during the weekend.
Regards
JB
On Tue, Apr 25, 2023 at 8:08 AM Ephemeris Lappis
wrote:
>
> Hello.
>
> I'm trying to configure remote JMX access to Karaf instances running
> inside containers.
>
> I've found a wor
No worries, I will create one for you.
Regards
JB
On Mon, Apr 3, 2023 at 8:32 AM dieder wrote:
>
> Hi,
>
> I'd love to create a Jira ticket, but I cannot seem to get a Jira
> account, so I cannot do that.
>
> kind regards
>Dieder Timmers
>
> Jean-Baptiste
stening
> loopback shutdown port. Shouldn't we change the default configuration to
> use the PID. I've tested this and it works correctly if I remove the
> karaf.shutdown.port.file property.
>
> kind regards
>Dieder Timmers
>
>
>
> Jean-Baptiste Onofré schreef op
Hi,
some info:
1. for security reason, the command loopback port has been disabled
while ago. It now use the PID.
2. which version are you using?
Regards
JB
On Mon, Mar 27, 2023 at 11:50 AM dieder wrote:
>
> Hi All,
>
> Recently I restarted using Karaf. We got an old project and started
> upgra
Yes, it sounds good to me :)
The purpose of providing KarafTestSupport is to simplify the
dependency (a kind of bom) and use.
Regards
JB
On Fri, Mar 24, 2023 at 10:12 PM Steinar Bang wrote:
>
> > Steinar Bang :
>
> > No, provisioning once with @Configuration will be fine, if that
> > actual
s on first boot if containing folder is
> renamed
>
>
>
> *CAUTION:* This email originated from outside of Gaston Schul. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe.
>
>
>
>
>
> For what it's wo
Hi Steinar,
Like this one:
https://github.com/apache/karaf/blob/main/itests/test/src/test/java/org/apache/karaf/itests/DiagnosticTest.java
For example, in this class we have several tests using a single Karaf
instance (depending of the @ExamReactorStrategy(PerClass.class)
annotation, PerClass me
ild does not display this behavior
> btw.
>
>
>
> *Van:* Jean-Baptiste Onofré
> *Verzonden:* woensdag 22 maart 2023 09:44
> *Aan:* user@karaf.apache.org
> *Onderwerp:* Re: Custom Karaf hangs on first boot if containing folder is
> renamed
>
>
>
> * CAUTION:* This ema
1 - 100 of 1877 matches
Mail list logo