Re: [VOTE] Apache Karaf OSGi runtime 4.4.6 release

+1 (Non binding) - Downloaded distro - Installed all of my apps https://github.com/steinarb/myapps?tab=readme-ov-file#installasjon - Smoketested the installed apps - saw no issues in install or smoketest Platform: debian 12.5 "bookworm", amd64, java 17

Re: [PROPOSAL] Apache Karaf 4.5.x with Java 17+

> Jean-Baptiste Onofré : > If it's OK for you, I will update Jenkinsfile to use Java 17 by > default on main (instead of Java 11 today), and update the resources > to target Java 17. +1 from me.

Re: [VOTE] Apache Karaf OSGi runtime 4.4.5 release

+1 (non binding) Smoketested and found OK with my set of applications: https://github.com/steinarb/myapps Platform tested on: debian 12.4 "bookworm", amd64, java17 What I did to test: - Download and unpack the 4.4.5 tar-ball - Copy all org.ops4j.datasource-*.cfg files from the etc of a

Re: Releases preparation

> Jean-Baptiste Onofré : > You might have seen I was pretty quiet recently. We have been hit by > Ciaran storm. I don’t have electricity and Internet connection at > home. As we have important damages on the house, we decided to rent a > new house for a few days. Wow! I've seen the news but

Re: The meaning of karaf-bom

> Jean-Baptiste Onofré : > Not really imho : each project does the way it considers the best. > For instance, quarkus is using a bop approach similar to Karaf: it exposes > all dependencies in the BOM as a guarantee about the versions working fine. > The idea in Karaf bom is to clearly

Re: The meaning of karaf-bom

And FWIW what I expected from the karaf BOM was that I would get build dependency versions from whatever that version of karaf pulls in as runtime dependencies. That was what I requested, when I noticed that a lot of my dependencies were ancient compared to what the current version of karaf was

Re: The meaning of karaf-bom

> Steven Huypens : > Please keep in mind that starting from Maven 4.0, a new specific BOM > packaging > > has been introduced. I have not looked into it, but it might be worth >

Re: The meaning of karaf-bom

>>>>> Steinar Bang : > For one of my projects I ended up restructuring the entire project, > moving the current top pom down one level and create a new top level > with two maven modules: a BOM and the project proper > https://github.com/steinarb/authservice : >

Re: The meaning of karaf-bom

> Robert Varga : > One thing that strikes me is "Bill of Materials" as perceived by karaf-bom. > As it currently stands, karaf-bom includes all declarations of > karaf.git/pom.xml. > As I understand the bill-of-materials concept under Maven, it should > only list artifacts provided by a

Re: [VOTE] Apache Karaf OSGi runtime 4.4.4 release

Works for me. + 1 non-binding What I did to test: - Download the 4.4.4 tarball and unpack into /tmp/apache-karaf-4.4.4 on a debian 12.1 "bookworm" amd64 computer - Edit /tmp/apache-karaf-4.4.4/etc/org.ops4j.pax.url.mvn.cfg file to add

Re: Happy new year 2023!

> Jean-Baptiste Onofré : > Hi everyone, > On behalf of the Apache Karaf team, I wish you all a very happy new year 2023! Happy new, year to JB and the rest of the Apache Karaf team!

Re: [PROPOSAL] Create new Apache project proposal with Minho

> Jean-Baptiste Onofré : > I would call for a vote to remove Minho from Karaf and create a > project proposal based on it (and a couple of additional features). > Thoughts ? +1 on having a vote (or have you already called the vote? Then +1 (non-binding) from me, in favour of the split)

Re: [DISCUSS] Accepting K5 in the Karaf ecosystem

