Re: [DISCUSS] Accepting K5 in the Karaf ecosystem

[Eric Lilja]

On Sat, Oct 8, 2022 at 3:46 PM Steinar Bang  wrote:

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

Because it's shedding its OSGi core, making it optional. It's a different
product stack.

- Eric L

Re: [ANN] Pax Logging 2.1.3 released

[Eric Lilja]

Great, thanks!

Question: Will Pax Exam be updated to use this version, it uses an ancient
version doesn't it?

- Eric L

On Tue, Jul 5, 2022 at 3:18 PM Grzegorz Grzybek 
wrote:

> Hello
>
> I'd like to announce the release of Pax Logging 2.1.3 with just one update:
>
>- Log4j2 2.18.0
>
> Updating to 2.18.0 helped with one CCE problem related to JeroMqAppender.
>
> I'd like to mention that lines 2.0.x and 1.11.x are no longer a priority
> because they include log4j1 "backend".
> And line 1.12.x without log4j1 backend is based on OSGi CMPN R6 which is
> already quite old.
>
> So if you can, please migrate to 2.1.x. If you can't, please let us know ;)
>
> The release notes can be found here:
>
>- 2.1.3:
>https://github.com/ops4j/org.ops4j.pax.logging/milestone/95?closed=1
>
> kind regards
> Grzegorz Grzybek
>

SSH warnings seen in Pax Exam test log after upgrade to 4.3.7

[Eric Lilja]

Hello, I just upgraded Karaf from 4.2.12 to 4.3.7 due to moving from Java
11 to Java 17. Now I can see the following warnings in the log when running
Pax Exam tests:

[INFO] 2022-05-23T15:33:43,050 | WARN  | activator-1-thread-1 | SshUtils
  | 55 - org.apache.karaf.shell.ssh - 4.3.7 |
Configured signature 'sk-ssh-ed25...@openssh.com' not available
[INFO] 2022-05-23T15:33:43,085 | WARN  | activator-1-thread-1 | SshUtils
  | 55 - org.apache.karaf.shell.ssh - 4.3.7 |
Configured signature 'ssh-ed25519' not available
[INFO] 2022-05-23T15:33:43,319 | WARN  | activator-1-thread-1 | SshUtils
  | 55 - org.apache.karaf.shell.ssh - 4.3.7 |
Configured signature 'sk-ssh-ed25...@openssh.com' not available
[INFO] 2022-05-23T15:33:43,320 | WARN  | activator-1-thread-1 | SshUtils
  | 55 - org.apache.karaf.shell.ssh - 4.3.7 |
Configured signature 'ssh-ed25519' not available

If I downgrade to 4.3.6, the warnings disappear. Looking at the changelog
for 4.3.7, I suppose this is caused by KARAF-7363 [1]

How do I make the above warnings disappear? Is it a bug? The tests
work fine, but it's a bit annoying to see these warnings. I'd rather not
silence the logger, that seems wrong..

- Eric L

[1] https://issues.apache.org/jira/browse/KARAF-7363

Re: [DISCUSSION] Move PAX projects to Apache Karaf ?

[Eric Lilja]

Personally, I would love to see this change and the other people in my
organization liked the proposal as well.

- Eric L

On Thu, Feb 24, 2022 at 3:04 PM Jean-Baptiste Onofré 
wrote:

> Hi guys,
>
> Some of you already pinged me to share concerns about PAX projects
> governance. I think it's my duty to share these concerns and discuss
> possible actions.
>
> Apache Karaf is one of the biggest consumers of PAX projects.
>
> However, PAX projects use a "self own" designed governance:
> - for contribution/IP
> - for release
> - for CVE/Security
> - ...
>
> And it could be seen as a major concern for Apache Karaf users, as PAX
> projects are not necessarily "aligned" with Apache Foundation rules.
>
> I would like to start a discussion on both Karaf and OPS4J communities
> to "move" PAX projects as Karaf subproject (like karaf-pax).
> Concretely, it would mean that:
> 1. Karaf PAX projects would use org.apache.karaf.pax namespace
> 2. Karaf PAX releases will have to follow the Apache release process
> (binding votes, 3 days vote period, ...)
> 3. Any active contributor on PAX projects would be invited as Karaf
> committer
>
> Thoughts ?
>
> Regards
> JB
>

Re: Releases schedule

[Eric Lilja]

Ah, that's great news, thanks JB and Freeman for handling that!

- Eric L


On Fri, May 28, 2021 at 6:11 AM Jean-Baptiste Onofre 
wrote:

> Hi Eric,
>
> About Pax Exam, Freeman did the fix already. Let’s move forward on the
> release to include it.
>
> Regards
> JB
>
> > Le 27 mai 2021 à 22:27, Eric Lilja  a écrit :
> >
> > Looking forward to the releases, JB!
> >
> > For 4.2.12, I personally think it's important that the regression that
> made
> > Pax Exam fail if Java version > 8 is fixed first, if it hasn't been
> > already. I wouldn't mind to see 4.3.3 out relatively soon with that fix
> as
> > well.
> >
> > - Eric L
> >
> > On Tue, May 25, 2021 at 8:21 AM Jean-Baptiste Onofre 
> > wrote:
> >
> >> Hi Steven,
> >>
> >> Yup, +1, it’s already planned ;)
> >>
> >> You can expect it for Decanter 2.8.0.
> >>
> >> Regards
> >> JB
> >>
> >>> Le 25 mai 2021 à 08:11, Steven Huypens  a
> >> écrit :
> >>>
> >>> Hi JB,
> >>>
> >>> It would be nice to have
> >> https://issues.apache.org/jira/browse/KARAF-7154
> >>> included in the new decanter release. Let me know if I can help.
> >>>
> >>> Best regards,
> >>> Steven
> >>>
> >>> On Tue, May 25, 2021 at 6:33 AM Jean-Baptiste Onofre 
> >>> wrote:
> >>>
> >>>> Hi guys,
> >>>>
> >>>> Just a quick update about the release schedule:
> >>>>
> >>>> - Karaf runtime 4.2.12 is in preparation. Target date is this week end
> >> for
> >>>> the vote.
> >>>> - Karaf Decanter 2.8.0 is in preparation. Target date is this week end
> >> for
> >>>> the vote as well.
> >>>> - Karaf Cave 4.2.2 should be in preparation soon but I’ve not yet
> >> started.
> >>>> - Karaf Cellar 4.3.0 refactoring started. Target date for a first RC
> is
> >>>> next month.
> >>>>
> >>>> I’m updating website (schedule table) accordingly.
> >>>>
> >>>> If you have specific Jira or comments to include in these releases,
> >> please
> >>>> let me know.
> >>>>
> >>>> Thanks,
> >>>> Regards
> >>>> JB
> >>
> >>
>
>

Re: Releases schedule

[Eric Lilja]

Looking forward to the releases, JB!

For 4.2.12, I personally think it's important that the regression that made
Pax Exam fail if Java version > 8 is fixed first, if it hasn't been
already. I wouldn't mind to see 4.3.3 out relatively soon with that fix as
well.

- Eric L

On Tue, May 25, 2021 at 8:21 AM Jean-Baptiste Onofre 
wrote:

> Hi Steven,
>
> Yup, +1, it’s already planned ;)
>
> You can expect it for Decanter 2.8.0.
>
> Regards
> JB
>
> > Le 25 mai 2021 à 08:11, Steven Huypens  a
> écrit :
> >
> > Hi JB,
> >
> > It would be nice to have
> https://issues.apache.org/jira/browse/KARAF-7154
> > included in the new decanter release. Let me know if I can help.
> >
> > Best regards,
> > Steven
> >
> > On Tue, May 25, 2021 at 6:33 AM Jean-Baptiste Onofre 
> > wrote:
> >
> >> Hi guys,
> >>
> >> Just a quick update about the release schedule:
> >>
> >> - Karaf runtime 4.2.12 is in preparation. Target date is this week end
> for
> >> the vote.
> >> - Karaf Decanter 2.8.0 is in preparation. Target date is this week end
> for
> >> the vote as well.
> >> - Karaf Cave 4.2.2 should be in preparation soon but I’ve not yet
> started.
> >> - Karaf Cellar 4.3.0 refactoring started. Target date for a first RC is
> >> next month.
> >>
> >> I’m updating website (schedule table) accordingly.
> >>
> >> If you have specific Jira or comments to include in these releases,
> please
> >> let me know.
> >>
> >> Thanks,
> >> Regards
> >> JB
>
>

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

[Eric Lilja]

Hi Steinar, for my Pax Exam Karaf tests, I am using a builder-style class I
wrote called KarafConfigurator for building the list of configuration
options.

It has methods for replacing bundled config files with user
supplied versions. Here's an example using startup.properties:

public KarafConfigurator replaceStartupProperties(final URL
newStartupProperties) throws URISyntaxException {
return replaceConfigurationFile(STARTUP_PROPERTIES_FILE_PATH,
newStartupProperties);
}

public KarafConfigurator replaceConfigurationFile(final String path, final
URL newConfigurationFileUrl) throws URISyntaxException {
final File newConfigurationFile = new
File(newConfigurationFileUrl.toURI());

return replaceConfigurationFile(path, newConfigurationFile);
}

public KarafConfigurator replaceConfigurationFile(final String path, final
File newConfigurationFile) {
final Option optionReplaceConfFile =
KarafDistributionOption.replaceConfigurationFile(path,
newConfigurationFile);

options.add(optionReplaceConfFile);

return this;
}

STARTUP_PROPERTIES_FILE_PATH denotes the path inside the Karaf distro to
the startup.properties-file. It's defined as:

private static final String STARTUP_PROPERTIES_FILE_PATH =
"etc/startup.properties";

Notice it's doesn't start with "/"

The user of KarafConfigurator-class would simply call the
replaceStartupProperties()-method. A URL to a replacement-file in
src/test/resources can be obtained simply:

final Class clz = getClass();
final URL resourceUrl = clz.getResource("/startup.properties");

Here it's assumed the file is the user wants to use as a replacement is
called "startup.properties" and is located in src/test/resources (assuming
Maven)

- Eric L

On Sun, May 23, 2021 at 11:42 AM Steinar Bang  wrote:

