Re: [VOTE] Apache Karaf runtime 4.4.1 release

[Oliver Lietz]

On Sunday, 10 July 2022 19:24:41 CEST Jean-Baptiste Onofré wrote:
> Hi guys,
> 
> I submit Apache Karaf runtime 4.4.1 release to your vote.
> 
> This release is a maintenance release bringing a lot of dependency
> updates and fixes.
> Especially, this release includes:
> - fix on the exported system packages
> - fix on the config management in features service
> - upgrade to Pax Web 8.0.6, Pax URL 2.6.11, Pax Logging 2.1.3
> - upgrade to OSGi frameworks (both Felix Framework 7.0.5 and Equinox 3.18.0)
> - upgrade to Spring 5.3.21 and 5.2.22.RELEASE
> 
> You can take a look on the Release Notes for details:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140
> rsion=12351548
> 
> Maven Staging Repository:
> https://repository.apache.org/content/repositories/orgapachekaraf-1176/
> 
> Dist Staging Repository:
> https://dist.apache.org/repos/dist/dev/karaf/4.4.1/
> 
> Git tag:
> karaf-4.4.1

+1

O.

Re: [VOTE] Apache Karaf runtime 4.4.0 release

[Oliver Lietz]

On Tuesday, 19 April 2022 08:24:18 CEST Jean-Baptiste Onofré wrote:
> Hi guys,
> 
> I submit Apache Karaf runtime 4.4.0 release to your vote.
> This release is a new milestone, starting the 4.4.x series.
> 
> This release includes:
> - OSGi R8 support
> - Pax Web 8.x upgrade
> - Pax Logging 2.1.x upgrade
> - and much much more !
> 
> You can take a look on the Release Notes for details:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140
> rsion=12349243
> 
> Maven Staging Repository:
> https://repository.apache.org/content/repositories/orgapachekaraf-1173/
> 
> Dist Staging Repository:
> https://dist.apache.org/repos/dist/dev/karaf/4.4.0/
> 
> Git tag:
> karaf-4.4.0

+1

O.

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

[Oliver Lietz]