> Eric Lilja : > Because it's shedding its OSGi core, making it optional. It's a different > product stack. What I meant: K5 is something different so call it something different, but leave the karaf 4.x line with the name "karaf". (And in a different place in the thread it seems like this

Re: [DISCUSS] Accepting K5 in the Karaf ecosystem

> Łukasz Dywicki : > Why rename karaf if it is what it was since begining? I agree!

Re: Stack overflow in gogo shell on second "feature:install"

>>>>> Steinar Bang : > I think this may be (as JB hinted at), a problem with my features, > rather than a bug in karaf. > I think the problem is with this feature: > > https://github.com/steinarb/oldalbum/blob/master/oldalbum.roleadder.test/src/main/fe

Re: Stack overflow in gogo shell on second "feature:install"

I think this may be (as JB hinted at), a problem with my features, rather than a bug in karaf. I think the problem is with this feature: https://github.com/steinarb/oldalbum/blob/master/oldalbum.roleadder.test/src/main/feature/feature.xml#L3 created in this commit:

Re: Stack overflow in gogo shell on second "feature:install"

>>>>> Steinar Bang : > Maybe I can try a remote debug into karaf and figure out what is > attempted loaded that way...? I've done remote debugging of the second call to bundle:install. One thing I see, is that in the call to Deployer.handlrePrerequisites() on line 394 (in t

Re: Stack overflow in gogo shell on second "feature:install"

> Jean-Baptiste Onofré : > Thanks, > I will take a look on your project/features asap (I will travel > tomorrow and Monday, but I should have time mid week). It seems to affect all of my projects and happens on the second feature:install. Digging into it feels a bit like looking for a

Re: Stack overflow in gogo shell on second "feature:install"

> Jean-Baptiste Onofré : > Hi, > It looks related to the resolver: it seems you have an infinite loop > in requirements check for your feature. Ok, so you're saying the problem is in my features and not in the resolver? > Do you have something special in terms of req/cap in your feature

Stack overflow in gogo shell on second "feature:install"

Platform: karaf 4.3.7, java 11, debian 11.3 "bullseye" When I run the first "feature:install" everything works fine. But when I try to "feature:install" for a different feature, felix gogo shell gets a stack overflow: https://gist.github.com/steinarb/cfbb1fad2795a93c0eda55951b85ab44 The stack

Re: [ANN] Apache Karaf runtime 4.3.6 has been released

> Jean-Baptiste Onofre : > The Apache Karaf team is pleased so announce Apache Karaf runtime 4.3.6 > release. > This release is an important release on the Karaf 4.3.x series containing: > - upgrade to Pax Logging 2.0.14 with log4j 2.17.1 (fixing CVE-2021-44832) > - prepare JDK 18 support >

Re: [VOTE] Apache Karaf runtime 4.3.6 release

+1 (non-binding) All of my karaf apps loaded without issues, and seems to run normally when smoketesting them. Tested on java 11 on debian 11.2 "bullseye", amd64

Re: [RESULT][VOTE] Apache Karaf runtime 4.3.5 release

>>>>> Jean-Baptiste Onofre : > Hi, > This vote passed with the following result: > +1 (binding): Grzegorz Grzybek, François Papon, Achim Nierbeck, Freeman Fang, > Jamie Goodyear, JB Onofré > +1 (non binding): Romain Manni-Bucau, Steinar Bang, Matt Pavlovich, L

Re: [RESULT][VOTE] Apache Karaf runtime 4.3.4 release (take #3)

>>>>> Jean-Baptiste Onofre : > Hi, > This vote passed with the following result: > +1 (binding): François Papon, Achim Nierbeck, Grzegorz Grzybek, Freeman Fang, > Jamie Goodyear, JB Onofré > +1 (non binding): Lukas Roedl, Romain Manni-Bucau, Matt Pavlovich, Robert

Re: Merry Christmas and Happy New Year

Merry Christmas, JB! And thanks for your great work! :-)

Re: [VOTE] Apache Karaf runtime 4.3.5 release

> Jean-Baptiste Onofré : > Hi everyone, > I submit Apache Karaf runtime 4.3.5 to your vote. > This release includes Pax Logging 2.0.13 update: > - with logback 1.2.9 upgrade, fixing CVE-2021-42550 > - with log4j 2.17.0 upgrade, fixing CVE-2021-45105 All of my karaf apps installed without a

Re: [VOTE] Apache Karaf runtime 4.3.4 release (take #3)

I have installed all of my active karaf applications on this 4.3.4 version as well. No error messages on install, normal messages to the karaf.log, applications seems to run. +1 (non-bindingn)

Re: [VOTE] Apache Karaf runtime 4.3.4 release (take #2)

> Jean-Baptiste Onofré : > Hi everyone, > I submit Apache Karaf runtime 4.3.4 to your vote (take #2). [snip!] > Please vote to approve this release: > [X] +1 Approve the release > [ ] -1 Don't approve the release (please provide specific comments) > This vote will be open for at least 72

Re: [ANN][CVE-2021-44228] Pax Logging 2.0.11 and 1.11.10 released

> Grzegorz Grzybek : > Hello > Pax Logging 2.0.11 and 1.11.10 have been released with CVE-2021-44228 fix. > *Log4j2 has been updated to version 2.15.0.* Great! Thanks!

Re: [CANCEL][VOTE] Apache Karaf runtime 4.3.4 release

> Jean-Baptiste Onofre : > Hi guys; > I cancel this vote to: > 1. Upgrade to pax-logging 2.0.11 which includes important log4j2 CVE fix +1 on that! (I just dropped by today to check if there were any discissions on karaf and log4j...)

Re: Main updated to 4.4.0-SNAPSHOT and karaf-4.3.x branch

> Jean-Baptiste Onofre : > If there’s no objection, I would like to push: > - create karaf-4.3.x branch with the current main HEAD > - update main branch with K44 branch > Thoughts ? LGTM! (ie. "Looks Good To Me!") :-)

Re: Plan to release Pax Web 8 + some information

+1

Re: [VOTE] Apache Karaf runtime 4.3.3 release

> Jean-Baptiste Onofré : > Please vote to approve this release: > [ ] +1 Approve the release > [ ] -1 Don't approve the release (please provide specific comments) Once I remembered to add the staging maven repository, my karaf 4.3.2 applications loaded as normal and seems to be running

Re: [VOTE] Apache Karaf runtime 4.3.3 release

>>>>> Steinar Bang : > Come to think of it: I've been through this before: I need to add a > maven repo Yeah! That worked a lot better: karaf@root()> config:edit org.ops4j.pax.url.mvn karaf@root()> config:property-append org.ops4j.pax.url.mvn.repositories "

Re: [VOTE] Apache Karaf runtime 4.3.3 release

Come to think of it: I've been through this before: I need to add a maven repo

Re: [VOTE] Apache Karaf runtime 4.3.3 release

I have problems installing apps from features. Platform: debian 11.0 "bullseye", amd64 openjdk 11.0.12 karaf 4.3.3 from https://dist.apache.org/repos/dist/dev/karaf/4.3.3/apache-karaf-4.3.3.tar.gz I get the following stack trace on installing features:

Re: Nice if OSGi and OSGi compendium versions were part of the karaf BoM

But pax-jdbc isn't in https://github.com/apache/karaf/blob/main/bom/pom.xml Should it be?

Re: Nice if OSGi and OSGi compendium versions were part of the karaf BoM

>>>>> Steinar Bang : >> https://github.com/apache/karaf/blob/main/bom/pom.xml#L525 >> <https://github.com/apache/karaf/blob/main/bom/pom.xml#L525> Ok. This works for all of the annotations, and the LogService. No need for me to reference these directly. O

Re: Nice if OSGi and OSGi compendium versions were part of the karaf BoM

> Jean-Baptiste Onofre : > Hi Steinar, > I just checked and both osgi.core and osgi.cmpn are part of the Karaf BoM (as > I thought ;) ): > https://github.com/apache/karaf/blob/main/bom/pom.xml#L39 > Hm... that one should be

Re: Nice if OSGi and OSGi compendium versions were part of the karaf BoM

> JB Onofré : > Good point and I agree. > Does it work for you if I add this to karaf 4.3.3 and 4.2.12 ? That would be excellent! Thanks! :-) > Thanks for the proposal. My pleasure! :-)