> > 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 authserviceFeatureRepo = maven()
> .groupId("no.priv.bang.authservice")
> .artifactId("karaf")
> .version("LATEST")
> .type("xml")
> .classifier("features");
> File dummyUsersProperties = new
> File(getClass().getClassLoader().getResource("dummy.users.properties").getFile());
> Option[] options = new Option[] {
> features(authserviceFeatureRepo),
> replaceConfigurationFile("/etc/users.properties",
> dummyUsersProperties)
> };
> return Stream.of(super.config(),
> options).flatMap(Stream::of).toArray(Option[]::new);
> }
>
> But the test still fails almost immediately with
>  org.ops4j.pax.exam.TestContainerException: java.lang.RuntimeException:
> Config resource /etc/users.properties not found
>
> I've tried "users.properties" and "etc/users.properties" as the
> configurationFilePath argument to replaceConfigurationFile(), but it
> didn't make any difference.
>
>

Re: Renaming master branch as main branch

[Eric Lilja]

Ok :(

On Mon, Mar 15, 2021 at 7:49 AM Jean-Baptiste Onofre 
wrote:

> Hi guys,
>
> I created a Jira for infra to rename master branch as main:
>
> https://issues.apache.org/jira/browse/INFRA-21576
>
> Thanks,
> Regards
> JB
>

Re: [VOTE] Apache Karaf runtime 4.2.11 release

[Eric Lilja]

What's the status of this one? Fixed or should move to 4.2.12?
https://issues.apache.org/jira/browse/KARAF-6948

- Eric L

On Tue, Mar 9, 2021 at 9:36 PM  wrote:

> +1 (binding)
>
> regards,
>
> François
> fpa...@apache.org
>
> Le 09/03/2021 à 12:56, Jean-Baptiste Onofre a écrit :
> > Hi everyone,
> >
> > I submit Apache Karaf runtime 4.2.11 to your vote.
> >
> > This release includes bunch of dependency upgrades, fixes, and
> improvements, especially:
> >
> > - fix on SSH stream
> > - fix on log:* commands
> > - improvement on the JMX layer (especially JMXMP)
> > - env/prop interpolation support on the SSH client
> > - add property to disable auto refresh in features service
> > - stronger JAAS encryption algorithms support
> > - updated Spring versions
> > - and much more !
> >
> > Please take a look on Release Notes for details !
> >
> > Release Notes:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12348692
> >
> > Staging Repository:
> > https://repository.apache.org/content/repositories/orgapachekaraf-1154/
> >
> > Staging Dist:
> > https://dist.apache.org/repos/dist/dev/karaf/4.2.11/
> >
> > Git tag:
> > karaf-4.2.11
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Don't approve the release (please provide specific comments)
> >
> > This vote will be open for at least 72 hours.
> >
> > Regards
> > JB
>

Re: Update apache-httpclient to 4.15.3 to address CVE-2020-13956

[Eric Lilja]

Ah, great, thanks JB!

- Eric L

On Fri, Oct 23, 2020 at 6:29 AM Jean-Baptiste Onofre 
wrote:

> Hi Eric,
>
> Yup: https://issues.apache.org/jira/browse/KARAF-6890
>
> Regards
> JB
>
> Le 23 oct. 2020 à 03:19, Eric Lilja  a écrit :
>
> Nice! Great to see! But is there a Jira for this issue for the upcoming
> 4.2.11?
>
> - Eric L
>
> On Thu, Oct 22, 2020 at 7:17 AM Jean-Baptiste Onofre 
> wrote:
>
>> The update has been already merged ;)
>>
>> Thanks
>> Regards
>> JB
>>
>> > Le 21 oct. 2020 à 11:04, Pattan, Sachin  a
>> écrit :
>> >
>> > Dear Colleagues,
>> >
>> > As per https://bugzilla.redhat.com/show_bug.cgi?id=1886587 <
>> https://bugzilla.redhat.com/show_bug.cgi?id=1886587>, http.client
>> librarires below version 4.5.13 have the vulnerability CVE-2020-13956 (
>> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-13956 <
>> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-13956>).
>> >
>> > As Karaf 4.2.x rebundles http.client (4.5.6) classes as seen at
>> https://github.com/apache/karaf/blob/karaf-4.2.10/jaas/modules/pom.xml#L180
>> <
>> https://github.com/apache/karaf/blob/karaf-4.2.10/jaas/modules/pom.xml#L180>.
>> This makes it vulnerable and hence our security scans are detecting it as a
>> vulnerable library. I created the the PR
>> https://github.com/apache/karaf/pull/1243 <
>> https://github.com/apache/karaf/pull/1243> to update httpclient.version
>> to 4.5.13. Please take a look at it whenever it is possible and include it
>> in the upcoming release of Karaf 4.2.x if it fits good.
>> >
>> > Kind regards,
>> >
>> >
>> >
>> > Sachin Pattan
>> > The Tools Team
>> > WDF07  X1.65
>>
>>
>

Re: Update apache-httpclient to 4.15.3 to address CVE-2020-13956

[Eric Lilja]

Nice! Great to see! But is there a Jira for this issue for the upcoming
4.2.11?

- Eric L

On Thu, Oct 22, 2020 at 7:17 AM Jean-Baptiste Onofre 
wrote:

> The update has been already merged ;)
>
> Thanks
> Regards
> JB
>
> > Le 21 oct. 2020 à 11:04, Pattan, Sachin  a écrit
> :
> >
> > Dear Colleagues,
> >
> > As per https://bugzilla.redhat.com/show_bug.cgi?id=1886587 <
> https://bugzilla.redhat.com/show_bug.cgi?id=1886587>, http.client
> librarires below version 4.5.13 have the vulnerability CVE-2020-13956 (
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-13956 <
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-13956>).
> >
> > As Karaf 4.2.x rebundles http.client (4.5.6) classes as seen at
> https://github.com/apache/karaf/blob/karaf-4.2.10/jaas/modules/pom.xml#L180
> <
> https://github.com/apache/karaf/blob/karaf-4.2.10/jaas/modules/pom.xml#L180>.
> This makes it vulnerable and hence our security scans are detecting it as a
> vulnerable library. I created the the PR
> https://github.com/apache/karaf/pull/1243 <
> https://github.com/apache/karaf/pull/1243> to update httpclient.version
> to 4.5.13. Please take a look at it whenever it is possible and include it
> in the upcoming release of Karaf 4.2.x if it fits good.
> >
> > Kind regards,
> >
> >
> >
> > Sachin Pattan
> > The Tools Team
> > WDF07  X1.65
>
>

Re: [VOTE] Apache Karaf 4.2.10 release

[Eric Lilja]

I've done some manual testing using Cygwin (MinTTY) as the terminal under
Windows 10. Things look pretty good, console behaves as it should from the
little testing I did.

I did see a folder being created in an unwanted location to house a log
file, but that is particular for this environment, so I will report that
later. Not a release blocker at all.

However, I seem to remember when doing scr:list you could give -s (or
--show-hidden) as a flag. Now when I do that I get:
karaf@karaf()> scr:list --show-hidden
Error executing command: Cannot coerce list(String) to any of [(long), ()]

If I give scr:list an obviously bogus flag, I get the same error. Should -s
or --show-hidden work for scr:list or am I remembering wrong?

It's not a general problem with flags, because I can perform  "bundle:list
-s -t 0", for example

The child instance was created with --feature config and --feature scr

I also tried hot deploy and that worked as well.

- Eric L

On Thu, Oct 8, 2020 at 3:51 PM Freeman Fang  wrote:

> +1(binding)
> Thanks JB!
>
> Freeman
>
> On Tue, Oct 6, 2020 at 3:34 PM Jean-Baptiste Onofre 
> wrote:
>
> > Hi everyone,
> >
> > I submit Apache Karaf runtime 4.2.10 release to your vote.
> >
> > This is a maintenance release on the 4.2.x series bringing fixes, updates
> > and improvements.
> > It especially included fixed version of Felix FileInstall.
> >
> > Release Notes:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12348288
> > <
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12348288
> > >
> >
> > Staging Repository:
> > https://repository.apache.org/content/repositories/orgapachekaraf-1148/
> <
> > https://repository.apache.org/content/repositories/orgapachekaraf-1148/>
> >
> > Staging Dist:
> > https://dist.apache.org/repos/dist/dev/karaf/4.2.10 <
> > https://dist.apache.org/repos/dist/dev/karaf/4.2.10>
> >
> > Git Tag:
> > karaf-4.2.10
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Don't approve the release (please provide specific comments)
> >
> > This vote will be open for at least 72 hours.
> >
> > Thanks,
> > Regards
> > JB
> >
> >
>

Re: [VOTE] Apache Karaf 4.2.10 release

[Eric Lilja]

+1 (non-binding, tentative) - ran some Pax Exam tests, one of which applies
configuration using fileinstall, and they all passed. Container looked
healthy! Promising!

Tomorrow I will do some manual tests and see if I find anything. With
previous releases on 4.2-track there have been quite a few shell problems,
mainly due to jline regressions (or gogo-related), and I can see in the
release notes there's a new jline included, so probably worthwhile testing.
I don't have time to test that today, though, since I want to get some
game-time in, before I head to bed, now that I'm the only one awake ;-)

- Eric L

On Tue, Oct 6, 2020 at 9:34 PM Jean-Baptiste Onofre  wrote:

> Hi everyone,
>
> I submit Apache Karaf runtime 4.2.10 release to your vote.
>
> This is a maintenance release on the 4.2.x series bringing fixes, updates
> and improvements.
> It especially included fixed version of Felix FileInstall.
>
> Release Notes:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12348288
> <
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12348288
> >
>
> Staging Repository:
> https://repository.apache.org/content/repositories/orgapachekaraf-1148/ <
> https://repository.apache.org/content/repositories/orgapachekaraf-1148/>
>
> Staging Dist:
> https://dist.apache.org/repos/dist/dev/karaf/4.2.10 <
> https://dist.apache.org/repos/dist/dev/karaf/4.2.10>
>
> Git Tag:
> karaf-4.2.10
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks,
> Regards
> JB
>
>

Re: Exceptions seen when using Karaf 4.2.9/Java 11/PaxExam

[Eric Lilja]

Thanks for the update, JB! Personally, I'm happy to wait a few days extra
to get the Felix framework upgrade into 4.2.10 as well. Thanks for all your
work and help!

- Eric L

On Thu, Aug 13, 2020 at 6:55 PM Jean-Baptiste Onofre 
wrote:

> Hi Eric,
>
> Happy it fixed your issue.
>
> About Felix Framework, I’m working on it, not sure I will have time to cut
> Felix release for Karaf 4.2.10 but I’m trying ;)
> On the other hand, I also have some change to do in order to support JDK
> 14.
>
> Regards
> JB
>
> > Le 13 août 2020 à 18:51, Eric Lilja  a écrit :
> >
> > Thanks for the quick replies, Robert and JB!
> >
> > I ended up adding these three VM options and the problem disappeared:
> >
> > new
> >
> VMOption("--add-exports=java.base/org.apache.karaf.specs.locator=java.xml,ALL-UNNAMED"),
> > new VMOption("--patch-module"),
> > new VMOption("java.base=lib/endorsed/org.apache.karaf.specs.locator-" +
> > System.getProperty("karaf.version") + ".jar")
> >
> > I also added this Surefire configuration to make a karaf.version system
> > property available
> > 
> >
> >${karaf.version}
> >
> > 
> >
> > JB: Have any idea what are the odds for a Felix framework release on the
> > 5.6.x fixing the reflective access warning?
> >
> > - Eric L
> >
> > On Thu, Aug 13, 2020 at 6:24 PM Jean-Baptiste Onofre 
> > wrote:
> >
> >> Hi Eric,
> >>
> >> As it’s seem you don’t extend KarafTestSupport (you should ;)), you have
> >> to provide the locator patch module:
> >>
> >>
> >>
> https://github.com/apache/karaf/blob/master/itests/common/src/main/java/org/apache/karaf/itests/KarafTestSupport.java#L217
> >> <
> >>
> https://github.com/apache/karaf/blob/master/itests/common/src/main/java/org/apache/karaf/itests/KarafTestSupport.java#L217
> >>>
> >>
> >> Regards
> >> JB
> >>
> >>> Le 13 août 2020 à 17:59, Eric Lilja  a écrit :
> >>>
> >>> https://github.com/elilja/java-11-runtime-issue <
> >> https://github.com/elilja/java-11-runtime-issue>
> >>
>
>

Re: Exceptions seen when using Karaf 4.2.9/Java 11/PaxExam

[Eric Lilja]

Thanks for the quick replies, Robert and JB!

I ended up adding these three VM options and the problem disappeared:

new
VMOption("--add-exports=java.base/org.apache.karaf.specs.locator=java.xml,ALL-UNNAMED"),
new VMOption("--patch-module"),
new VMOption("java.base=lib/endorsed/org.apache.karaf.specs.locator-" +
System.getProperty("karaf.version") + ".jar")

I also added this Surefire configuration to make a karaf.version system
property available


${karaf.version}



JB: Have any idea what are the odds for a Felix framework release on the
5.6.x fixing the reflective access warning?

- Eric L

On Thu, Aug 13, 2020 at 6:24 PM Jean-Baptiste Onofre 
wrote:

> Hi Eric,
>
> As it’s seem you don’t extend KarafTestSupport (you should ;)), you have
> to provide the locator patch module:
>
>
> https://github.com/apache/karaf/blob/master/itests/common/src/main/java/org/apache/karaf/itests/KarafTestSupport.java#L217
> <
> https://github.com/apache/karaf/blob/master/itests/common/src/main/java/org/apache/karaf/itests/KarafTestSupport.java#L217
> >
>
> Regards
> JB
>
> > Le 13 août 2020 à 17:59, Eric Lilja  a écrit :
> >
> > https://github.com/elilja/java-11-runtime-issue <
> https://github.com/elilja/java-11-runtime-issue>
>

Exceptions seen when using Karaf 4.2.9/Java 11/PaxExam

[Eric Lilja]

Hello, when attempting to move our existing code base from Java 8 to Java
11, we noticed exceptions appearing in the Karaf log in our automated tests
(using Pax Exam).

I've made a minimal test project available on github show-casing the issue:
https://github.com/elilja/java-11-runtime-issue

Make sure JAVA_HOME is set to Java 11 JDK and simply execute "mvn clean
test" (we're using Maven 3.6.3 by the way)

maven.compiler.source/target for this project is currently set java 11
target, but can be set to java 8, and the issue will still appear if
using a Java 11 runtime.

The karaf log can be found under the target folder, where the karaf
distribution is unpacked, and the exception looks like this:

$ cat target/38ed3633-4936-4894-9334-0d1849833602/data/log/karaf.log
aug. 13, 2020 5:36:48 EM org.apache.karaf.main.Main launch
INFO: Installing and starting initial bundles
aug. 13, 2020 5:36:49 EM org.apache.karaf.main.Main launch
INFO: All initial bundles installed and set to start
aug. 13, 2020 5:36:49 EM org.apache.karaf.main.lock.SimpleFileLock lock
INFO: Trying to lock
C:\projects\java-11-runtime-issue\target\38ed3633-4936-4894-9334-0d1849833602\lock
aug. 13, 2020 5:36:49 EM org.apache.karaf.main.lock.SimpleFileLock lock
INFO: Lock acquired
aug. 13, 2020 5:36:49 EM org.apache.karaf.main.Main$KarafLockCallback
lockAcquired
INFO: Lock acquired. Setting startlevel to 100
2020-08-13T17:36:53,355 | ERROR | features-3-thread-1 | Felix
 | 5 - org.ops4j.pax.logging.pax-logging-api - 1.11.6 | Bundle