On Wednesday, 15 December 2021 05:43:44 CET JB Onofré wrote:
> Hi everyone,
> 
> I submit Apache Karaf runtime 4.3.4 to your vote (take #3).
> 
> This release includes dependency upgrades, fixes, and improvements,
> especially:
> 
> - upgrade to Pax Logging 2.0.12, upgrading to log4j2 2.0.15, fixing
> important security issue (CVE-2021-44228) and fixing JNDI issue - align
> dependencies versions between Karaf and Pax *
> - fix missing system export packages
> - fix on Karaf features json support
> - fix features autoRefresh configuration handling
> - fix on sshd session handling
> - update to sshd 2.8.0
> - lot of pax * updates
> - and much more !
> 
> Please take a look on Release Notes for details !
> 
> Release Notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140
> rsion=12350547
> 
> Staging Maven Repository:
> https://repository.apache.org/content/repositories/orgapachekaraf-1165/
> 
> Staging Dist Repository:
> https://dist.apache.org/repos/dist/dev/karaf/4.3.4/
> 
> Git tag:
> karaf-4.3.4

+1

O.

Re: [VOTE] Apache Karaf runtime 4.3.2 release

[Oliver Lietz]

On Sunday, 9 May 2021 07:18:44 CEST Jean-Baptiste Onofre wrote:
> Hi everyone,
> 
> I submit Apache Karaf runtime 4.3.2 to your vote.
> 
> This release includes bunch of dependency upgrades, fixes, and improvements,
> especially:
> 
> - upgrade to xbean 4.19 fixing JDK9 style war file
> - improvements on scheduler to support array configuration
> - fix on the JSON configuration to support array
> - improvement on JSON configuration to support R7 factory style
> - fix on the default pax-logging layout pattern
> - fix on the JMX RMI to use the configured host
> - fix race condition on SSHd startup
> - improvement on ShellTable
> - bunch of dependency updates for fixes and CVE
> - and much more !
> 
> *NOTE: for security reason, the default karaf user is commented in
> etc/users.properties file. Please uncomment and change password if you want
> to use it (for remote access like ssh, jmx, …).*
> 
> Please take a look on Release Notes for details !
> 
> Release Notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311140
> rsion=12349968
>  version=12349968>
> 
> Staging Maven Repository:
> https://repository.apache.org/content/repositories/orgapachekaraf-1156/
> 
> 
> Staging Dist Repository:
> https://dist.apache.org/repos/dist/dev/karaf/4.3.2/
> 
> 
> Git tag:
> karaf-4.3.2
> 
> 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.

+1

O.

Re: More often releases/back on regular pace

[Oliver Lietz]

On Wednesday, October 7, 2020 8:55:44 AM CEST Romain Manni-Bucau wrote:
> Hi JB,
> 
> Think one key point for this ambition is to be able to ensure releases
> don't depend on a single man (whatever his quality is ;)).
> Checking on apache index it seems around 3-4 PMC are active (I can be wrong
> since I don't follow the list accurately from very long so happy if it is
> more), what about having planned (each two months?) releases and rotating
> in the PMC for the releases? The big advantage is that it enables fallbacks
> when needed and avoids to put pressure on a single man which is also a
> positive sign community wide and for the project IMHO. It can also enable
> to highlight that some points can be too hard and needs some love (not sure
> if accurate but thinking out loud it can be to split the repo in smaller
> ones to make releases easier, to make the build parallelizable, to automate
> dist upload, to automate site update with a "main" or script, etc...).
> 
> Hope it makes some sense.

+1

I would like to see a focus on OSGi Spec. R7 is from April 2018 but still not 
fully implemented (yes, I know it's an enterprise runtime not only OSGi). 
Everything else should come after anyhow.

Regards,
O.


> Just my 2cts indeed.
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Blog
>  | Github 
> | LinkedIn  | Book
>  >
> 
> 
> Le mer. 7 oct. 2020 à 06:13, Jean-Baptiste Onofre  a
> 
> écrit :
> > Hi guys,
> > 
> > I would like to be back on more regular/stable release cycle for Karaf.
> > Again, I was a little bit too ambitious in release content and it means
> > that releases have been postponed several times.
> > That’s not good and we should have some more stable/regular: my bad.
> > 
> > So, now, the release should be more driven by time more than content.
> > Starting from now, I will try to keep regular releases.
> > It’s very important in the new Karaf direction, given the opportunity to
> > include more regularly coming features.
> > 
> > Thanks,
> > Regards
> > JB

Re: [HEADS UP] Apache Karaf runtime 4.2.9 & 4.3.0.RC2 releases

[Oliver Lietz]

On Thursday, April 9, 2020 9:10:59 AM CEST Francois Papon wrote:
> Thanks Grzegorz for dealing with PaxWeb!

+1

Would like to see Web Console 4.4.0 and support for R7 configurations in RC2.

Regards,
O.


> regards,
> 
> François
> fpa...@apache.org
> 
> Le 09/04/2020 à 06:55, Grzegorz Grzybek a écrit :
> > Hello
> > 
> > Good idea. However Pax Web 8 is still far from candidate release... But
> > I'm
> > really working hard on it. It turned out that Pax Web 7's "model" had to
> > be
> > rewritten entirely. Just see this test scenario I've implemented in Pax
> > Web
> > 8 (and it's working!):
> > 
> > assertThat(get(port, "/c1/s"), endsWith("my.id=1"));
> > assertThat(get(port, "/c2/s"), endsWith("my.id=1"));
> > assertThat(get(port, "/c3/s"), endsWith("my.id=2"));
> > 
> > // servlet#5 registered to /c2 and /c4 - ranked higher than s#1 in /c2,
> > so:
> > //  - s#1 is deactivated in /c1 and /c2
> > //  - s#3 is activated in /c1
> > //  - s#5 MAY be activated in /c2 and /c4, but in /c2, s#4 is ranked
> > higher
> > than s#5
> > //  - s#4 is ranked lower than s#2 in /c3, so it won't be activated
> > ANYWHERE //  - s#5 will thus be activated in /c2 and /c4
> > wc.doRegisterServlet(Arrays.asList(wcc2, wcc4), new ServletModel.Builder()
> > 
> >  .withServletName("s1")
> >  .withUrlPatterns(new String[] { "/s" })
> >  .withServletReference(s15)
> >  .withServiceRankAndId(1, ++serviceId)
> >  .build());
> > 
> > assertThat(get(port, "/c1/s"), endsWith("my.id=3"));
> > assertThat(get(port, "/c2/s"), endsWith("my.id=5"));
> > assertThat(get(port, "/c3/s"), endsWith("my.id=2"));
> > assertThat(get(port, "/c4/s"), endsWith("my.id=5"));
> > 
> > // servlet#2 unregistered, s#4 can be activated in /c3 and can be
> > activated
> > in /c2 because s#5 in /c2 is ranked
> > // lower than s#4, so s#5 disabled in /c4, so s#6 enabled in /c4
> > wc.doUnregisterServlet(new ServletModel.Builder()
> > 
> >  .withServletReference(s12)
> >  .withOsgiContextModel(cm3)
> >  .remove());
> > 
> > assertTrue(get(port, "/c1/s").endsWith("my.id=3"));
> > assertTrue(get(port, "/c2/s").endsWith("my.id=4"));
> > assertTrue(get(port, "/c3/s").endsWith("my.id=4"));
> > assertTrue(get(port, "/c4/s").endsWith("my.id=6"));
> > 
> > Yes - this directly stems from R7 Whiteboard specification. Single servlet
> > registration may always lead to re-registration avalanche.
> > 
> > So please give me a bit more time with Pax Web 8.
> > 
> > regards
> > Grzegorz Grzybek
> > 
> > czw., 9 kwi 2020 o 06:47 Jean-Baptiste Onofre  
napisał(a):
> >> Hi everyone,
> >> 
> >> Now that jline 3.14.1 and Felix Gogo Kline 1.1.6 have been released, the
> >> "paste" issue in Karaf terminal and issue with "core" commands (man,
> >> history, more, less, …) are now fixed.
> >> 
> >> I would like to cut Karaf runtime 4.2.9 and 4.3.0.RC2. They won’t include
> >> all Jira targeted now (I’m doing a triage right now), but they will be
> >> maintenance releases to address issues mentioned above.
> >> 
> >> No objection ?
> >> 
> >> Regards
> >> JB

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

[Oliver Lietz]

On Monday 17 December 2018 15:49:52 Jean-Baptiste Onofré wrote:
> Oh by the way, you have to update to Pax Exam 4.13.1 where I already did
> the KARAF_LOG addition.

Updating to 4.13.1 fixed the log issue.

Thanks, JB!

O.

> Regards
> JB
> 
> On 17/12/2018 13:38, Oliver Lietz wrote:
> > On Sunday 16 December 2018 11:11:06 Jean-Baptiste Onofré wrote:
> >> Hi all,
> > 
> > Hi,
> > 
> >> Finally, after different new fixes and third party releases, I'm glad to
> >> submit Karaf (runtime) 4.2.2 release to your vote. This is a major
> >> maintenance release for 4.2.x series, bringing a lot of fixes &
> >> improvements.
> >> 
> >> Release Notes:
> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12343458
> >> roj ectId=12311140
> >> 
> >> Staging Repository:
> >> https://repository.apache.org/content/repositories/orgapachekaraf-1123/
> >> 
> >> Git Tag:
> >> karaf-4.2.2
> >> 
> >> 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.
> > 
> > I see several issues in Karaf build and Sling/Karaf ITs.
> > 
> > Karaf build:
> > 
> > [INFO] Results:
> > [INFO]
> > [ERROR] Errors:
> > [ERROR]   JmsTest.testCommands » NotBound
> > ef29bfce-4ace-4ea4-8529-9b0255ab485c [ERROR]   JmsTest.testMBean »
> > NotBound 94e3f2b8-8ba2-45c1-92d3-9ec1f7933258 [ERROR]  
> > ServletExampleTest.testWithAnnotation:76->verify:49 » Connect Connection
> > refus...
> > [INFO]
> > [ERROR] Tests run: 265, Failures: 0, Errors: 3, Skipped: 5
> > [INFO]
> > [INFO]
> > 
> > [INFO] Reactor Summary for Apache Karaf 4.2.2:
> > 
> > Sling/Karaf ITs:
> > 
> > java.lang.RuntimeException: /karaf.log (Permission denied)
> > 
> > at
> > 
> > org.apache.karaf.main.util.BootstrapLogManager.getDefaultHandlerInternal(B
> > ootstrapLogManager.java:102)> 
> > at
> > 
> > org.apache.karaf.main.util.BootstrapLogManager.getDefaultHandlersInternal(
> > BootstrapLogManager.java:137)> 
> > at
> > 
> > org.apache.karaf.main.util.BootstrapLogManager.getDefaultHandlers(Bootstra
> > pLogManager.java:70)> 
> > at
> > 
> > org.apache.karaf.main.util.BootstrapLogManager.configureLogger(BootstrapLo
> > gManager.java:75)> 
> > at org.apache.karaf.main.Main.launch(Main.java:244)
> > at org.apache.karaf.main.Main.main(Main.java:178)
> > 
> > Caused by: java.io.FileNotFoundException: /karaf.log (Permission denied)
> > 
> > at java.io.FileOutputStream.open0(Native Method)
> > at java.io.FileOutputStream.open(FileOutputStream.java:270)
> > at java.io.FileOutputStream.(FileOutputStream.java:213)
> > at
> > 
> > org.apache.karaf.main.util.BootstrapLogManager$SimpleFileHandler.open(Boot
> > strapLogManager.java:193)> 
> > at
> > 
> > org.apache.karaf.main.util.BootstrapLogManager$SimpleFileHandler.(Bo
> > otstrapLogManager.java:182)> 
> > at
> > 
> > org.apache.karaf.main.util.BootstrapLogManager.getDefaultHandlerInternal(B
> > ootstrapLogManager.java:100)> 
> > ... 5 more
> > 
> > java.lang.RuntimeException: /karaf.log (Permission denied)
> > 
> > at
> > 
> > org.apache.karaf.main.util.BootstrapLogManager.getDefaultHandlerInternal(B
> > ootstrapLogManager.java:102)> 
> > at
> > 
> > org.apache.karaf.main.util.BootstrapLogManager.getDefaultHandlersInternal(
> > BootstrapLogManager.java:137)> 
> > at
> > 
> > org.apache.karaf.main.util.BootstrapLogManager.getDefaultHandlers(Bootstra
> > pLogManager.java:70)> 
> > at
> > 
> > org.apache.karaf.main.util.BootstrapLogManager.configureLogger(BootstrapLo
> > gManager.java:75)> 
> > at
> > 
> > org.apache.karaf.main.KarafActivatorManager.(KarafActivatorManager.j
> > ava:48)> 
> > at org.apache.karaf.main.Main.launch(Main.java:280)
> > at org.apache.karaf.main.Main.main(Main.java:178)
> > 
> > Caused by: java.io.FileNotFoundException: /karaf.log (Permission denied)
> > 
> > at java.io.FileOutputStream.open0(Native Method)
> > at java.io.FileOutputStr

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

[Oliver Lietz]

On Sunday 16 December 2018 11:11:06 Jean-Baptiste Onofré wrote:
> Hi all,

Hi,

> Finally, after different new fixes and third party releases, I'm glad to
> submit Karaf (runtime) 4.2.2 release to your vote. This is a major
> maintenance release for 4.2.x series, bringing a lot of fixes &
> improvements.
> 
> Release Notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12343458
> ectId=12311140
> 
> Staging Repository:
> https://repository.apache.org/content/repositories/orgapachekaraf-1123/
> 
> Git Tag:
> karaf-4.2.2
> 
> 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.

I see several issues in Karaf build and Sling/Karaf ITs.

Karaf build:

[INFO] Results:
[INFO] 
[ERROR] Errors: 
[ERROR]   JmsTest.testCommands » NotBound ef29bfce-4ace-4ea4-8529-9b0255ab485c
[ERROR]   JmsTest.testMBean » NotBound 94e3f2b8-8ba2-45c1-92d3-9ec1f7933258
[ERROR]   ServletExampleTest.testWithAnnotation:76->verify:49 » Connect 
Connection refus...
[INFO] 
[ERROR] Tests run: 265, Failures: 0, Errors: 3, Skipped: 5
[INFO] 
[INFO] 

[INFO] Reactor Summary for Apache Karaf 4.2.2:

Sling/Karaf ITs:

java.lang.RuntimeException: /karaf.log (Permission denied)
at 
org.apache.karaf.main.util.BootstrapLogManager.getDefaultHandlerInternal(BootstrapLogManager.java:102)
at 
org.apache.karaf.main.util.BootstrapLogManager.getDefaultHandlersInternal(BootstrapLogManager.java:137)
at 
org.apache.karaf.main.util.BootstrapLogManager.getDefaultHandlers(BootstrapLogManager.java:70)
at 
org.apache.karaf.main.util.BootstrapLogManager.configureLogger(BootstrapLogManager.java:75)
at org.apache.karaf.main.Main.launch(Main.java:244)
at org.apache.karaf.main.Main.main(Main.java:178)
Caused by: java.io.FileNotFoundException: /karaf.log (Permission denied)
at java.io.FileOutputStream.open0(Native Method)
at java.io.FileOutputStream.open(FileOutputStream.java:270)
at java.io.FileOutputStream.(FileOutputStream.java:213)
at 
org.apache.karaf.main.util.BootstrapLogManager$SimpleFileHandler.open(BootstrapLogManager.java:193)
at 
org.apache.karaf.main.util.BootstrapLogManager$SimpleFileHandler.(BootstrapLogManager.java:182)
at 
org.apache.karaf.main.util.BootstrapLogManager.getDefaultHandlerInternal(BootstrapLogManager.java:100)
... 5 more
java.lang.RuntimeException: /karaf.log (Permission denied)
at 
org.apache.karaf.main.util.BootstrapLogManager.getDefaultHandlerInternal(BootstrapLogManager.java:102)
at 
org.apache.karaf.main.util.BootstrapLogManager.getDefaultHandlersInternal(BootstrapLogManager.java:137)
at 
org.apache.karaf.main.util.BootstrapLogManager.getDefaultHandlers(BootstrapLogManager.java:70)
at 
org.apache.karaf.main.util.BootstrapLogManager.configureLogger(BootstrapLogManager.java:75)
at 
org.apache.karaf.main.KarafActivatorManager.(KarafActivatorManager.java:48)
at org.apache.karaf.main.Main.launch(Main.java:280)
at org.apache.karaf.main.Main.main(Main.java:178)
Caused by: java.io.FileNotFoundException: /karaf.log (Permission denied)
at java.io.FileOutputStream.open0(Native Method)
at java.io.FileOutputStream.open(FileOutputStream.java:270)
at java.io.FileOutputStream.(FileOutputStream.java:213)
at 
org.apache.karaf.main.util.BootstrapLogManager$SimpleFileHandler.open(BootstrapLogManager.java:193)
at 
org.apache.karaf.main.util.BootstrapLogManager$SimpleFileHandler.(BootstrapLogManager.java:182)
at 
org.apache.karaf.main.util.BootstrapLogManager.getDefaultHandlerInternal(BootstrapLogManager.java:100)
... 6 more
java.lang.RuntimeException: /karaf.log (Permission denied)
at 
org.apache.karaf.main.util.BootstrapLogManager.getDefaultHandlerInternal(BootstrapLogManager.java:102)
at 
org.apache.karaf.main.util.BootstrapLogManager.getDefaultHandlersInternal(BootstrapLogManager.java:137)
at 
org.apache.karaf.main.util.BootstrapLogManager.getDefaultHandlers(BootstrapLogManager.java:70)
at 
org.apache.karaf.main.util.BootstrapLogManager.configureLogger(BootstrapLogManager.java:75)
at 
org.apache.karaf.main.lock.SimpleFileLock.(SimpleFileLock.java:40)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at org.apache.karaf.main.Main.createLock(Main.java:496)
at org.apache.karaf.main.Main.doMonitor(Main.java:388)
at org.apache.karaf.main.Main.access$100(Main.java:74)
at org.apache.karaf.main.Main$3.run(Main.java:377)
Caused by: java.io.FileNotFoundException: /karaf.log (Permission denied)
  

Re: [HEADS UP] Preparing Apache Karaf 4.2.0 GA

[Oliver Lietz]

On Monday 19 February 2018 05:58:31 Jean-Baptiste Onofré wrote:
> Hi guys,

Hi,

> After 4.2.0.M1 & 4.2.0.M2, I think it's time to do the first 4.2.0 GA.
> 
> I have three actions on the way:
> 
> 1. Upgrade to Pax Web 7 with Jetty 9.4 support. I started Pax Web/Jetty part
> on a local branch. I hope to have something this week around that. It takes
> a little bit of time because the Jetty API slightly changed (as usual).
> This point is a blocker and 4.2.0 needs it. If you think it's worth to have
> a 4.2.0.M3 with this update, please let me know.

+1 for M3 with Pax Web 7

> 2. Merge karaf-docker feature branch. It's something that we discussed days
> ago. I updated and cleanup the code for donation. Not blocker but good to
> have. 3. Merge examples branch. In order to allow users to easily start
> with Karaf, François and I are working on a set of examples
> (https://github.com/jbonofre/karaf/tree/DEV_GUIDE/examples). The idea is to
> include those examples in the Karaf distribution, linked them in the
> developer guide. At the end, I would like to add itests using these
> examples as well, allowing us to detect regression. Again not a blocker,
> but good to have. Please, let me know what you are thinking about the
> examples. Some examples are in development (take a look in the examples
> pom.xml for the list of examples).
> 
> Roughly, I would like to cut 4.2.0 in 2 weeks or so.

Thanks, JB!

O.

> Regards
> JB

Re: [VOTE] Apache Karaf 4.2.0.M2 release

[Oliver Lietz]

On Friday 29 December 2017 09:57:05 Jean-Baptiste Onofré wrote:
> Hi all
> 
> I submit Karaf 4.2.0.M2 release to your vote. Like 4.2.0.M1, it's not a
> GA release but a second technical preview. The purpose is to continue
> the test campaign before the first GA Release.
> Compared to 4.2.0.M1 we did lot of bug fixes and improved the Java 9
> support. 4.2.0.M2 is probably the last technical preview before the
> 4.2.0 GA.

+1 (built from tag, works fine with Apache Sling on Java 8 – all ITs pass)

Thanks, JB!

O.

Re: [DISCUSS] Trim down karaf distributions for 4.2

[Oliver Lietz]

On Wednesday 11 October 2017 16:04:47 Jean-Baptiste Onofré wrote:
> By the way, we provide nightly build of 4.2.0-SNAPSHOT if you want already
> try.

I'm already preparing for 4.2 with snapshots, see e.g. SLING-7010 but 
snapshots are a moving target and no option for early adopters (aka guinea 
pigs) without access to Apache snapshots repo.

Regards,
O.

> Regards
> JB
> 
> On 10/11/2017 03:58 PM, Oliver Lietz wrote:
> > On Wednesday 11 October 2017 15:43:34 Jean-Baptiste Onofré wrote:
> >> Yeah, but we postponed due to the Java9 issue in dependencies.
> >> 
> >> We are focused on 4.1.3 right now, but 4.2.0.M1 should happen just after.
> > 
> > Having milestones regularly would help to fix issues one by one (or at
> > least in small units) when doing major upgrades – the upgrade from 3 to 4
> > was a pain which I really would like to avoid when upgrading to 4.2. So
> > having a current milestone without (breaking) changes for Java 9 is much
> > appreciated.
> > 
> > Thanks,
> > O.
> > 
> >> Regards
> >> JB
> >> 
> >> On 10/11/2017 03:41 PM, Oliver Lietz wrote:
> >>> On Wednesday 11 October 2017 15:21:52 Jean-Baptiste Onofré wrote:
> >>>> Hi OLiver,
> >>> 
> >>> Hi JB,
> >>> 
> >>>> The idea is to cut a Milestone1 release as soon as we have a rough
> >>>> Java9
> >>>> support.
> >>> 
> >>> well, 4.2.0.M1 was planned for second week of August... ;)
> >>> 
> >>> Regards,
> >>> O.
> >>> 
> >>>> Regards
> >>>> JB
> >>>> 
> >>>> On 10/11/2017 03:19 PM, Oliver Lietz wrote:
> >>>>> On Wednesday 11 October 2017 15:00:41 Guillaume Nodet wrote:
> >>>>>> The point that makes me raise this problem is that the karaf default
> >>>>>> distribution uses the Apache versions of xerces and xalan.  Fwiw, the
> >>>>>> latest xerces release is from 2011 and the latest xalan from 2014, so
> >>>>>> they're not the most active.  In particular, xalan latest release
> >>>>>> does
> >>>>>> not
> >>>>>> implement jaxp 1.4.
> >>>>>> 
> >>>>>> One additional point is that those libraries stuff is broken on Java
> >>>>>> 9,
> >>>>>> so
> >>>>>> one option would be to remove it alltogether which bring us much
> >>>>>> closer
> >>>>>> to
> >>>>>> Java 9 support ;-)  Seriously, I'm not sure I want to spend too much
> >>>>>> time
> >>>>>> allowing pluggability for specs/implementations while the only real
> >>>>>> implementation provider is the JDK itself.  That's really a lot of
> >>>>>> work
> >>>>>> for
> >>>>>> no real benefit.
> >>>>>> 
> >>>>>> In addition, the default distribution still install some "legacy"
> >>>>>> features
> >>>>>> such as aries-blueprint, shell-compat, etc...
> >>>>>> 
> >>>>>> So here's a list of propositions for 4.2:
> >>>>>>  * remove all libraries for specs / impls from apache-karaf
> >>>>>>  distro
> >>>>>>  * remove support for endorsed / ext libraries in the 
> >>>>>>  element
> >>>>>> 
> >>>>>> and wherever used
> >>>>>> 
> >>>>>>  * remove aries-blueprint and shell-compat from default distro
> >>>>>>  * remove a few features from the karaf-minimal distro. I'm not
> >>>>>>  sure
> >>>>>>  which
> >>>>>> 
> >>>>>> one exactly, but I think we should get the zip under 10 Mb.  Maybe
> >>>>>> only
> >>>>>> keeping jaas, shell, feature, ssh, bundle, config, deployer and log,
> >>>>>> also
> >>>>>> removing equinox / logback bundles...
> >>>>>> 
> >>>>>> Thoughts ?
> >>>>> 
> >>>>> +1
> >>>>> 
> >>>>> And again, I would like to see some milestones before going final/GA
> >>>>> to
> >>>>> move Apache Sling to 4.2 ASAP.
> >>>>> 
> >>>>> Thanks,
> >>>>> O.

Re: [DISCUSS] Trim down karaf distributions for 4.2

[Oliver Lietz]

On Wednesday 11 October 2017 15:43:34 Jean-Baptiste Onofré wrote:
> Yeah, but we postponed due to the Java9 issue in dependencies.
> 
> We are focused on 4.1.3 right now, but 4.2.0.M1 should happen just after.

Having milestones regularly would help to fix issues one by one (or at least 
in small units) when doing major upgrades – the upgrade from 3 to 4 was a pain 
which I really would like to avoid when upgrading to 4.2. So having a current 
milestone without (breaking) changes for Java 9 is much appreciated.

Thanks,
O.

> Regards
> JB
> 
> On 10/11/2017 03:41 PM, Oliver Lietz wrote:
> > On Wednesday 11 October 2017 15:21:52 Jean-Baptiste Onofré wrote:
> >> Hi OLiver,
> > 
> > Hi JB,
> > 
> >> The idea is to cut a Milestone1 release as soon as we have a rough Java9
> >> support.
> > 
> > well, 4.2.0.M1 was planned for second week of August... ;)
> > 
> > Regards,
> > O.
> > 
> >> Regards
> >> JB
> >> 
> >> On 10/11/2017 03:19 PM, Oliver Lietz wrote:
> >>> On Wednesday 11 October 2017 15:00:41 Guillaume Nodet wrote:
> >>>> The point that makes me raise this problem is that the karaf default
> >>>> distribution uses the Apache versions of xerces and xalan.  Fwiw, the
> >>>> latest xerces release is from 2011 and the latest xalan from 2014, so
> >>>> they're not the most active.  In particular, xalan latest release does
> >>>> not
> >>>> implement jaxp 1.4.
> >>>> 
> >>>> One additional point is that those libraries stuff is broken on Java 9,
> >>>> so
> >>>> one option would be to remove it alltogether which bring us much closer
> >>>> to
> >>>> Java 9 support ;-)  Seriously, I'm not sure I want to spend too much
> >>>> time
> >>>> allowing pluggability for specs/implementations while the only real
> >>>> implementation provider is the JDK itself.  That's really a lot of work
> >>>> for
> >>>> no real benefit.
> >>>> 
> >>>> In addition, the default distribution still install some "legacy"
> >>>> features
> >>>> such as aries-blueprint, shell-compat, etc...
> >>>> 
> >>>> So here's a list of propositions for 4.2:
> >>>> * remove all libraries for specs / impls from apache-karaf distro
> >>>> * remove support for endorsed / ext libraries in the 
> >>>> element
> >>>> 
> >>>> and wherever used
> >>>> 
> >>>> * remove aries-blueprint and shell-compat from default distro
> >>>> * remove a few features from the karaf-minimal distro. I'm not sure
> >>>> which
> >>>> 
> >>>> one exactly, but I think we should get the zip under 10 Mb.  Maybe only
> >>>> keeping jaas, shell, feature, ssh, bundle, config, deployer and log,
> >>>> also
> >>>> removing equinox / logback bundles...
> >>>> 
> >>>> Thoughts ?
> >>> 
> >>> +1
> >>> 
> >>> And again, I would like to see some milestones before going final/GA to
> >>> move Apache Sling to 4.2 ASAP.
> >>> 
> >>> Thanks,
> >>> O.