Nice if OSGi and OSGi compendium versions were part of the karaf BoM

I need the osgi framework and the OSGi LogService defintion and the SCR annotations for all project (and now: the OSGi 7 web whiteboard annotations) for all of my karaf web app projects. It would be nice if I could pick the versions for all of those from the karaf BoM (where I eg. get pax-web

Re: pax exam tests started failing when I bumped karaf version to 4.3.2

Thanks, Eric! I'll study your config builders. However, what I ended up doing in this case, was very simple: I created a dummy users.properties file, and dropped it into the src/test/resources/etc/ directory of the maven project for the pax exam test:

Re: pax exam tests started failing when I bumped karaf version to 4.3.2

>>>>> Steinar Bang : >> A simple workaround is to include your own users.properties in the pax-exam >> option. > Thanks! I will look into this. I tried this: @Configuration public Option[] config() { final MavenArtifactUrlReference

Re: pax exam tests started failing when I bumped karaf version to 4.3.2

> Jean-Baptiste Onofre : > Hi, > It’s has been discussed on the mailing list already (I don’t remember who > reported this). > The change we did is that etc/users.properties has the karaf user commented > now (for security reason). Right. I noticed yesterday, when rolling the .deb package

pax exam tests started failing when I bumped karaf version to 4.3.2

When I bumped the karaf version (affects the karaf-maven-plugin, the karaf BoM and the pax exam tests in my project builds), then the pax exam tests fail with this message: [ERROR] initializationError(no.priv.bang.authservice.tests.AuthserviceIntegrationTest) Time elapsed: 0.015 s <<< ERROR!

Re: [VOTE] Apache Karaf runtime 4.3.2 release

> Jean-Baptiste Onofre : > Hi, > Can you try to cleanup your ~/.karaf folder (just in case) ? That worked! :-) See the command output trace for the same sequence (tried to exit with something other than my usual Ctrl-d there, but neither quit, nor exit worked...):

Re: [VOTE] Apache Karaf runtime 4.3.2 release

> Jean-Baptiste Onofre : > It seems to work for me (about the commands history). You started karaf from the command line, did some commands, exited karaf, and started karaf from the command line again, and the history was preserved? Could it be something about the exact tar.gz file I

Re: [VOTE] Apache Karaf runtime 4.3.2 release

> Jean-Baptiste Onofre : > Can you describe your test case ? 1. Download the tar.gz of the binary build 2. Unpack into /tmp/apache-karaf-4.3.2/ 3. Do "cd /tmp/apache-karaf-4.3.2/" 4. Start karaf with "bin/karaf debug" 5. From the karaf console add my own maven repo: config:edit

Re: [VOTE] Apache Karaf runtime 4.3.2 release

> JB Onofré : > Hi > I changed the location of the shell history file. It could be related. Let me > check (I tested without problem). I just did a tar xvf in /tmp/ on a debian computer (just a temporary installation to test). Could the location I unzipped in, be the issue?

Re: [VOTE] Apache Karaf runtime 4.3.2 release

> JB Onofré : > By the way do you have the repo in the pax url cfg file ? A different config than org.ops4j.pax.url.mvn? No, org.ops4j.pax.url.mvn was the only one I modified. (and it seemed to be sufficient...?)

Re: [VOTE] Apache Karaf runtime 4.3.2 release

Once I added the staging maven repository to the property org.ops4j.pax.url.mvn.repositories in the config, i.e. config:edit org.ops4j.pax.url.mvn config:property-append org.ops4j.pax.url.mvn.repositories ",

Re: Non-Deterministic startup order

> Jean-Baptiste Onofre : > And just to let you know that I created > https://issues.apache.org/jira/browse/KARAF-7130 > to be able to have a > pluggable startup order strategy (for instance based on symbolic name). A "thumbs-up" on that

Re: Apache Karaf 4.3.2 very soon

> Serge Huber : > Hi JB, > Please pace yourself man, we can wait a little ! Agreed!

Re: Problems making debian package of karaf 4.3.1

> JB Onofré : > Yea it makes sense to use an empty file for 4.3. Actually, I think it makes > sense to do it by default on 4.3. I will create the jira related to that. +1

Re: Problems making debian package of karaf 4.3.1

> JB Onofré : > Hi > That’s normal: karaf 4.2.x uses blacklist so it provides the file, especially > to blacklist 4.3.x features repositories. > Karaf 4.3.x doesn’t use blacklist (as the version is newer). Yes, but that collided with the way I had decided to handle the etc directory: to

Re: Problems making debian package of karaf 4.3.1

I did a diff between the directory contents of the etc directory of the karaf 4.3.1 binary tarball, and the etc directory of the debian package: https://gist.github.com/steinarb/7a8427ac19b355c27598c945b27863f8 One file looked particularily interesting: org.apache.karaf.features.xml which was

Re: Problems making debian package of karaf 4.3.1

Here's the difference in the startup of 4.3.1 and 4.2.11 in karaf.log. As you said, JB, it looks like it doesn't find the startup features...? 4.3.1: 2021-04-03T17:25:45,773 | INFO | CM Configuration Updater (Update: pid=org.ops4j.pax.logging) | EventAdminConfigurationNotifier | 6 -

Re: Problems making debian package of karaf 4.3.1

>>>>> Steinar Bang : > A little more info. > The debian installed karaf starts in /var/lib/karaf/ which looks like > this: Are there any layout changed in the file/directory layout of karaf 4.3.x that might cause this structure to no longer work?

Re: Problems making debian package of karaf 4.3.1

A little more info. The debian installed karaf starts in /var/lib/karaf/ which looks like this: sb@lorenzo:/var/lib/karaf$ ls -al total 36 drwxr-xr-x 7 karaf karaf 4096 Apr 3 17:25 . drwxr-xr-x 77 root root 4096 Nov 15 15:36 .. drwxr-xr-x 2 karaf karaf 4096 Aug 25 2017 .karaf

Re: Problems making debian package of karaf 4.3.1

>>>>> Steinar Bang : >>>>> Jean-Baptiste Onofre : >> Hi Steinar, >> It’s weird: it looks like the boot feature are not startup. >> Do you have the features core bundle in etc/startup.properties ? Yes, at the end of /etc/karaf/startu

Re: Problems making debian package of karaf 4.3.1

> Jean-Baptiste Onofre : > Hi Steinar, > It’s weird: it looks like the boot feature are not startup. > Do you have the features core bundle in etc/startup.properties ? > Did you update etc/org.apache.karaf.features.cfg ? Thanks for the pointers! I will check. It could be that I have

Problems making debian package of karaf 4.3.1

I'm trying to make a debian package of karaf 4.3.1[1]. The resulting deb package so far: 1. Builds without any error messages 2. Installs without any error messages 3. Leaves a running process 4. Leaves very few messages in the logs[6] 5. Does not start an SSH server (I think...? at least

Re: [VOTE] Apache Karaf runtime 4.2.11 release

> Jean-Baptiste Onofre : > Release Notes: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12348692 Yay! The BOM is in place! :-) +1 (non-binding)