org.apache.felix.framework [0] EventDispatcher: Error during dispatch.
(java.lang.NoClassDefFoundError: org/apache/karaf/specs/locator/OsgiLocator)
java.lang.NoClassDefFoundError: org/apache/karaf/specs/locator/OsgiLocator
at
org.apache.karaf.specs.activator.Activator.register(Activator.java:124)
~[org.apache.karaf.specs.activator-4.2.9.jar:4.2.9]
at
org.apache.karaf.specs.activator.Activator.bundleChanged(Activator.java:96)
~[org.apache.karaf.specs.activator-4.2.9.jar:4.2.9]
at
org.apache.felix.framework.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:915)
~[org.apache.felix.framework-5.6.12.jar:?]
at
org.apache.felix.framework.EventDispatcher.fireEventImmediately(EventDispatcher.java:834)
[org.apache.felix.framework-5.6.12.jar:?]
at
org.apache.felix.framework.EventDispatcher.fireBundleEvent(EventDispatcher.java:516)
[org.apache.felix.framework-5.6.12.jar:?]
at
org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4579)
[org.apache.felix.framework-5.6.12.jar:?]
at
org.apache.felix.framework.StatefulResolver.fireResolvedEvents(StatefulResolver.java:1286)
[org.apache.felix.framework-5.6.12.jar:?]
at
org.apache.felix.framework.StatefulResolver.resolve(StatefulResolver.java:512)
[org.apache.felix.framework-5.6.12.jar:?]
at org.apache.felix.framework.Felix.resolveBundles(Felix.java:4108)
[org.apache.felix.framework-5.6.12.jar:?]
at
org.apache.felix.framework.FrameworkWiringImpl.resolveBundles(FrameworkWiringImpl.java:133)
[org.apache.felix.framework-5.6.12.jar:?]
at
org.apache.karaf.features.internal.service.BundleInstallSupportImpl.resolveBundles(BundleInstallSupportImpl.java:244)
[!/:?]
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl.resolveBundles(FeaturesServiceImpl.java:1168)
[!/:?]
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:1022)
[!/:?]
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1062)
[!/:?]
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:998)
[!/:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
[?:?]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
[?:?]
at java.lang.Thread.run(Thread.java:834) [?:?]
2020-08-13T17:36:53,377 | ERROR | FelixDispatchQueue | FrameworkEvent
| 0 - org.apache.felix.framework - 5.6.12 | FrameworkEvent ERROR

This exception trace appears several times in the log. It seems to be
finding an incompatible definition of the OsgiLocator class.

If I switch back to Java 8, the exception disappears, everything looks fine

I get the same behavior both under Linux and Windows. On Windows, Oracle
JDK 11.0.8 was used, on Linux OpenJDK 11.0.8 was used. No difference in
behavior.

It happens with older Karaf 4.2.x-versions as well, and I've seen reports
of this problem on other lists going back to last autumn. With no
resolution.

As a side note, we also noticed this reflective access warning, which I
guess is not related since it's just a warning, but I felt I should share
it nonetheless:
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by

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

- Eric L


On Sat, Jul 18, 2020 at 4:53 PM Steinar Bang  wrote:

> 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
> it's possible so it works as a workaroung).
>
>

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

[Eric Lilja]

+1 (non-binding)

Tested on Windows 10/Java 8 running some Pax Exam tests. No issues observed.

Not tested interactively, which was a pity I didn't have time for, since
there have been quite a few issues in that area during the 4.2.x-series,
and it would have been nice to confirm the console (mainly) was working
smoothly now, even under Windows.

Reason for limited testing and late vote is that my new computer just
arrived so I had to set it up first, sorry about that

- Eric L

On Fri, Jun 5, 2020 at 2:48 PM Jean-Baptiste Onofre  wrote:

> Hi everyone,
>
> I submit Apache Karaf runtime 4.2.9 release to your vote (take #2 where we
> fixed the ASM update).
>
> This is a maintenance release on the 4.2.x series bringing fixes, updates
> and improvements.
> It especially fixes the issues related to the shell (paste didn’t work
> properly, some commands caused exception, …).
>
> Release Notes:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12346465
> <
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12346465
> >
>
> Staging Repository:
> https://repository.apache.org/content/repositories/orgapachekaraf-1143/ <
> https://repository.apache.org/content/repositories/orgapachekaraf-1143/>
>
> Staging Dist:
> https://dist.apache.org/repos/dist/dev/karaf/4.2.9/ <
> https://dist.apache.org/repos/dist/dev/karaf/4.2.9/>
>
> Git Tag:
> karaf-4.2.9
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks,
> Regards
> JB

Re: [VOTE] Apache Karaf runtime 4.2.8 release

[Eric Lilja]

Unfortunately, I haven't been able to test it on Windows, so cannot vote. I
like to a do a manual test and also run some automated pax exam tests, but
don't have time right now. I was also curious if there's an updated
dependency convergence report, and a comparison with the equivalent report
for 4.2.7?

- Eric L

On Tue, Jan 14, 2020 at 9:28 PM Markus Rathgeb  wrote:

> Hm, for me it depends if the multi part stuff that has been broken on
> 4.2.7 is working again (so depends on the findings of the respective
> thread on the user mailing list).
>

Re: Merry Christmas & releases on the way

[Eric Lilja]

Thanks for the update, JB!

Will KARAF-6480 [1] and KARAF-6514 [2] make it into 4.2.8?

[1] https://issues.apache.org/jira/browse/KARAF-6480
[2] https://issues.apache.org/jira/browse/KARAF-6514

- Eric L

On Wed, Dec 25, 2019 at 10:13 AM Jean-Baptiste Onofré 
wrote:

> Hi guys,
>
> on behalf of the Karaf team, I wish a Merry Christmas to the whole Karaf
> community.
>
> Let me use this mail to give you an update about releases:
> - Karaf 4.2.8 is planned before the end of this year (this week or early
> beginning of next week).
> - I do my best to cut 4.3.0.RC1 next week, but it's possible that I will
> cut the release first week of January (depending how fast I can be on
> 4.2.8 preparation).
> - Decanter 2.3.0 preparation moved well, but I have to release Karaf
> 4.2.8 first (as I have dependency to KarafTestSupport 4.2.8 for Decanter
> itests).
>
> I keep you posted !
>
> Again, Merry Christmas and enjoy time with family and friends.
>
> Regards
> JB
>
> On 11/10/2019 07:31, Jean-Baptiste Onofré wrote:
> > Hi guys,
> >
> > I've almost finished the refactoring of Cave for Cave 4.2.0 release:
> >
> > https://github.com/jbonofre/karaf-cave/tree/REFACTORING
> >
> > I'm polishing a bit this morning and merge to master later today.
> > I will prepare the Cave 4.2.0 during the week end.
> >
> > On the other hand, I moved forward on Karaf master heading to 4.3.0.RC1.
> > I should be able to push a first RC (RC1) beginning on next week.
> >
> > Meantime, I also moved forward on Decanter 2.3.0 preparation with new
> > improvements, fixes, etc.
> > The target is to submit this release in couple of weeks.
> >
> > Stay tuned !
> >
> > Regards
> > JB
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [HEADS UP] Apache Karaf 4.2.7 on the way

[Eric Lilja]

Hi! Do we have time to bump hibernate-validator to 6.0.17.Final?

Excited about the release!

- Eric L

On Mon, Sep 16, 2019 at 7:55 AM Jean-Baptiste Onofré 
wrote:

> No problem, it's just 3 or 4 days and I would like to include other fixes.
>
> Regards
> JB
>
> On 16/09/2019 07:53, Robert Varga wrote:
> > On 16/09/2019 07:50, Jean-Baptiste Onofré wrote:
> >> Hi Robert,
> >>
> >> just to let you know that I updated ASM OpCodes in Aries Proxy and it
> >> works now.
> >>
> >> I will cut the Aries Proxy Impl release today.
> >
> > Awesome, thank you! Sorry about delaying karaf...
> >
> > Regards,
> > Robert
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [VOTE] Apache Karaf (runtime) 4.2.6 release

[Eric Lilja]

Hi JB, and thanks for the hints! However, this time I solved it by letting
Maven resolve org.apache.karaf.scr.management/state before executing any
Pax Exam tests, so I didn't have to modify my tests. Everything worked. My
vote remains at +1 and I'm looking forward to seeing this release on Maven
central, great work!

- Eric L

On Sat, Jun 8, 2019 at 6:52 PM Jean-Baptiste Onofré  wrote:

> Hi,
>
> it's "as karaf", so basically, it uses your .m2/repository by default
> and then goes into the repository in etc/org.ops4j.pax.url.mvn.cfg.
>
> So, you have to use PaxExam Configuration to add the staging repo there.
>
> I don't have such issue locally because I'm building Karaf based on the
> tag.
>
> Regards
> JB
>
> On 08/06/2019 18:46, Eric Lilja wrote:
> > Ah, when doing some more testing I noticed my Pax Exam tests using Karaf
> do
> > not work, because some artifacts cannot be resolved (I believe
> > org.apache.karaf.scr.management was among them). I updated my maven
> > settings to use the staging repository (both for repository and
> > pluginRepository) and at build-time I can resolve artifacts without
> issue),
> > but I believe I need to tweak my Pax Exam test to also use the staging
> > repository. So it's a little more involved to evaluate Karaf since I also
> > have to tweak my Pax Exam tests, it's not just simply adding staging
> > repository to Maven's setting.xml. Maybe someone has some tips about
> that?
> > Basically I want Pax Exam to use repository setup from my settings.xml, I
> > don't want to duplicate that information in Pax Exam itself. I'm sure
> > others are using Pax Exam too, how do you manage repository information?
> >
> > - Eric L
> >
> > On Sat, Jun 8, 2019 at 1:06 AM Eric Lilja  wrote:
> >
> >> +1 (non-binding)
> >>
> >> - Eric Lilja
> >>
> >> On Fri, Jun 7, 2019 at 10:54 PM Robert Varga  wrote:
> >>
> >>> On 07/06/2019 13:13, Jean-Baptiste Onofré wrote:
> >>>> Hi all,
> >>>>
> >>>> I submit Apache Karaf (runtime) 4.2.6 to your vote. This is a
> >>>> maintenance release on the 4.2.x series, bringing some improvements
> and
> >>>> bug fixes (scr with equinox, dependencies updates, and much more !).
> >>>>
> >>>> Release Notes:
> >>>>
> >>>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12345365
> >>>>
> >>>> Staging Repository:
> >>>>
> https://repository.apache.org/content/repositories/orgapachekaraf-1132/
> >>>>
> >>>> Git Tag:
> >>>> karaf-4.2.6
> >>>>
> >>>> Please vote to approve this release:
> >>>>
> >>>> [ ] +1 Approve the release
> >>>> [ ] -1 Don't approve the release (please provide specific comments)
> >>>
> >>> +1, non-binding, based on very basic validation with OpenDaylight.
> >>>
> >>> One question: pax-web-features-7.2.10 still references
> >>> commons-beanutils/1.8.3, which trips up vuln scanners, is this
> >>> intentional?
> >>>
> >>> Thanks,
> >>> Robert
> >>>
> >>
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [VOTE] Apache Karaf (runtime) 4.2.6 release

[Eric Lilja]

Ah, when doing some more testing I noticed my Pax Exam tests using Karaf do
not work, because some artifacts cannot be resolved (I believe
org.apache.karaf.scr.management was among them). I updated my maven
settings to use the staging repository (both for repository and
pluginRepository) and at build-time I can resolve artifacts without issue),
but I believe I need to tweak my Pax Exam test to also use the staging
repository. So it's a little more involved to evaluate Karaf since I also
have to tweak my Pax Exam tests, it's not just simply adding staging
repository to Maven's setting.xml. Maybe someone has some tips about that?
Basically I want Pax Exam to use repository setup from my settings.xml, I
don't want to duplicate that information in Pax Exam itself. I'm sure
others are using Pax Exam too, how do you manage repository information?

- Eric L

On Sat, Jun 8, 2019 at 1:06 AM Eric Lilja  wrote:

> +1 (non-binding)
>
> - Eric Lilja
>
> On Fri, Jun 7, 2019 at 10:54 PM Robert Varga  wrote:
>
>> On 07/06/2019 13:13, Jean-Baptiste Onofré wrote:
>> > Hi all,
>> >
>> > I submit Apache Karaf (runtime) 4.2.6 to your vote. This is a
>> > maintenance release on the 4.2.x series, bringing some improvements and
>> > bug fixes (scr with equinox, dependencies updates, and much more !).
>> >
>> > Release Notes:
>> >
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12345365
>> >
>> > Staging Repository:
>> > https://repository.apache.org/content/repositories/orgapachekaraf-1132/
>> >
>> > Git Tag:
>> > karaf-4.2.6
>> >
>> > Please vote to approve this release:
>> >
>> > [ ] +1 Approve the release
>> > [ ] -1 Don't approve the release (please provide specific comments)
>>
>> +1, non-binding, based on very basic validation with OpenDaylight.
>>
>> One question: pax-web-features-7.2.10 still references
>> commons-beanutils/1.8.3, which trips up vuln scanners, is this
>> intentional?
>>
>> Thanks,
>> Robert
>>
>

Re: [VOTE] Apache Karaf (runtime) 4.2.6 release

[Eric Lilja]

+1 (non-binding)

- Eric Lilja

On Fri, Jun 7, 2019 at 10:54 PM Robert Varga  wrote:

> On 07/06/2019 13:13, Jean-Baptiste Onofré wrote:
> > Hi all,
> >
> > I submit Apache Karaf (runtime) 4.2.6 to your vote. This is a
> > maintenance release on the 4.2.x series, bringing some improvements and
> > bug fixes (scr with equinox, dependencies updates, and much more !).
> >
> > Release Notes:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12345365
> >
> > Staging Repository:
> > https://repository.apache.org/content/repositories/orgapachekaraf-1132/
> >
> > Git Tag:
> > karaf-4.2.6
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Don't approve the release (please provide specific comments)
>
> +1, non-binding, based on very basic validation with OpenDaylight.
>
> One question: pax-web-features-7.2.10 still references
> commons-beanutils/1.8.3, which trips up vuln scanners, is this intentional?
>
> Thanks,
> Robert
>

Re: [HEADS UP] Preparing Karaf 4.2.6 and 4.3.0.RC1

[Eric Lilja]

Can we fix the few, odd lines using tabs as indentation character in the
root pom as well (the one that contains all dependency management)? :-)
Maven coordinates: org.apache.karaf:karaf

- Eric L

On Tue, Jun 4, 2019 at 12:57 PM Jean-Baptiste Onofré 
wrote:

> Hi guys,
>
> I would like to provide a quick update and those releases.
>
> I created pax-logging-1.10.x branch and released pax-logging 1.10.2 with
> the improvements to avoid the refreshes. With Grzegorz, we also started
> bunch of improvements on master and we also already started the OSGi R7
> support in Pax Logging.
>
> I'm completing the latest minor updates on karaf-4.2.x: I will submit
> Karaf 4.2.6 to vote tonight or tomorrow early morning.
>
> Once done, I will focus on 4.3.0.RC1 with OSGi R7 support.
>
> Stay tuned !
>
> Regards
> JB
>
> On 20/05/2019 07:47, Jean-Baptiste Onofré wrote:
> > Hi guys,
> >
> > FYI, I'm completing the preparation of Karaf 4.2.6 today. I hope to
> > submit this release to vote tomorrow or Wednesday.
> >
> > In the mean time, we are moving forward on third party projects
> > (especially Pax*) to be OSGi R7 compliant.
> > I'm also doing some preparation steps on Karaf master to prepare the
> > OSGi R7 upgrade.
> > I think I will be able to cut a RC1 beginning of next week.
> >
> > Stay tuned !
> >
> > Regards
> > JB
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [HEADS UP] Preparing Karaf 4.2.6 and 4.3.0.RC1