Re: [DISCUSS] Trim down karaf distributions for 4.2

[Oliver Lietz]

On Wednesday 11 October 2017 15:21:52 Jean-Baptiste Onofré wrote:
> Hi OLiver,

Hi JB,

> The idea is to cut a Milestone1 release as soon as we have a rough Java9
> support.

well, 4.2.0.M1 was planned for second week of August... ;)

Regards,
O.

> Regards
> JB
> 
> On 10/11/2017 03:19 PM, Oliver Lietz wrote:
> > On Wednesday 11 October 2017 15:00:41 Guillaume Nodet wrote:
> >> The point that makes me raise this problem is that the karaf default
> >> distribution uses the Apache versions of xerces and xalan.  Fwiw, the
> >> latest xerces release is from 2011 and the latest xalan from 2014, so
> >> they're not the most active.  In particular, xalan latest release does
> >> not
> >> implement jaxp 1.4.
> >> 
> >> One additional point is that those libraries stuff is broken on Java 9,
> >> so
> >> one option would be to remove it alltogether which bring us much closer
> >> to
> >> Java 9 support ;-)  Seriously, I'm not sure I want to spend too much time
> >> allowing pluggability for specs/implementations while the only real
> >> implementation provider is the JDK itself.  That's really a lot of work
> >> for
> >> no real benefit.
> >> 
> >> In addition, the default distribution still install some "legacy"
> >> features
> >> such as aries-blueprint, shell-compat, etc...
> >> 
> >> So here's a list of propositions for 4.2:
> >>* remove all libraries for specs / impls from apache-karaf distro
> >>* remove support for endorsed / ext libraries in the  element
> >> 
> >> and wherever used
> >> 
> >>* remove aries-blueprint and shell-compat from default distro
> >>* remove a few features from the karaf-minimal distro. I'm not sure
> >>which
> >> 
> >> one exactly, but I think we should get the zip under 10 Mb.  Maybe only
> >> keeping jaas, shell, feature, ssh, bundle, config, deployer and log, also
> >> removing equinox / logback bundles...
> >> 
> >> Thoughts ?
> > 
> > +1
> > 
> > And again, I would like to see some milestones before going final/GA to
> > move Apache Sling to 4.2 ASAP.
> > 
> > Thanks,
> > O.