Re: Coming releases

> Jean-Baptiste Onofre : > - Apache Karaf 4.3.1 and 4.2.11 should be on vote during next week end. I’m > doing the Jira triage right now. Great news! :-)

Re: Happy new year

Happy new year, to you and all of the Karaf team! Keep up the good work! :-)

Re: Thinking about Karaf 5 modulith runtime

> Jean-Baptiste Onofre : > My thinking now is more to still use OSGi internally (and let people > do OSGi on Karaf if they want) but open the scope to other > framework/approach (spring boot, micro profile, etc). We would embrace > a wider community and expend our use cases. FWIW what drew

Re: Download page is a bit confusing right now

> Jean-Baptiste Onofre : > Hi, > 4.2.10 has been released and available: > https://repo1.maven.org/maven2/org/apache/karaf/apache-karaf/4.2.10/ > Ah, OK. Thanks!

Download page is a bit confusing right now

https://karaf.apache.org/download Latest release is "Karaf Runtime 4.2.10" from June 9 2020. But 4.2.10 never happened if I remember correctly? We were to get 4.2.11 instead (and I haven't seen any announcements for that...?) Also further down under "Schedule", 4.2.9 is listed as the current

Re: Will there be a BOM with the 4.2.10 release?

> Jean-Baptiste Onofre : > Hi Steinar, > Just to let you know that the BOM will be included on 4.3.0 (and 4.2.11) > planned for this week. Thanks for the information! (I got some confusiong Jira notification about this today...:-) )