[Eric Lilja]

Thanks for the update, JB, looking forward to seeing 4.2.6 on vote! Nice to
see the pax-logging improvements part of it!

- Eric L

On Tue, Jun 4, 2019 at 12:57 PM Jean-Baptiste Onofré 
wrote:

> Hi guys,
>
> I would like to provide a quick update and those releases.
>
> I created pax-logging-1.10.x branch and released pax-logging 1.10.2 with
> the improvements to avoid the refreshes. With Grzegorz, we also started
> bunch of improvements on master and we also already started the OSGi R7
> support in Pax Logging.
>
> I'm completing the latest minor updates on karaf-4.2.x: I will submit
> Karaf 4.2.6 to vote tonight or tomorrow early morning.
>
> Once done, I will focus on 4.3.0.RC1 with OSGi R7 support.
>
> Stay tuned !
>
> Regards
> JB
>
> On 20/05/2019 07:47, Jean-Baptiste Onofré wrote:
> > Hi guys,
> >
> > FYI, I'm completing the preparation of Karaf 4.2.6 today. I hope to
> > submit this release to vote tomorrow or Wednesday.
> >
> > In the mean time, we are moving forward on third party projects
> > (especially Pax*) to be OSGi R7 compliant.
> > I'm also doing some preparation steps on Karaf master to prepare the
> > OSGi R7 upgrade.
> > I think I will be able to cut a RC1 beginning of next week.
> >
> > Stay tuned !
> >
> > Regards
> > JB
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [HEADS UP] Preparing Karaf 4.2.6 and 4.3.0.RC1

[Eric Lilja]

Ah, that's great news! Looking forward to see the improved Pax Logging 1.x
in 4.2.x then

- Eric L

On Mon, May 20, 2019 at 10:25 AM Jean-Baptiste Onofré 
wrote:

> Ah yes, those ones will be applied on both Pax Logging 2.x and 1.x.
>
> Regards
> JB
>
> On 20/05/2019 10:01, Eric Lilja wrote:
> > Sorry, I was unclear, I most thinking about the refactorings I've heard
> of
> > to reduce the number of optional imports (which would reduce refreshes)
> and
> > better class layout in general in the api/impl-bundles. Are these
> > improvements dependent on R7?
> >
> > - Eric L
> >
> > On Mon, May 20, 2019 at 9:58 AM Jean-Baptiste Onofré 
> > wrote:
> >
> >> No, Pax Logging improvements with OSGi R7 will go into 4.3.x.
> >>
> >> Regards
> >> JB
> >>
> >> On 20/05/2019 09:29, Eric Lilja wrote:
> >>> Sounds exciting! Will the improvements to pax logging make it to 4.2.x
> >>> release train?
> >>>
> >>> - Eric L
> >>>
> >>> On Mon, May 20, 2019 at 7:47 AM Jean-Baptiste Onofré 
> >>> wrote:
> >>>
> >>>> Hi guys,
> >>>>
> >>>> FYI, I'm completing the preparation of Karaf 4.2.6 today. I hope to
> >>>> submit this release to vote tomorrow or Wednesday.
> >>>>
> >>>> In the mean time, we are moving forward on third party projects
> >>>> (especially Pax*) to be OSGi R7 compliant.
> >>>> I'm also doing some preparation steps on Karaf master to prepare the
> >>>> OSGi R7 upgrade.
> >>>> I think I will be able to cut a RC1 beginning of next week.
> >>>>
> >>>> Stay tuned !
> >>>>
> >>>> Regards
> >>>> JB
> >>>> --
> >>>> Jean-Baptiste Onofré
> >>>> jbono...@apache.org
> >>>> http://blog.nanthrax.net
> >>>> Talend - http://www.talend.com
> >>>>
> >>>
> >>
> >> --
> >> Jean-Baptiste Onofré
> >> jbono...@apache.org
> >> http://blog.nanthrax.net
> >> Talend - http://www.talend.com
> >>
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [HEADS UP] Preparing Karaf 4.2.6 and 4.3.0.RC1

[Eric Lilja]

Sorry, I was unclear, I most thinking about the refactorings I've heard of
to reduce the number of optional imports (which would reduce refreshes) and
better class layout in general in the api/impl-bundles. Are these
improvements dependent on R7?

- Eric L

On Mon, May 20, 2019 at 9:58 AM Jean-Baptiste Onofré 
wrote:

> No, Pax Logging improvements with OSGi R7 will go into 4.3.x.
>
> Regards
> JB
>
> On 20/05/2019 09:29, Eric Lilja wrote:
> > Sounds exciting! Will the improvements to pax logging make it to 4.2.x
> > release train?
> >
> > - Eric L
> >
> > On Mon, May 20, 2019 at 7:47 AM Jean-Baptiste Onofré 
> > wrote:
> >
> >> Hi guys,
> >>
> >> FYI, I'm completing the preparation of Karaf 4.2.6 today. I hope to
> >> submit this release to vote tomorrow or Wednesday.
> >>
> >> In the mean time, we are moving forward on third party projects
> >> (especially Pax*) to be OSGi R7 compliant.
> >> I'm also doing some preparation steps on Karaf master to prepare the
> >> OSGi R7 upgrade.
> >> I think I will be able to cut a RC1 beginning of next week.
> >>
> >> Stay tuned !
> >>
> >> Regards
> >> JB
> >> --
> >> Jean-Baptiste Onofré
> >> jbono...@apache.org
> >> http://blog.nanthrax.net
> >> Talend - http://www.talend.com
> >>
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [HEADS UP] Preparing Karaf 4.2.6 and 4.3.0.RC1

[Eric Lilja]

Sounds exciting! Will the improvements to pax logging make it to 4.2.x
release train?

- Eric L

On Mon, May 20, 2019 at 7:47 AM Jean-Baptiste Onofré 
wrote:

> Hi guys,
>
> FYI, I'm completing the preparation of Karaf 4.2.6 today. I hope to
> submit this release to vote tomorrow or Wednesday.
>
> In the mean time, we are moving forward on third party projects
> (especially Pax*) to be OSGi R7 compliant.
> I'm also doing some preparation steps on Karaf master to prepare the
> OSGi R7 upgrade.
> I think I will be able to cut a RC1 beginning of next week.
>
> Stay tuned !
>
> Regards
> JB
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [VOTE] Apache Karaf (runtime) 4.2.5 release

[Eric Lilja]

+1 (non-binding), looking forward to see it on Maven central!

On Fri, Apr 19, 2019 at 1:32 PM Jamie G.  wrote:

> +1 (binding)
>
> Cheers,
> Jamie
>
> On Fri, Apr 19, 2019 at 7:20 AM Andrea Cosentino
>  wrote:
> >
> > +1 (non-binding)
> >
> > Thanks JB
> >
> > --
> > Andrea Cosentino
> > --
> > Apache Camel PMC Chair
> > Apache Karaf Committer
> > Apache Servicemix PMC Member
> > Email: ancosen1...@yahoo.com
> > Twitter: @oscerd2
> > Github: oscerd
> >
> >
> >
> >
> >
> >
> > On Friday, April 19, 2019, 10:40:17 AM GMT+2, Jean-Baptiste Onofré <
> j...@nanthrax.net> wrote:
> >
> >
> >
> >
> >
> > +1 (binding)
> >
> > Regards
> > JB
> >
> > On 17/04/2019 20:29, Jean-Baptiste Onofré wrote:
> > > Hi all,
> > >
> > > I submit Apache Karaf (runtime) 4.2.5 to your vote. This is a
> > > maintenance release on the 4.2.x series, bringing some improvements and
> > > bug fixes (scr commands, new docker goal in maven plugin, new
> > > distribution examples, ...).
> > >
> > > Release Notes:
> > >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12345153
> > >
> > > Staging Repository:
> > >
> https://repository.apache.org/content/repositories/orgapachekaraf-1131/
> > >
> > > Git Tag:
> > > karaf-4.2.5
> > >
> > > Please vote to approve this release:
> > >
> > > [ ] +1 Approve the release
> > > [ ] -1 Don't approve the release (please provide specific comments)
> > >
> > > This vote will be open for at least 72 hours.
> > >
> > > Thanks,
> > > Regards
> > > JB
> > >
> >
> > --
> > Jean-Baptiste Onofré
> > jbono...@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
>

Re: [VOTE] Apache Karaf (runtime) 4.2.5 release

[Eric Lilja]

Ah, thanks for the clarification, JB! Very happy to see this release under
vote!

On Thu, Apr 18, 2019 at 10:57 AM Jean-Baptiste Onofré 
wrote:

> Hi,
>
> No need for Felix Utils, I did a workaround in Features Deployer
> directly. I will remove the workaround once I will do the new Felix
> Utils release.
>
> Regards
> JB
>
> On 18/04/2019 09:47, Eric Lilja wrote:
> > Ah, nice to see it on vote, but I thought we had to wait one or two days
> > for a Felix utils release first?
> >
> > Hope to give it a spin later and will submit my (non-binding) vote after
> I
> > have done so.
> >
> > - Eric L
> >
> > On Thu, Apr 18, 2019 at 6:51 AM Freeman Fang 
> wrote:
> >
> >> +1 (binding)
> >>
> >> Thanks!
> >> －
> >> Freeman(Yue) Fang
> >>
> >> Red Hat, Inc.
> >>
> >>
> >>
> >>
> >>
> >>> On Apr 18, 2019, at 2:29 AM, Jean-Baptiste Onofré 
> >> wrote:
> >>>
> >>> Hi all,
> >>>
> >>> I submit Apache Karaf (runtime) 4.2.5 to your vote. This is a
> >>> maintenance release on the 4.2.x series, bringing some improvements and
> >>> bug fixes (scr commands, new docker goal in maven plugin, new
> >>> distribution examples, ...).
> >>>
> >>> Release Notes:
> >>>
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12345153
> >>>
> >>> Staging Repository:
> >>>
> https://repository.apache.org/content/repositories/orgapachekaraf-1131/
> >>>
> >>> Git Tag:
> >>> karaf-4.2.5
> >>>
> >>> Please vote to approve this release:
> >>>
> >>> [ ] +1 Approve the release
> >>> [ ] -1 Don't approve the release (please provide specific comments)
> >>>
> >>> This vote will be open for at least 72 hours.
> >>>
> >>> Thanks,
> >>> Regards
> >>> JB
> >>> --
> >>> Jean-Baptiste Onofré
> >>> jbono...@apache.org
> >>> http://blog.nanthrax.net
> >>> Talend - http://www.talend.com
> >>
> >>
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [VOTE] Apache Karaf (runtime) 4.2.5 release