Re: [DISCUSS] Trim down karaf distributions for 4.2

[Oliver Lietz]

On Wednesday 11 October 2017 15:00:41 Guillaume Nodet wrote:
> The point that makes me raise this problem is that the karaf default
> distribution uses the Apache versions of xerces and xalan.  Fwiw, the
> latest xerces release is from 2011 and the latest xalan from 2014, so
> they're not the most active.  In particular, xalan latest release does not
> implement jaxp 1.4.
> 
> One additional point is that those libraries stuff is broken on Java 9, so
> one option would be to remove it alltogether which bring us much closer to
> Java 9 support ;-)  Seriously, I'm not sure I want to spend too much time
> allowing pluggability for specs/implementations while the only real
> implementation provider is the JDK itself.  That's really a lot of work for
> no real benefit.
> 
> In addition, the default distribution still install some "legacy" features
> such as aries-blueprint, shell-compat, etc...
> 
> So here's a list of propositions for 4.2:
>   * remove all libraries for specs / impls from apache-karaf distro
>   * remove support for endorsed / ext libraries in the  element
> and wherever used
>   * remove aries-blueprint and shell-compat from default distro
>   * remove a few features from the karaf-minimal distro. I'm not sure which
> one exactly, but I think we should get the zip under 10 Mb.  Maybe only
> keeping jaas, shell, feature, ssh, bundle, config, deployer and log, also
> removing equinox / logback bundles...
> 
> Thoughts ?