Re: [HEADS UP] Docker friendly runtime with env variables compliant configuration

> Jean-Baptiste Onofre : > Yes, it’s what I did in the PR ;) Ah, sorry! I searched for it, but didn't find it. Bad at searching, me.

Re: [HEADS UP] Docker friendly runtime with env variables compliant configuration

> Jean-Baptiste Onofre : > Hi, > In this PR: https://github.com/apache/karaf/pull/1206 > > I have implemented the interpolation. > It means that you can use the following for instance: > export >

Re: [HEADS UP] Docker friendly runtime with env variables compliant configuration

> Jean-Baptiste Onofre : > Yeah, that’s pretty easy to do on the KarafConfigurationPlugin (interpolating > the value). > I can add this on the PR ;) Cool!

Re: [HEADS UP] Docker friendly runtime with env variables compliant configuration

> Jean-Baptiste Onofre : > Thoughts ? Not directly environment variable releated, but one thing I would like to see, is a simple way to add one or more feature repositories, and to add one or more features to the boot set. That's what I've done in my karaf based docker images. I've done it

Re: Will there be a BOM with the 4.2.10 release?

> Jean-Baptiste Onofre : > Hi Steinar, > I set Jira version to 4.2.10. So, yes, a first BOM will be available on > 4.2.10. Great! :-)