[Eric Lilja]

Ah, nice to see it on vote, but I thought we had to wait one or two days
for a Felix utils release first?

Hope to give it a spin later and will submit my (non-binding) vote after I
have done so.

- Eric L

On Thu, Apr 18, 2019 at 6:51 AM Freeman Fang  wrote:

> +1 (binding)
>
> Thanks!
> －
> Freeman(Yue) Fang
>
> Red Hat, Inc.
>
>
>
>
>
> > On Apr 18, 2019, at 2:29 AM, Jean-Baptiste Onofré 
> wrote:
> >
> > Hi all,
> >
> > I submit Apache Karaf (runtime) 4.2.5 to your vote. This is a
> > maintenance release on the 4.2.x series, bringing some improvements and
> > bug fixes (scr commands, new docker goal in maven plugin, new
> > distribution examples, ...).
> >
> > Release Notes:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140=12345153
> >
> > Staging Repository:
> > https://repository.apache.org/content/repositories/orgapachekaraf-1131/
> >
> > Git Tag:
> > karaf-4.2.5
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Don't approve the release (please provide specific comments)
> >
> > This vote will be open for at least 72 hours.
> >
> > Thanks,
> > Regards
> > JB
> > --
> > Jean-Baptiste Onofré
> > jbono...@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
>
>

Re: [HEADS UP] Apache Karaf 4.2.5 should be on vote tonight

[Eric Lilja]

Great news, JB!

On Mon, Apr 15, 2019 at 7:23 AM Francois Papon 
wrote:

> Thanks JB!
>
> regards,
>
> François Papon
> fpa...@apache.org
>
> Le 15/04/2019 à 08:21, Jean-Baptiste Onofré a écrit :
> > Hi guys,
> >
> > I fixed the latest issues for 4.2.5 during the weekend. I'm working
> > today on the examples (including dynamic/static distribution +
> > dockerfile generation).
> >
> > I plan to submit Karaf 4.2.5 to vote tonight.
> >
> > Regards
> > JB
>

Re: Problem deploying 4.2.3 custom distribution

[Eric Lilja]

Ah, thanks for the update, I am constantly checking the activity stream on
Jira to see what is happening, we are eagerly awaiting 4.2.4!

- Eric L

On Wed, Mar 6, 2019 at 7:59 AM Jean-Baptiste Onofré  wrote:

> Hi,
>
> just to let you know that most of the changes are done on local
> branches. I will open the PRs soon and move forward on 4.2.4. I just
> have to prepare Felix ConfigAdmin release and complete ServiceMix
> Bundles release first.
>
> Stay tuned !
>
> Regards
> JB
>
> On 03/03/2019 18:16, Jean-Baptiste Onofré wrote:
> > Hi guys,
> >
> > FYI, I will move forward on 4.2.4 release tomorrow.
> >
> > Regards
> > JB
> >
> > On 26/02/2019 09:46, Jean-Baptiste Onofré wrote:
> >> Good point, it makes sense. I will do both in a row.
> >>
> >> I also have other fixes ready. I will prepare 4.2.4 soon. Stay tuned !
> ;)
> >>
> >> Regards
> >> JB
> >>
> >> On 26/02/2019 09:41, Eric Lilja wrote:
> >>> Speaking for my project, we're not impacted by this particular issue,
> >>> but
> >>> we would still be very happy to see a 4.2.4 out as soon as possible
> >>> for the
> >>> fixes to variable substitution, in particular.
> >>>
> >>> - Eric L
> >>>
> >>> On Tue, Feb 26, 2019 at 6:44 AM Jean-Baptiste Onofré 
> >>> wrote:
> >>>
> >>>> As other plugins (especially deploy) didn't yet update, and in order
> to
> >>>> keep aligned, I'm proposing to downgrade to wagon 3.2.0 (as before)
> and
> >>>> quickly cut Karaf 4.2.4 to avoid to impact the users.
> >>>> We will upgrade wagon sync with other Maven plugins to avoid "API
> >>>> change" in Wagon.
> >>>>
> >>>> Thoughts ?
> >>>>
> >>>> Regards
> >>>> JB
> >>>>
> >>>> On 24/02/2019 11:20, Fabian Lange wrote:
> >>>>> Hi,
> >>>>>
> >>>>> did anyone come across this problem when deploying a 4.2.3 custom
> >>>> distribution?
> >>>>>
> >>>>> [ERROR] Failed to execute goal
> >>>>> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
> >>>>> (default-deploy) on project karaf-assembly: Execution default-deploy
> >>>>> of goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
> >>>>> failed: An API incompatibility was encountered while executing
> >>>>> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy:
> >>>>> java.lang.NoSuchMethodError:
> >>>>>
> >>>>
> org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.getBufferCapacityForTransfer(J)I
> >>>>
> >>>>>
> >>>>>
> >>>>> I have the feeling that there is a new dependency from pax-url /
> karaf
> >>>>> maven plugin interfering with mvn-deploy?
> >>>>>
> >>>>> I will dig into this and report findings, if somebody has seen and
> >>>>> solved this let me know. Thx
> >>>>>
> >>>>> Fabian
> >>>>>
> >>>>
> >>>> --
> >>>> Jean-Baptiste Onofré
> >>>> jbono...@apache.org
> >>>> http://blog.nanthrax.net
> >>>> Talend - http://www.talend.com
> >>>>
> >>>
> >>
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: Problem deploying 4.2.3 custom distribution

[Eric Lilja]

That's awesome news, thanks JB! Can't wait for 4.2.4 to appear!

- Eric L

On 2019-03-03 18:16, Jean-Baptiste Onofré wrote:

Hi guys,

FYI, I will move forward on 4.2.4 release tomorrow.

Regards
JB

On 26/02/2019 09:46, Jean-Baptiste Onofré wrote:

Good point, it makes sense. I will do both in a row.

I also have other fixes ready. I will prepare 4.2.4 soon. Stay tuned 
! ;)


Regards
JB

On 26/02/2019 09:41, Eric Lilja wrote:
Speaking for my project, we're not impacted by this particular 
issue, but
we would still be very happy to see a 4.2.4 out as soon as possible 
for the

fixes to variable substitution, in particular.

- Eric L

On Tue, Feb 26, 2019 at 6:44 AM Jean-Baptiste Onofré 
wrote:

As other plugins (especially deploy) didn't yet update, and in 
order to
keep aligned, I'm proposing to downgrade to wagon 3.2.0 (as before) 
and

quickly cut Karaf 4.2.4 to avoid to impact the users.
We will upgrade wagon sync with other Maven plugins to avoid "API
change" in Wagon.

Thoughts ?

Regards
JB

On 24/02/2019 11:20, Fabian Lange wrote:

Hi,

did anyone come across this problem when deploying a 4.2.3 custom

distribution?


[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
(default-deploy) on project karaf-assembly: Execution default-deploy
of goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
failed: An API incompatibility was encountered while executing
org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy:
java.lang.NoSuchMethodError:

org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.getBufferCapacityForTransfer(J)I 




I have the feeling that there is a new dependency from pax-url / 
karaf

maven plugin interfering with mvn-deploy?

I will dig into this and report findings, if somebody has seen and
solved this let me know. Thx

Fabian



--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Problem deploying 4.2.3 custom distribution

[Eric Lilja]

If the new bugfix releases of felix.configadmin and felix.scr could be
included as well, that would be great!

- Eric L

On Tue, Feb 26, 2019 at 9:41 AM Eric Lilja  wrote:

> Speaking for my project, we're not impacted by this particular issue, but
> we would still be very happy to see a 4.2.4 out as soon as possible for the
> fixes to variable substitution, in particular.
>
> - Eric L
>
> On Tue, Feb 26, 2019 at 6:44 AM Jean-Baptiste Onofré 
> wrote:
>
>> As other plugins (especially deploy) didn't yet update, and in order to
>> keep aligned, I'm proposing to downgrade to wagon 3.2.0 (as before) and
>> quickly cut Karaf 4.2.4 to avoid to impact the users.
>> We will upgrade wagon sync with other Maven plugins to avoid "API
>> change" in Wagon.
>>
>> Thoughts ?
>>
>> Regards
>> JB
>>
>> On 24/02/2019 11:20, Fabian Lange wrote:
>> > Hi,
>> >
>> > did anyone come across this problem when deploying a 4.2.3 custom
>> distribution?
>> >
>> > [ERROR] Failed to execute goal
>> > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
>> > (default-deploy) on project karaf-assembly: Execution default-deploy
>> > of goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
>> > failed: An API incompatibility was encountered while executing
>> > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy:
>> > java.lang.NoSuchMethodError:
>> >
>> org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.getBufferCapacityForTransfer(J)I
>> >
>> >
>> > I have the feeling that there is a new dependency from pax-url / karaf
>> > maven plugin interfering with mvn-deploy?
>> >
>> > I will dig into this and report findings, if somebody has seen and
>> > solved this let me know. Thx
>> >
>> > Fabian
>> >
>>
>> --
>> Jean-Baptiste Onofré
>> jbono...@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>

Re: Problem deploying 4.2.3 custom distribution

[Eric Lilja]

That's great news! Exciting! Thanks JB! :-)

- Eric L

On Tue, Feb 26, 2019 at 9:46 AM Jean-Baptiste Onofré 
wrote:

> Good point, it makes sense. I will do both in a row.
>
> I also have other fixes ready. I will prepare 4.2.4 soon. Stay tuned ! ;)
>
> Regards
> JB
>
> On 26/02/2019 09:41, Eric Lilja wrote:
> > Speaking for my project, we're not impacted by this particular issue, but
> > we would still be very happy to see a 4.2.4 out as soon as possible for
> the
> > fixes to variable substitution, in particular.
> >
> > - Eric L
> >
> > On Tue, Feb 26, 2019 at 6:44 AM Jean-Baptiste Onofré 
> > wrote:
> >
> >> As other plugins (especially deploy) didn't yet update, and in order to
> >> keep aligned, I'm proposing to downgrade to wagon 3.2.0 (as before) and
> >> quickly cut Karaf 4.2.4 to avoid to impact the users.
> >> We will upgrade wagon sync with other Maven plugins to avoid "API
> >> change" in Wagon.
> >>
> >> Thoughts ?
> >>
> >> Regards
> >> JB
> >>
> >> On 24/02/2019 11:20, Fabian Lange wrote:
> >>> Hi,
> >>>
> >>> did anyone come across this problem when deploying a 4.2.3 custom
> >> distribution?
> >>>
> >>> [ERROR] Failed to execute goal
> >>> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
> >>> (default-deploy) on project karaf-assembly: Execution default-deploy
> >>> of goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
> >>> failed: An API incompatibility was encountered while executing
> >>> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy:
> >>> java.lang.NoSuchMethodError:
> >>>
> >>
> org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.getBufferCapacityForTransfer(J)I
> >>>
> >>>
> >>> I have the feeling that there is a new dependency from pax-url / karaf
> >>> maven plugin interfering with mvn-deploy?
> >>>
> >>> I will dig into this and report findings, if somebody has seen and
> >>> solved this let me know. Thx
> >>>
> >>> Fabian
> >>>
> >>
> >> --
> >> Jean-Baptiste Onofré
> >> jbono...@apache.org
> >> http://blog.nanthrax.net
> >> Talend - http://www.talend.com
> >>
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: Problem deploying 4.2.3 custom distribution