+1

And again, I would like to see some milestones before going final/GA to move 
Apache Sling to 4.2 ASAP.

Thanks,
O.

Re: [INFO] Releases schedule

[Oliver Lietz]

On Thursday 29 June 2017 13:33:32 Jean-Baptiste Onofré wrote:
> Hi guys,

hi,

> just a quick update about the next releases cycle.
> 
> I plan to release Karaf Decanter 1.4.0 during the week end.
> 
> Next week, we plan new releases on 3.0.x, 4.0.x and 4.1.x branches. We will
> update to jline 3.3.1 soon and we have some polishing/fixes in the way.

is there a schedule for 4.2 already? Can you cut some milestones until 4.2.0 
is final?

Thanks,
O.

> Thanks !
> Regards
> JB

Re: Towards Karaf (Container) 4.1.0

[Oliver Lietz]

On Wednesday 18 January 2017 04:48:43 Jean-Baptiste Onofré wrote:
> Oh, I see.
> 
> Regarding the schedule, I'm not sure we will have time to do this for
> Karaf 4.1.0. I would more plan this for 4.1.1.
> 
> The changes are already pretty large in coming 4.1.0.
> 
> Agreed ?

Sure – working around with external config files.

But can you please, please have a look at KARAF-4105 again? 8D

Thanks,
O.