Re: Will there be a BOM with the 4.2.10 release?

(I meant 4.2.9 and not 4.3.9. Typo, sorry)

Re: Apache Karaf runtime 4.3.0 - Decision taken

A late and non-binding +1 from me. I'm looking forward to seeing, and using, a 90% complete pax web 7! :-)

Re: karaf 4.2.9 cygwin console seems broken

> Jean-Baptiste Onofre : > Hi, > That’s a "known" issue with latest Cygwin version. > It’s not Karaf directly related. Ok. Good to know! Thanks!

Re: karaf 4.2.9 cygwin console seems broken

> Eric Lilja : > If you start Cygwin (or MinTTY I should say) with the following environment > variable set, does it make a difference? > CYGWIN=disable_pcon Yep, that worked! Thanks! What I did: 1. Set the CYGWIN environment variable using advanced system settings 2. Start a new cygwin

karaf 4.2.9 cygwin console seems broken

When starting karaf 4.2.9 from the cygwin console on windows 10, the karaf prompt is broken. Is this a known issue? Should I make a Jira for the issue? Starting karaf 4.2.9 from cmd.exe on windows 10 works fine so I'm using that for now (copy paste is not as nice as with the cygwin console, but

Re: [HEADS UP] Apache Karaf releases plan

Thanks for the update, JB! Out of curiosity: What's "Features JSON"? Karaf features to pull in JSON support? If so, which parser? Jackson? GSON? Something else...? Thanks! - Steinar

Re: [HEADS UP] Three new features proposal this week

> Matt Pavlovich : > Have you looked at using local-repo? I don't think it matters too much where things are loaded from at karaf boot, as much as what's put into that repo. I.e. I would like to specify a feature I want to add to the start set, and then resolve everything needed to that

Re: [HEADS UP] Three new features proposal this week

> Jean-Baptiste Onofre : > Instead I’m working on: > 1. Improve log message for runtime resolution Yay! +1 :-) > 2. Improve build tool (part of devx) for build time resolution Hm... can this be used to fill up the system directory when creating a docker image on top of the official image?

Re: [HEADS UP] Three new features proposal this week

> Jean-Baptiste Onofre : > The problem is that regular resolver makes sense for "dynamic/standard" > distribution, but very painful for "cloud/light/straight" runtime. > The proposal is to have a lighter version of the resolver to be faster and > predictable. So it's not a replacement?

Re: [HEADS UP] Three new features proposal this week

> Łukasz Dywicki : > On the resolver thingy. > I believe that the main problem we need to address is a format of error > messages spit from our code. > In quite many cases error takes half of the screen. Failure reason is at > the end. Going over spaghetti causation in between is a challenge.

Re: [HEADS UP] Releases plan: Decanter 2.3.0 and Karaf 4.2.9/4.3.0

>>>>> Steinar Bang : > Hi, > Will 4.2.9 contain a fix for the ssh console issues? Ie. the paste issue.

Re: [HEADS UP] Releases plan: Decanter 2.3.0 and Karaf 4.2.9/4.3.0

> Jean-Baptiste Onofre : > Hi Markus, > I’m working on including a fix. That’s why I don’t plan Karaf 4.2.9 at least > during the week end (it gives time to address several issues including the > "paste" one ;) ). One more console issue I've seen, I don't know if it's reported (I didn't

Re: [HEADS UP] Releases plan: Decanter 2.3.0 and Karaf 4.2.9/4.3.0

Hi, Will 4.2.9 contain a fix for the ssh console issues?