[Eric Lilja]

Speaking for my project, we're not impacted by this particular issue, but
we would still be very happy to see a 4.2.4 out as soon as possible for the
fixes to variable substitution, in particular.

- Eric L

On Tue, Feb 26, 2019 at 6:44 AM Jean-Baptiste Onofré 
wrote:

> As other plugins (especially deploy) didn't yet update, and in order to
> keep aligned, I'm proposing to downgrade to wagon 3.2.0 (as before) and
> quickly cut Karaf 4.2.4 to avoid to impact the users.
> We will upgrade wagon sync with other Maven plugins to avoid "API
> change" in Wagon.
>
> Thoughts ?
>
> Regards
> JB
>
> On 24/02/2019 11:20, Fabian Lange wrote:
> > Hi,
> >
> > did anyone come across this problem when deploying a 4.2.3 custom
> distribution?
> >
> > [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
> > (default-deploy) on project karaf-assembly: Execution default-deploy
> > of goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
> > failed: An API incompatibility was encountered while executing
> > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy:
> > java.lang.NoSuchMethodError:
> >
> org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.getBufferCapacityForTransfer(J)I
> >
> >
> > I have the feeling that there is a new dependency from pax-url / karaf
> > maven plugin interfering with mvn-deploy?
> >
> > I will dig into this and report findings, if somebody has seen and
> > solved this let me know. Thx
> >
> > Fabian
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: Apache Karaf Pom Missing from Maven Central

[Eric Lilja]

Hi JB and thanks for your continued work on this! I guess it has only been
fixed for the upcoming 4.2.3, because 4.2.2 is still "broken" in this
regard. Any way to publish the missing POM for 4.2.2 posthumously so to
speak?

On Tue, Jan 8, 2019 at 6:13 AM Jean-Baptiste Onofré  wrote:

> Hi guys,
>
> FYI, it has been fixed. I'm currently working on other issues reported
> on 4.2.2 and I will submit 4.2.3 to vote soon.
>
> Regards
> JB
>
> On 02/01/2019 18:47, Williams, Kyle [USA] wrote:
> > Hello!
> >
> > I just wanted to give you guys a heads up that it looks like your Apache
> Karaf pom is missing from Maven Central for version 4.2.2. Happy New Year!
> >
> > http://central.maven.org/maven2/org/apache/karaf/apache-karaf/4.2.2/
> >
> > Kyle Williams
> > Software Engineer
> > Booz|Allen|Hamilton
> > williams_k...@bah.com
> > Cell: (518) 852-5188
> >
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: Consider KARAF-5934 for Karaf 4.2.2?

[Eric Lilja]

Hi, I did as you suggested, put a jar-file in the deploy folder of 
newinst and checked its log. I can see fileinstall trying to start it 
now. Seems guava is not self-contained anymore...I must have missed it 
before. I wish I could log in to the instance and confirm I see it as 
INSTALLED when doing bundle:list


- Eric L

On 2018-12-04 23:17, Jean-Baptiste Onofré wrote:

HI Eric,

the ArrayIndexOutOfBoundsException is already fixed on 4.2.2-SNAPSHOT.

Can you check directly in the karaf.log of the child instance ?

Regards
JB

On 04/12/2018 22:05, Eric Lilja wrote:

Hi!

I decided to re-try, so I did this:
$ cd /cygdrive/c/apache-karaf-4.2.1/bin
$ ./karaf
(when I do this I see the following message, but Karaf starts normally:
' : integer expression expected' (error message starts with the
character ':')
Then, inside Karaf I did
$ instance:create --feature:scr newinst
$ instance:start newinst

$ instance:connect newinst
Now I get
Connecting to host localhost on port 8103
Error executing command: Failed (ArrayIndexOutOfBoundsException) to
execute: 1
log:tail shows:
21:55:46.109 ERROR [Karaf local console user karaf] Exception caught
while executing command
org.apache.sshd.common.SshException: Failed
(ArrayIndexOutOfBoundsException) to execute: 1
     at
org.apache.sshd.common.future.AbstractSshFuture.verifyResult(AbstractSshFuture.java:125)
~[?:?]
     at
org.apache.sshd.client.future.DefaultAuthFuture.verify(DefaultAuthFuture.java:40)
~[?:?]
     at
org.apache.sshd.client.future.DefaultAuthFuture.verify(DefaultAuthFuture.java:33)
~[?:?]
     at
org.apache.sshd.common.future.VerifiableFuture.verify(VerifiableFuture.java:44)
~[?:?]
     at
org.apache.karaf.shell.ssh.SshAction.execute(SshAction.java:168) ~[?:?]
     at
org.apache.karaf.shell.impl.action.command.ActionCommand.execute(ActionCommand.java:84)
~[?:?]
     at
org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:68)
~[?:?]
     at
org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:86)
~[?:?]
     at
org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:599) ~[?:?]
     at
org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:526)
~[?:?]
     at
org.apache.felix.gogo.runtime.Closure.execute(Closure.java:415) ~[?:?]
     at org.apache.felix.gogo.runtime.Pipe.doCall(Pipe.java:416) ~[?:?]
     at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:229) ~[?:?]
     at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:59) ~[?:?]
     at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:?]
     at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
~[?:?]
     at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
~[?:?]
     at java.lang.Thread.run(Thread.java:748) [?:?]
Caused by: java.lang.ArrayIndexOutOfBoundsException: 1
     at
org.apache.karaf.shell.ssh.KnownHostsManager.getKnownKeyInternal(KnownHostsManager.java:84)
~[?:?]
     at
org.apache.karaf.shell.ssh.KnownHostsManager.getKnownKey(KnownHostsManager.java:64)
~[?:?]
     at
org.apache.karaf.shell.ssh.ServerKeyVerifierImpl.verifyServerKey(ServerKeyVerifierImpl.java:57)
~[?:?]
     at
org.apache.sshd.client.session.AbstractClientSession.checkKeys(AbstractClientSession.java:488)
~[?:?]
     at
org.apache.sshd.common.session.helpers.AbstractSession.handleKexMessage(AbstractSession.java:664)
~[?:?]
     at
org.apache.sshd.common.session.helpers.AbstractSession.doHandleMessage(AbstractSession.java:612)
~[?:?]
     at
org.apache.sshd.common.session.helpers.AbstractSession.handleMessage(AbstractSession.java:547)
~[?:?]
     at
org.apache.sshd.common.session.helpers.AbstractSession.decode(AbstractSession.java:1498)
~[?:?]
     at
org.apache.sshd.common.session.helpers.AbstractSession.messageReceived(AbstractSession.java:508)
~[?:?]
     at
org.apache.sshd.common.session.helpers.AbstractSessionIoHandler.messageReceived(AbstractSessionIoHandler.java:66)
~[?:?]
     at
org.apache.sshd.common.io.nio2.Nio2Session.handleReadCycleCompletion(Nio2Session.java:301)
~[?:?]
     at
org.apache.sshd.common.io.nio2.Nio2Session$1.onCompleted(Nio2Session.java:281)
~[?:?]
     at
org.apache.sshd.common.io.nio2.Nio2Session$1.onCompleted(Nio2Session.java:278)
~[?:?]
     at
org.apache.sshd.common.io.nio2.Nio2CompletionHandler.lambda$completed$0(Nio2CompletionHandler.java:38)
~[?:?]
     at java.security.AccessController.doPrivileged(Native Method)
~[?:?]
     at
org.apache.sshd.common.io.nio2.Nio2CompletionHandler.completed(Nio2CompletionHandler.java:37)
~[?:?]
     at sun.nio.ch.Invoker.invokeUnchecked(Invoker.java:126) ~[?:?]
     at sun.nio.ch.Invoker$2.run(Invoker.java:218) ~[?:?]
     at
sun.nio.ch.AsynchronousChannelGroupImpl$1.run(AsynchronousChannelGroupImpl.java:112)
~[?:?]
     ... 3 more

So I

Re: Consider KARAF-5934 for Karaf 4.2.2?

[Eric Lilja]

 with:
instance:create test
instance:start test
instance:connect test

2. I dropped a bundle in the test instance deploy folder.

I can see the fileinstall "trigger" in the log:

2018-12-04 21:21:43,375 | INFO  | nces/test/deploy | fileinstall 
 | 10 - org.apache.felix.fileinstall - 3.6.4 | Started 
bundle: 
file:/home/jbonofre/Workspace/karaf/assemblies/apache-karaf/target/apache-karaf-4.2.2-SNAPSHOT/instances/test/deploy/commons-lang-2.6.jar


So, it looks good to me.

Regards
JB