> Regards
> JB
> 
> On 01/18/2017 03:39 AM, Oliver Lietz wrote:
> > On Wednesday 18 January 2017 03:22:31 Jean-Baptiste Onofré wrote:
> >> Hi Oli
> > 
> > Hi JB,
> > 
> >> Not sure I follow you. Cfg file are configadmin files. Do we have a Jira
> >> describing what you mean ?
> > 
> > .cfg is the plain (Java) property file format and .config is the more rich
> > format of Felix ConfigAdmin. Both formats and the differences are
> > described at [2]. KARAF-4346 is related but I guess there should be more
> > issues in JIRA targeting the concrete problems, e.g. features do not
> > support the inlining of ConfigAdmin format configs.
> > 
> > Regards,
> > O.
> > 
> >> Regards
> >> JB⁣​
> >> 
> >> On Jan 18, 2017, 03:20, at 03:20, Oliver Lietz <apa...@oliverlietz.de>
> > 
> > wrote:
> >>> On Thursday 05 January 2017 15:39:19 Jean-Baptiste Onofré wrote:
> >>>> Hi guys,
> >>>> 
> >>>> I started the updates and fixes for Karaf 4.1.0.
> >>>> 
> >>>> As dependencies, we will need Pax Exam 4.10.0 and Pax Web 6.0.1.
> >>> 
> >>> Achim
> >>> 
> >>>> and I will tackle this as it's pre-requisite for 4.1.0.
> >>>> 
> >>>> I plan to create karaf-4.1.x branch next week for a release the
> >>>> following week.
> >>>> 
> >>>> Thoughts ?
> >>> 
> >>> I would like to see full support for configurations in Felix
> >>> Configuration
> >>> Admin format (.config). This feature is essential for Sling on Karaf as
> >>> 
> >>> several components require not only strings in configurations[1], but
> >>> not
> >>> supported in .cfg format [2]. Support for this format in Pax Exam is
> >>> under way
> >>> (PAXEXAM-805).
> >>> 
> >>> For downstream projects (like Sling), early pre-releases would be
> >>> helpful for
> >>> transition. There was some uproar as I had to disable build jobs for
> >>> Sling/Karaf when switching to 4.1-SNAPSHOT ("no external snapshots
> >>> policy") to
> >>> catch up with current Sling (requires R6).
> >>> 
> >>> Regards,
> >>> O.
> >>> 
> >>> [1]
> >>> https://github.com/apache/sling/tree/trunk/karaf/org.apache.sling.karaf-> 
> >>> >>> con
> >>> figs/src/main/resources [2]
> >>> http://sling.apache.org/documentation/bundles/configuration-installer-fa
> >>> cto
> >>> ry.html>
> >>> 
> >>>> Thanks,
> >>>> Regards
> >>>> JB

Re: Towards Karaf (Container) 4.1.0

[Oliver Lietz]

On Wednesday 18 January 2017 03:22:31 Jean-Baptiste Onofré wrote:
> Hi Oli

Hi JB,

> Not sure I follow you. Cfg file are configadmin files. Do we have a Jira
> describing what you mean ?

.cfg is the plain (Java) property file format and .config is the more rich 
format of Felix ConfigAdmin. Both formats and the differences are described at 
[2]. KARAF-4346 is related but I guess there should be more issues in JIRA 
targeting the concrete problems, e.g. features do not support the inlining of 
ConfigAdmin format configs.

Regards,
O.

> Regards
> JB⁣​
> 
> On Jan 18, 2017, 03:20, at 03:20, Oliver Lietz <apa...@oliverlietz.de> 
wrote:
> >On Thursday 05 January 2017 15:39:19 Jean-Baptiste Onofré wrote:
> >> Hi guys,
> >> 
> >> I started the updates and fixes for Karaf 4.1.0.
> >> 
> >> As dependencies, we will need Pax Exam 4.10.0 and Pax Web 6.0.1.
> >
> >Achim
> >
> >> and I will tackle this as it's pre-requisite for 4.1.0.
> >> 
> >> I plan to create karaf-4.1.x branch next week for a release the
> >> following week.
> >> 
> >> Thoughts ?
> >
> >I would like to see full support for configurations in Felix
> >Configuration
> >Admin format (.config). This feature is essential for Sling on Karaf as
> >
> >several components require not only strings in configurations[1], but
> >not
> >supported in .cfg format [2]. Support for this format in Pax Exam is
> >under way
> >(PAXEXAM-805).
> >
> >For downstream projects (like Sling), early pre-releases would be
> >helpful for
> >transition. There was some uproar as I had to disable build jobs for
> >Sling/Karaf when switching to 4.1-SNAPSHOT ("no external snapshots
> >policy") to
> >catch up with current Sling (requires R6).
> >
> >Regards,
> >O.
> >
> >[1]
> >https://github.com/apache/sling/tree/trunk/karaf/org.apache.sling.karaf-con
> >figs/src/main/resources [2]
> >http://sling.apache.org/documentation/bundles/configuration-installer-facto
> >ry.html>
> >> Thanks,
> >> Regards
> >> JB

Re: Towards Karaf (Container) 4.1.0

[Oliver Lietz]

On Thursday 05 January 2017 15:39:19 Jean-Baptiste Onofré wrote:
> Hi guys,
> 
> I started the updates and fixes for Karaf 4.1.0.
> 
> As dependencies, we will need Pax Exam 4.10.0 and Pax Web 6.0.1. Achim
> and I will tackle this as it's pre-requisite for 4.1.0.
> 
> I plan to create karaf-4.1.x branch next week for a release the
> following week.
> 
> Thoughts ?

I would like to see full support for configurations in Felix Configuration 
Admin format (.config). This feature is essential for Sling on Karaf as 
several components require not only strings in configurations[1], but not 
supported in .cfg format [2]. Support for this format in Pax Exam is under way 
(PAXEXAM-805).

For downstream projects (like Sling), early pre-releases would be helpful for 
transition. There was some uproar as I had to disable build jobs for 
Sling/Karaf when switching to 4.1-SNAPSHOT ("no external snapshots policy") to 
catch up with current Sling (requires R6). 

Regards,
O.

[1] 
https://github.com/apache/sling/tree/trunk/karaf/org.apache.sling.karaf-configs/src/main/resources
[2] 
http://sling.apache.org/documentation/bundles/configuration-installer-factory.html


> Thanks,
> Regards
> JB

Re: [K4.1] Pax Logging: Sift appender

[Oliver Lietz]

On Wednesday 18 January 2017 11:03:42 Guillaume Nodet wrote:
> In that case, it might be better to use the same config as previously, i.e.
> route on bundle.name instead of bundle.id.

+1

Thanks,
O.

> 2017-01-18 11:01 GMT+01:00 Jean-Baptiste Onofré <j...@nanthrax.net>:
> > +1
> > 
> > It will do it.
> > 
> > Regards
> > JB⁣​
> > 
> > On Jan 18, 2017, 01:59, at 01:59, Oliver Lietz <apa...@oliverlietz.de>
> > 
> > wrote:
> > >On Wednesday 18 January 2017 10:25:42 Guillaume Nodet wrote:
> > >> I just got it working with something like:
> > >> 
> > >> log4j2.appender.routing.type = Routing
> > >> log4j2.appender.routing.name = Routing
> > >> log4j2.appender.routing.routes.type = Routes
> > >> log4j2.appender.routing.routes.pattern = \$\$\\\{ctx:bundle.id\}
> > >> log4j2.appender.routing.routes.bundle.type = Route
> > >> log4j2.appender.routing.routes.bundle.appender.type =
> > >> RollingRandomAccessFile
> > >> log4j2.appender.routing.routes.bundle.appender.name =
> > >
> > >Bundle-\$\\\{ctx:
> > >> bundle.id\}
> > >> log4j2.appender.routing.routes.bundle.appender.fileName =
> > >> ${karaf.data}/log/bundle-\$\\\{ctx:bundle.id\}.log
> > >> log4j2.appender.routing.routes.bundle.appender.filePattern =
> > >> ${karaf.data}/log/bundle-\$\\\{ctx:bundle.id\}.log.%i
> > >> log4j2.appender.routing.routes.bundle.appender.append = true
> > >> log4j2.appender.routing.routes.bundle.appender.layout.type =
> > >
> > >PatternLayout
> > >
> > >> log4j2.appender.routing.routes.bundle.appender.layout.pattern =
> > >> ${log4j2.pattern}
> > >> log4j2.appender.routing.routes.bundle.appender.policies.type =
> > >
> > >Policies
> > >
> > >> log4j2.appender.routing.routes.bundle.appender.policies.size.type =
> > >> SizeBasedTriggeringPolicy
> > >> log4j2.appender.routing.routes.bundle.appender.policies.size.size =
> > >
> > >8MB
> > >
> > >Thanks, Guillaume. Can you add this appender configuration to Karaf
> > >4.1?
> > >
> > >O.
> > >
> > >> 2017-01-17 23:31 GMT+01:00 mbelling <mbe...@gmail.com>:
> > >> > I am also interested in the sift/MDC configuration in Karaf 4.1.
> > >
> > >Was
> > >
> > >> > there
> > >> > any more progress on this?

Re: [K4.1] Pax Logging: Sift appender

[Oliver Lietz]

On Wednesday 18 January 2017 10:25:42 Guillaume Nodet wrote:
> I just got it working with something like:
> 
> log4j2.appender.routing.type = Routing
> log4j2.appender.routing.name = Routing
> log4j2.appender.routing.routes.type = Routes
> log4j2.appender.routing.routes.pattern = \$\$\\\{ctx:bundle.id\}
> log4j2.appender.routing.routes.bundle.type = Route
> log4j2.appender.routing.routes.bundle.appender.type =
> RollingRandomAccessFile
> log4j2.appender.routing.routes.bundle.appender.name = Bundle-\$\\\{ctx:
> bundle.id\}
> log4j2.appender.routing.routes.bundle.appender.fileName =
> ${karaf.data}/log/bundle-\$\\\{ctx:bundle.id\}.log
> log4j2.appender.routing.routes.bundle.appender.filePattern =
> ${karaf.data}/log/bundle-\$\\\{ctx:bundle.id\}.log.%i
> log4j2.appender.routing.routes.bundle.appender.append = true
> log4j2.appender.routing.routes.bundle.appender.layout.type = PatternLayout
> log4j2.appender.routing.routes.bundle.appender.layout.pattern =
> ${log4j2.pattern}
> log4j2.appender.routing.routes.bundle.appender.policies.type = Policies
> log4j2.appender.routing.routes.bundle.appender.policies.size.type =
> SizeBasedTriggeringPolicy
> log4j2.appender.routing.routes.bundle.appender.policies.size.size = 8MB

Thanks, Guillaume. Can you add this appender configuration to Karaf 4.1?

O.

> 2017-01-17 23:31 GMT+01:00 mbelling :
> > I am also interested in the sift/MDC configuration in Karaf 4.1.  Was
> > there
> > any more progress on this?
> > 
> > 
> > 

[K4.1] Pax Logging: Sift appender

[Oliver Lietz]

hi all,

the sifting appender was removed from org.ops4j.pax.logging.cfg with "Switch 
to log4j v2" (KARAF-4189 and KARAF-4190).

How do I have to configure Pax Logging in Karaf to get back a log per bundle?

Thanks,
O.

Re: [UPDATE] Releases schedule

[Oliver Lietz]

On Thursday 07 July 2016 17:18:15 Jean-Baptiste Onofré wrote:
> Hi Oli,
> 
> yes, it's on my plan.

Thanks, JB. Let me know if there is anything I can do.

Regards,
O.

> Regards
> JB
> 
> On 07/07/2016 09:01 AM, Oliver Lietz wrote:
> > On Sunday 03 July 2016 20:52:39 Jean-Baptiste Onofré wrote:
> >> Hi all,
> > 
> > hi,
> > 
> >> just a quick update about the releases schedule.
> >> 
> >> End of this week and during the week end, I should be able to submit
> >> Cellar 4.0.1 and Decanter 1.1.1 to vote.
> >> 
> >> Karaf Container 4.0.6 and 3.0.8 are planned for end of the following
> >> week.
> > 
> > any chance to get KARAF-4105 and KARAF-4346 fixed for 4.0.6?
> > 
> > Regards,
> > O.
> > 
> >> On the other hand, I worked on couple of PoC around Docker and
> >> karaf-boot. I will give you more details soon.
> >> 
> >> Regards
> >> JB

Re: [UPDATE] Releases schedule

[Oliver Lietz]

On Thursday 07 July 2016 10:32:54 Markus Rathgeb wrote:
> Hi Oliver,

Hi Markus,

> > any chance to get KARAF-4105 and KARAF-4346 fixed for 4.0.6?
> 
> Have you had a change to review my changes / PR for KARAF-4105?

yes, I can successfully build Sling Launchpad Karaf Distribution (using 
${project.version} in Sling Launchpad Karaf Features) with your patch applied.

Patch looks good to me.

O.

> Best regards,
> Markus

Re: [UPDATE] Releases schedule

[Oliver Lietz]

On Sunday 03 July 2016 20:52:39 Jean-Baptiste Onofré wrote:
> Hi all,

hi,

> just a quick update about the releases schedule.
> 
> End of this week and during the week end, I should be able to submit
> Cellar 4.0.1 and Decanter 1.1.1 to vote.
> 
> Karaf Container 4.0.6 and 3.0.8 are planned for end of the following week.

any chance to get KARAF-4105 and KARAF-4346 fixed for 4.0.6?

Regards,
O.

> On the other hand, I worked on couple of PoC around Docker and
> karaf-boot. I will give you more details soon.
> 
> Regards
> JB

Re: Troubles to upgrade from 3.0.5 to 4.0.5 (karaf maven plugin behavior changes)

[Oliver Lietz]

On Sunday 12 June 2016 16:29:21 Richard Kosegi wrote:
> Hi Karaf folks,

Hello Richard,

> I have a question about changed behaviour of karaf-maven-plugin between
> versions 3.0.5 and 4.0.5.
> 
> While using 3.0.5 my feature is correctly recognized in "assembly"  goal,
> where in 4.0.5 it is not due to this error:
> 
> Caused by: org.apache.maven.plugin.MojoExecutionException: Unable to build
> assembly
> at org.apache.karaf.tooling.AssemblyMojo.execute(AssemblyMojo.java:234)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPl
> uginManager.java:134) at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:2
> 08) ... 20 more
> Caused by: java.lang.IllegalStateException: Could not find matching feature
> for myfeature-thirdparty/0.2.4-SNAPSHOT
> at
> org.apache.karaf.profile.assembly.Builder.addFeatures(Builder.java:1079)
> at
> org.apache.karaf.profile.assembly.Builder.addFeatures(Builder.java:1072)
> at
> org.apache.karaf.profile.assembly.Builder.addFeatures(Builder.java:1072)
> at org.apache.karaf.profile.assembly.Builder.bootStage(Builder.java:811)
> at
> org.apache.karaf.profile.assembly.Builder.doGenerateAssembly(Builder.java:61
> 1) at
> org.apache.karaf.profile.assembly.Builder.generateAssembly(Builder.java:389)
> at
> org.apache.karaf.tooling.AssemblyMojo.doExecute(AssemblyMojo.java:392)
> at org.apache.karaf.tooling.AssemblyMojo.execute(AssemblyMojo.java:228)
> ... 22 more
> 
> Problem seems to be somehow connected to how OSGi versions artifacts versus
> how maven versions snapshots.
> I'm assuming that this only affects SNAPSHOT versions.
> 
> Here is my feature:
> 
>  description="My all features" version="${project.version}">
> myfeature-thirdparty
> myfeature-core 
> 
> 
> I was able to workaround this problem by ugly hack below, but I guess I'm
> missing something very elemenary.