Re: Merry Christmas & releases on the way

Merry Christmas JB, to you and the rest of the karaf team! Thanks for continuing to provide us with such good software! :-)

Re: [DISCUSS] Accept HTML on the Apache Karaf mailing lists

>>>>> Steinar Bang : >> Do you agree about allowing HTML emails on the mailing lists ? > (-0.5 I rather you didn't but I don't have a strong objection) HTML in posted message is broken in the mailing list archives: http://mail-archives.apache.org/mod_mbox/karaf-user/20

Re: [DISCUSS] Accept HTML on the Apache Karaf mailing lists

> Jean-Baptiste Onofré : > Do you agree about allowing HTML emails on the mailing lists ? (-0.5 I rather you didn't but I don't have a strong objection)

Re: Hello World!

> Christian Schneider : > Another issue is that especially for dependency injection there are quite a > few alternatives. Every of these come with their own pros and cons. > As a beginner it is difficult to understand and decide how to start. Personally I don't understand why anyone would

Re: Issue in bin/inc on 4.3.0-SNAPSHOT and 4.2.7-SNAPSHOT

> Jean-Baptiste Onofré : > Quick update about the bin/inc issue: it seems to be an environment > issue on one of my machine (I'm suspecting the CRLF git config). > I tested the SNAPSHOT deployed by Jenkins and it's working fine. JB, FWIW, I run with an LF only setup, and this is how I do it:

Re: Are mvn URLs in startup.properties resolved locally or against maven central?

> Jean-Baptiste Onofré : > You are welcome ;) Karaf 4.2.6 have been debian-packaged and deployed to my apt-repo https://steinar.bang.priv.no/2018/01/23/installing-apache-karaf-on-debian/comment-page-1/#comment-14352 Thanks again!

Re: Are mvn URLs in startup.properties resolved locally or against maven central?

>>>>> Steinar Bang : > I'm trying to get my debian APT package of karaf to build for karaf 4.2.6. > https://github.com/steinarb/karaf-debian > > https://steinar.bang.priv.no/2018/01/23/packaging-karaf-with-native-debian-packaging-tools/ > (the last time I built

Are mvn URLs in startup.properties resolved locally or against maven central?

I'm trying to get my debian APT package of karaf to build for karaf 4.2.6. https://github.com/steinarb/karaf-debian https://steinar.bang.priv.no/2018/01/23/packaging-karaf-with-native-debian-packaging-tools/ (the last time I built this package was with version 4.1.7 on december 1 2018) Karaf

Re: karaf iTest results on my machine

>>>>> Steinar Bang : > Most iTests work, but I have 3 tests failing with "error" and one > failing with failure. > The three failing with error, are: > org.apache.karaf.itests.FelixHttpTest.txt:4:Tests run: 1, Failures: 0, > Errors: 1, Skippe

karaf iTest results on my machine (Was: What's the difference between org.osgi.core-6.0.0.jar and felix and/or equinox?)

>>>>> Steinar Bang : > As mentioned in a different thread on the ops4j list, karaf master is > also failing in itest on "mvn clean install" on my development system. [snip!] > But first I will go back to the karaf itests and try to get them to > build on

Re: What's the difference between org.osgi.core-6.0.0.jar and felix and/or equinox?

> Jean-Baptiste Onofré : > To be honest, I don't understand your issue: itest just works fine in > Karaf (in my box, in Jenkins). It could be something in my setup. As mentioned in a different thread on the ops4j list, karaf master is also failing in itest on "mvn clean install" on my

Re: What's the difference between org.osgi.core-6.0.0.jar and felix and/or equinox?

>>>>> Steinar Bang : > Is org.osgi.core-6.0.0.jar a version of the felix framework? No. > Or does org.osgi.core-6.0.0.jar only contain interfaces used by all OSGi > 6 frameworks? Yes. > (but if so: where does karaf find the framework it should use to boot) It

What's the difference between org.osgi.core-6.0.0.jar and felix and/or equinox?

I'm trying to figure out why my pax exam tests are failing on openjdk-11, and am trying to trace the difference between regular karaf startup on openjdk-11 (karaf starts and runs fine on openjdk-11) and pax exam karaf startup on openjdk-11 (which fails for me). I was trying to figure out what

  1   2   >