On 02/12/2018 20:15, Eric Lilja wrote:
Hi, is it possible to consider including KARAF-5934 for 4.2.2? I saw 
it was just tentatively postponed to 4.2.3.


Also, is the deploy folder enabled by default? I downloaded the 
binary distribution (version 4.2.1), and created a new instance with 
feature scr enabled. Everything else vanilla. I put a bundle in the 
deploy folder but it doesn't get installed, no interesting output 
from log:tail either, so no failures. Just like the directory was not 
monitored at all (I did use the deploy directory in the instance I 
created).


Furthermore, output from scr:list seems to lack line breaks. This is 
under Windows, with Cygwin (Mintty) as terminal. Also tried with 
TakeCommand under Windows, which used to work really well with Karaf, 
but when one does bundle:list -s -t 0 for example, a lot columns 
contains only ?-characters (question marks). Also scr:list looks bad 
under it.


- Eric L

Re: Consider KARAF-5934 for Karaf 4.2.2?

[Eric Lilja]

It was an instance created with instance:create --feature scr

I put the jar-file in the deploy folder inside that instance, so it was the
correct one, but it was like I had done nothing.

- Eric L

On Mon, Dec 3, 2018 at 7:30 AM Jean-Baptiste Onofré  wrote:

> Hi Eric,
>
> when you say new instance, you mean instance created with
> instance:create or a "regular" vanilla one (maybe you don't use the
> right deploy folder) ?
>
> You should have something in the log anyway from the artifact installer.
>
> Regards
> JB
>
> On 02/12/2018 21:15, Eric Lilja wrote:
> > Hi, see my replies at relevant places below!
> >
> > On 2018-12-02 21:03, Jean-Baptiste Onofré wrote:
> >> Hi Eric,
> >>
> >> The update to maven-bundle-plugin 4.1.0 introduces some other changes
> >> (as the requirements/capabilities created are extended). Why do you
> >> need this for 4.2.2 ? It's transparent for you as user.
> >> So I will try but without strong commitment. Reasonably, I would
> >> prefer to target in 4.2.3 as I'm planning 4.2.2 for this week. So, it
> >> will be a best effort.
> >
> > Okay, I see, I bumped to that version for my projects without issue so I
> > thought it was straight-forward.
> >
> >>
> >> Yes, deploy folder is enabled by default. Did you deploy a bundle or a
> >> raw jar ?
> >
> > It was one of my bundles, built using maven-bundle-plugin 4.1.0. I have
> > no troubles provisioning it programmatcially when using Karaf/Pax-Exam.
> > I also tried with a 3PP found on Maven central. The deploy folder
> > doesn't seem to be active on Windows. It was working fine on Windows a
> > couple of versions (of Karaf) ago.
> >
> >>
> >> The line breaks should be fixed already (you can test on
> 4.2.2-SNAPSHOT).
> >
> > Ah, nice to hear! Could you try on your end Windows with TakeCommand to
> > see about the question-mark-thingie? I also recall a DOS .bat-file error
> > being reported by TakeCommand as I launched karaf.bat
> >
> > - Eric L
> >
> >>
> >> Regards
> >> JB
> >>
> >> On 02/12/2018 20:15, Eric Lilja wrote:
> >>> Hi, is it possible to consider including KARAF-5934 for 4.2.2? I saw
> >>> it was just tentatively postponed to 4.2.3.
> >>>
> >>> Also, is the deploy folder enabled by default? I downloaded the
> >>> binary distribution (version 4.2.1), and created a new instance with
> >>> feature scr enabled. Everything else vanilla. I put a bundle in the
> >>> deploy folder but it doesn't get installed, no interesting output
> >>> from log:tail either, so no failures. Just like the directory was not
> >>> monitored at all (I did use the deploy directory in the instance I
> >>> created).
> >>>
> >>> Furthermore, output from scr:list seems to lack line breaks. This is
> >>> under Windows, with Cygwin (Mintty) as terminal. Also tried with
> >>> TakeCommand under Windows, which used to work really well with Karaf,
> >>> but when one does bundle:list -s -t 0 for example, a lot columns
> >>> contains only ?-characters (question marks). Also scr:list looks bad
> >>> under it.
> >>>
> >>> - Eric L
> >>>
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: Consider KARAF-5934 for Karaf 4.2.2?

[Eric Lilja]

Hi, see my replies at relevant places below!

On 2018-12-02 21:03, Jean-Baptiste Onofré wrote:

Hi Eric,

The update to maven-bundle-plugin 4.1.0 introduces some other changes 
(as the requirements/capabilities created are extended). Why do you 
need this for 4.2.2 ? It's transparent for you as user.
So I will try but without strong commitment. Reasonably, I would 
prefer to target in 4.2.3 as I'm planning 4.2.2 for this week. So, it 
will be a best effort.


Okay, I see, I bumped to that version for my projects without issue so I 
thought it was straight-forward.




Yes, deploy folder is enabled by default. Did you deploy a bundle or a 
raw jar ?


It was one of my bundles, built using maven-bundle-plugin 4.1.0. I have 
no troubles provisioning it programmatcially when using Karaf/Pax-Exam. 
I also tried with a 3PP found on Maven central. The deploy folder 
doesn't seem to be active on Windows. It was working fine on Windows a 
couple of versions (of Karaf) ago.




The line breaks should be fixed already (you can test on 4.2.2-SNAPSHOT).


Ah, nice to hear! Could you try on your end Windows with TakeCommand to 
see about the question-mark-thingie? I also recall a DOS .bat-file error 
being reported by TakeCommand as I launched karaf.bat


- Eric L



Regards
JB

On 02/12/2018 20:15, Eric Lilja wrote:
Hi, is it possible to consider including KARAF-5934 for 4.2.2? I saw 
it was just tentatively postponed to 4.2.3.


Also, is the deploy folder enabled by default? I downloaded the 
binary distribution (version 4.2.1), and created a new instance with 
feature scr enabled. Everything else vanilla. I put a bundle in the 
deploy folder but it doesn't get installed, no interesting output 
from log:tail either, so no failures. Just like the directory was not 
monitored at all (I did use the deploy directory in the instance I 
created).


Furthermore, output from scr:list seems to lack line breaks. This is 
under Windows, with Cygwin (Mintty) as terminal. Also tried with 
TakeCommand under Windows, which used to work really well with Karaf, 
but when one does bundle:list -s -t 0 for example, a lot columns 
contains only ?-characters (question marks). Also scr:list looks bad 
under it.


- Eric L

Consider KARAF-5934 for Karaf 4.2.2?

[Eric Lilja]

Hi, is it possible to consider including KARAF-5934 for 4.2.2? I saw it 
was just tentatively postponed to 4.2.3.


Also, is the deploy folder enabled by default? I downloaded the binary 
distribution (version 4.2.1), and created a new instance with feature 
scr enabled. Everything else vanilla. I put a bundle in the deploy 
folder but it doesn't get installed, no interesting output from log:tail 
either, so no failures. Just like the directory was not monitored at all 
(I did use the deploy directory in the instance I created).


Furthermore, output from scr:list seems to lack line breaks. This is 
under Windows, with Cygwin (Mintty) as terminal. Also tried with 
TakeCommand under Windows, which used to work really well with Karaf, 
but when one does bundle:list -s -t 0 for example, a lot columns 
contains only ?-characters (question marks). Also scr:list looks bad 
under it.


- Eric L

Two more interesting bumps for Karaf 4.2.1

[Eric Lilja]

These include: EclipseLink 2.7.3 and org.apache.felix.scr 2.1.2

Any possibility they could be included? I suspect the vote is imminent 
since I noticed the Pax Web upgrade was just resolved.


- EL

Re: Latest configadmin in Karaf 4.2.1

[Eric Lilja]

That's great news, thanks! 4.2.1 is shaping up to be a killer release by 
the looks of it, can't wait until it arrives!


- EL

On 2018-08-05 20:39, Jean-Baptiste Onofré wrote:

https://issues.apache.org/jira/browse/KARAF-5859 ;)

By the way, I'm adding the new examples in the itests and polishing
examples themselves and dev guide a bit and I will submit the release to
vote.

Regards
JB

On 05/08/2018 17:47, Eric Lilja wrote:

Ah, very nice to see, thanks for your awesome work! Any chance to get
the latest hibernate validator as well (6.0.11.Final)?

- EL

On 2018-08-05 17:38, Jean-Baptiste Onofré wrote:

See:

https://issues.apache.org/jira/browse/KARAF-5858

The PR is on the way.

Regards
JB

On 05/08/2018 13:31, Eric Lilja wrote:

Hi, many of us are highly anticipating the upcoming Karaf 4.2.1 release!
Thanks for all your work to those involved! It is possible it could
include the newly released org.apache.felix.configadmin version 1.9.4?

Best wishes to all

- EL

Re: Latest configadmin in Karaf 4.2.1

[Eric Lilja]

Ah, very nice to see, thanks for your awesome work! Any chance to get 
the latest hibernate validator as well (6.0.11.Final)?


- EL

On 2018-08-05 17:38, Jean-Baptiste Onofré wrote:

See:

https://issues.apache.org/jira/browse/KARAF-5858

The PR is on the way.

Regards
JB

On 05/08/2018 13:31, Eric Lilja wrote:

Hi, many of us are highly anticipating the upcoming Karaf 4.2.1 release!
Thanks for all your work to those involved! It is possible it could
include the newly released org.apache.felix.configadmin version 1.9.4?

Best wishes to all

- EL

Latest configadmin in Karaf 4.2.1

[Eric Lilja]

Hi, many of us are highly anticipating the upcoming Karaf 4.2.1 release! 
Thanks for all your work to those involved! It is possible it could 
include the newly released org.apache.felix.configadmin version 1.9.4?


Best wishes to all

- EL

Re: newer felix

[Eric Lilja]

But looking at the release notes for Karaf 3.0.5, which was just put up 
for voting, none of the felix-dependencies seem to have been updated? I 
didn't see a pax-url bump either for Karaf 3.0.5, which would have been 
nice.


- Eric L

On 2015-09-08 06:40, Jean-Baptiste Onofré wrote:

I'm updating most of the dependencies for the next Karaf 3.0.5 and 4.0.2
releases. They should be on vote end of this week or next week.

Regards
JB

On 09/08/2015 02:50 AM, Benson Margulies wrote:

What's the plan for a release of Karaf with newer, for example, felix
SCR?