no. This is a known issue: https://issues.apache.org/jira/browse/KARAF-4105

I hope Jean-Baptiste finds some time to look into this.
In the meantime you could use the patch from Markus Rathgeb.

> Please suggest.
> 
> Here is ugly hack:
> 
> 
> git diff -- ./src/main/java/org/apache/karaf/profile/assembly/Builder.java
> diff --git
> a/profile/src/main/java/org/apache/karaf/profile/assembly/Builder.java
> b/profile/src/main/java/org/apache/karaf/profile/assembly/Builder.java
> index b4daa50..de47483 100644
> --- a/profile/src/main/java/org/apache/karaf/profile/assembly/Builder.java
> +++ b/profile/src/main/java/org/apache/karaf/profile/assembly/Builder.java
> @@ -1094,7 +1094,7 @@ public class Builder {
>   * @return
>   */
>  private boolean matches(Feature f, Dependency featureRef) {
> -String version = featureRef.getVersion();
> +String version = featureRef.getVersion().replace("-SNAPSHOT",
> ".SNAPSHOT");
>  return f.getName().equals(featureRef.getName())
>  && (version == null || version.equals("0.0.0")||
> version.startsWith("[") || f.getVersion().equals(version));
>  }
> 

Regards,
O.

> Thanks!
> 
> Richard.

Re: Apache Sling on Karaf 4.0

[Oliver Lietz]

On Wednesday 08 July 2015 13:26:35 Guillaume Nodet wrote:

hi Guillaume,

 I commented on SLING-4412.
 I think you're simply missing the wrap url handler, so try installing the
 wrap feature before the sling one.
 Alternatively, if you switch to the 1.3 namespace, you can add a feature
 prerequisite=truewrap/feature in your sling feature definition.

see my comment in SLING-4412 regarding wrap.
The problem with dependency=true when using 1.2 is unrelated and still exists.

Regards,
O.

 2015-07-08 12:42 GMT+02:00 Oliver Lietz apa...@oliverlietz.de:
  On Sunday 05 July 2015 21:24:07 Jean-Baptiste Onofré wrote:
   It could be a bug indeed. Let me take a look on SLING-4412.
  
  Any ideas what goes wrong?
  
   In the mean time, can you try to change the req enforcement mode in
   etc/org.apache.karaf.features.cfg just to be sure ?
  
  Tested with all possible values, SLING-4412 updated.
  
  Regards,
  O.
  
   Regards
   JB
   
   On 07/05/2015 09:19 PM, Oliver Lietz wrote:
On Sunday 05 July 2015 20:47:56 Jean-Baptiste Onofré wrote:
Hi Oliver,

hi Jean-Baptiste,

if you want to migrate smoothly, you can still use features xmlns 
1.3.0: it should work as before.

If you want to use new style features repository XML (xmlns =
1.3.0),
in that case you use the new features resolver.

The dependency attribute is no more required with xmlns 1.3.0 as the
resolver deals with that.

the XML namespace is still 1.2.0 - so maybe a bug?

What happens on 3.x with new style features in degraded mode without
dependency attribute?

Regards,
O.

Regards
JB

On 07/05/2015 08:35 PM, Oliver Lietz wrote:
hi,

I'm trying to bring Sling's Karaf features to Karaf 4.0 but
encounter
some
problems. So far there is a problem with dependency=true for bundles
  
  and
  
the wrap protocol (may be related to Pax Exam?).

I've documented my findings in SLING-4412 and added a patch (against
trunk)
which updates Karaf from 3.0.3 to 4.0.1-SNAPSHOT and removes the
dependency
attribute (workaround).

Can someone with understanding of the new resolver have a look what
  
  goes
  
wrong, please?

Thanks,
O.

https://issues.apache.org/jira/browse/SLING-4412

Re: Apache Sling on Karaf 4.0

[Oliver Lietz]

On Sunday 05 July 2015 21:24:07 Jean-Baptiste Onofré wrote:
 It could be a bug indeed. Let me take a look on SLING-4412.

Any ideas what goes wrong?

 In the mean time, can you try to change the req enforcement mode in
 etc/org.apache.karaf.features.cfg just to be sure ?

Tested with all possible values, SLING-4412 updated.

Regards,
O.

 Regards
 JB
 
 On 07/05/2015 09:19 PM, Oliver Lietz wrote:
  On Sunday 05 July 2015 20:47:56 Jean-Baptiste Onofré wrote:
  Hi Oliver,
  
  hi Jean-Baptiste,
  
  if you want to migrate smoothly, you can still use features xmlns 
  1.3.0: it should work as before.
  
  If you want to use new style features repository XML (xmlns = 1.3.0),
  in that case you use the new features resolver.
  
  The dependency attribute is no more required with xmlns 1.3.0 as the
  resolver deals with that.
  
  the XML namespace is still 1.2.0 - so maybe a bug?
  
  What happens on 3.x with new style features in degraded mode without
  dependency attribute?
  
  Regards,
  O.
  
  Regards
  JB
  
  On 07/05/2015 08:35 PM, Oliver Lietz wrote:
  hi,
  
  I'm trying to bring Sling's Karaf features to Karaf 4.0 but encounter
  some
  problems. So far there is a problem with dependency=true for bundles and
  the wrap protocol (may be related to Pax Exam?).
  
  I've documented my findings in SLING-4412 and added a patch (against
  trunk)
  which updates Karaf from 3.0.3 to 4.0.1-SNAPSHOT and removes the
  dependency
  attribute (workaround).
  
  Can someone with understanding of the new resolver have a look what goes
  wrong, please?
  
  Thanks,
  O.
  
  https://issues.apache.org/jira/browse/SLING-4412

Apache Sling on Karaf 4.0

[Oliver Lietz]

hi,

I'm trying to bring Sling's Karaf features to Karaf 4.0 but encounter some 
problems. So far there is a problem with dependency=true for bundles and the 
wrap protocol (may be related to Pax Exam?).

I've documented my findings in SLING-4412 and added a patch (against trunk) 
which updates Karaf from 3.0.3 to 4.0.1-SNAPSHOT and removes the dependency 
attribute (workaround).

Can someone with understanding of the new resolver have a look what goes 
wrong, please?

Thanks,
O.

https://issues.apache.org/jira/browse/SLING-4412

Re: Apache Sling on Karaf 4.0

[Oliver Lietz]

On Sunday 05 July 2015 20:47:56 Jean-Baptiste Onofré wrote:
 Hi Oliver,

hi Jean-Baptiste,

 if you want to migrate smoothly, you can still use features xmlns 
 1.3.0: it should work as before.
 
 If you want to use new style features repository XML (xmlns = 1.3.0),
 in that case you use the new features resolver.
 
 The dependency attribute is no more required with xmlns 1.3.0 as the
 resolver deals with that.

the XML namespace is still 1.2.0 - so maybe a bug?

What happens on 3.x with new style features in degraded mode without 
dependency attribute?

Regards,
O.

 Regards
 JB
 
 On 07/05/2015 08:35 PM, Oliver Lietz wrote:
  hi,
  
  I'm trying to bring Sling's Karaf features to Karaf 4.0 but encounter some
  problems. So far there is a problem with dependency=true for bundles and
  the wrap protocol (may be related to Pax Exam?).
  
  I've documented my findings in SLING-4412 and added a patch (against
  trunk)
  which updates Karaf from 3.0.3 to 4.0.1-SNAPSHOT and removes the
  dependency
  attribute (workaround).
  
  Can someone with understanding of the new resolver have a look what goes
  wrong, please?
  
  Thanks,
  O.
  
  https://issues.apache.org/jira/browse/SLING-4412

integration tests fail with Karaf 3.0.0 and Pax Exam

[Oliver Lietz]

hello all,

the integration tests for Sling Launchpad Karaf[1] fail when upgrading Karaf 
from 3.0.0.RC1 to 3.0.0 with java.lang.ClassNotFoundException: 
org.apache.sling.launchpad.karaf.testing.KarafTestSupport not found by 
PAXEXAM-PROBE-[...].
Upgrading Pax Exam to 3.4.0 or 3.5.0-SNAPSHOT does not help. Any ideas?

thanks,
O.

[1] 
http://svn.apache.org/viewvc/sling/trunk/contrib/launchpad/karaf/org.apache.sling.launchpad.karaf-
integration-tests/

Re: integration tests fail with Karaf 3.0.0 and Pax Exam

[Oliver Lietz]

Am Freitag, 27. Dezember 2013 schrieb Achim Nierbeck:
 The tools for testing are now included with pax-exam. You just need to use
 those.

hello Achim,

I already use them from Pax Exam. The integration tests for Sling Launchpad 
Karaf look very similar to yours in Camel-Pax-Exam-Demo (which uses Karaf 
2.2.11). I think you will face the same problem when upgrading to 3.0.0. Btw 
you can remove the dependency org.apache.kataf.tooling.exam.options from 
route-control/pom.xml.

regards,
O.

 Regards, Achim
 
 sent from mobile device
 
 Am 27.12.2013 14:28 schrieb Oliver Lietz apa...@oliverlietz.de:
  hello all,
  
  the integration tests for Sling Launchpad Karaf[1] fail when upgrading
  Karaf
  from 3.0.0.RC1 to 3.0.0 with java.lang.ClassNotFoundException:
  org.apache.sling.launchpad.karaf.testing.KarafTestSupport not found by
  PAXEXAM-PROBE-[...].
  Upgrading Pax Exam to 3.4.0 or 3.5.0-SNAPSHOT does not help. Any ideas?
  
  thanks,
  O.
  
  [1]
  
  http://svn.apache.org/viewvc/sling/trunk/contrib/launchpad/karaf/org.apac
  he.sling.launchpad.karaf- integration-tests/

Re: integration tests fail with Karaf 3.0.0 and Pax Exam

[Oliver Lietz]

Am Freitag, 27. Dezember 2013 schrieb Oliver Lietz:
 Am Freitag, 27. Dezember 2013 schrieb Achim Nierbeck:
  The tools for testing are now included with pax-exam. You just need to
  use those.
 
 hello Achim,
 
 I already use them from Pax Exam. The integration tests for Sling Launchpad
 Karaf look very similar to yours in Camel-Pax-Exam-Demo (which uses Karaf
 2.2.11). I think you will face the same problem when upgrading to 3.0.0.
 Btw you can remove the dependency org.apache.kataf.tooling.exam.options
 from route-control/pom.xml.

solved by adding useDeployFolder(false) AND switching from bundle() to 
streamBundle():

http://svn.apache.org/viewvc?view=revisionrevision=1553688

(cross-checked with Achim's Camel-Pax-Exam-Demo, removing 
useDeployFolder(false) after upgrading to Karaf 3.0.0 breaks the tests)

I don't think that this is documented anywhere (Karaf/Pax Exam).

regards,
O.

 regards,
 O.
 
  Regards, Achim
  
  sent from mobile device
  
  Am 27.12.2013 14:28 schrieb Oliver Lietz apa...@oliverlietz.de:
   hello all,
   
   the integration tests for Sling Launchpad Karaf[1] fail when upgrading
   Karaf
   from 3.0.0.RC1 to 3.0.0 with java.lang.ClassNotFoundException:
   org.apache.sling.launchpad.karaf.testing.KarafTestSupport not found by
   PAXEXAM-PROBE-[...].
   Upgrading Pax Exam to 3.4.0 or 3.5.0-SNAPSHOT does not help. Any ideas?
   
   thanks,
   O.
   
   [1]
   
   http://svn.apache.org/viewvc/sling/trunk/contrib/launchpad/karaf/org.ap
   ac he.sling.launchpad.karaf- integration-tests/

Re: [VOTE] Release Apache Karaf version 3.0.0.RC1

[Oliver Lietz]

Am Tuesday, 12. March 2013 schrieb Jamie G.:
 Hi,
 
 We resolved 964 issues in this release (web page will be published
 post RC promotion):
 https://svn.apache.org/repos/asf/karaf/site/trunk/src/main/webapp/index/com
 munity/download/karaf-3.0.0.RC1-release.page
 
 NOTE: This is a technology preview release candidate.
 
 Staging repository:
 https://repository.apache.org/content/repositories/orgapachekaraf-019/
 
 Release tags:
 https://svn.apache.org/repos/asf/karaf/tags/karaf-3.0.0.RC1/
 
 3.0.x Dependencies table:
 https://svn.apache.org/repos/asf/karaf/site/trunk/src/main/webapp/index/doc
 umentation/karaf-dependencies/karaf-deps-3.0.x.page
 
 Please vote to approve this release:
 
 [ ] +1 Approve the release
 [ ] -1 Veto the release (please provide specific comments)
 
 This vote will be open for 72 hours.

build fails:

Tests in error: 
  
listViaMBean:org.apache.karaf.itests.WebTest.listViaMBean:KarafTestContainer{mvn:org.apache.karaf\/apache-
karaf\/3.0.0.RC1\/tar.gz}(org.apache.karaf.itests.WebTest): 
org.apache.karaf:type=web,name=root

https://gist.github.com/oliverlietz/5142210

Re: [VOTE] Release Apache Karaf version 3.0.0.RC1

[Oliver Lietz]

Am Tuesday, 12. March 2013 schrieb Jean-Baptiste Onofré:
 Hi,

hello JB,

 it's random test failures.
 
 Could you try a couple of more times ?

random, indeed. What is causing this random failures? Is it related to Pax Web 
where I've also random test failures?

thanks,
O.

 Thanks,
 Regards
 JB
 
 On 03/12/2013 12:41 PM, Oliver Lietz wrote:
  Am Tuesday, 12. March 2013 schrieb Jamie G.:
  Hi,
  
  We resolved 964 issues in this release (web page will be published
  post RC promotion):
  https://svn.apache.org/repos/asf/karaf/site/trunk/src/main/webapp/index/
  com munity/download/karaf-3.0.0.RC1-release.page
  
  NOTE: This is a technology preview release candidate.
  
  Staging repository:
  https://repository.apache.org/content/repositories/orgapachekaraf-019/
  
  Release tags:
  https://svn.apache.org/repos/asf/karaf/tags/karaf-3.0.0.RC1/
  
  3.0.x Dependencies table:
  https://svn.apache.org/repos/asf/karaf/site/trunk/src/main/webapp/index/
  doc umentation/karaf-dependencies/karaf-deps-3.0.x.page
  
  Please vote to approve this release:
  
  [ ] +1 Approve the release
  [ ] -1 Veto the release (please provide specific comments)
  
  This vote will be open for 72 hours.
  
  build fails:
  
  Tests in error:
 listViaMBean:org.apache.karaf.itests.WebTest.listViaMBean:KarafTestCon
 tainer{mvn:org.apache.karaf\/apache-
  
  karaf\/3.0.0.RC1\/tar.gz}(org.apache.karaf.itests.WebTest):
  org.apache.karaf:type=web,name=root
  
  https://gist.github.com/oliverlietz/5142210