Re: Logging service 1.5.0 not exported in karaf 4.4.1

[Steinar Bang <sb...@dod.no>]

>>>>> Grzegorz Grzybek <gr...@gmail.com>:

> Hello
> There's (still) unresolved
> https://github.com/ops4j/org.ops4j.pax.logging/issues/410 issue. And yes -
> Pax Logging exports at most version 1.4 because there were no big reasons
> to bump this version... However I agree that users with
> org.osgi.service.log 1.5 on the classpath will have "[1.5,2)" generated by
> maven-bundle-plugin...

The issue was that the karaf 4.4.0 and 4.4.1 BOM will pull in logservice
1.5.0, and my expectation of a BOM is that things should work out of the
box.

So IMO either the BOM should be changed or karaf should be changed to
offer up both version 1.4.0 and 1.5.0 of org.osgi.service.log.

Hm... but maybe I can override the org.osgi.service.log version set by
the BOM?

And maybe I should move the import config of maven-bundle-plugin to
plugin mangement in the parent POM?

Both would give me less pom config.

Overriding the org.osgi.service.log version set by the BOM would be the
simplest solution, if possible.

(But ideally it should work out the box)

Re: Logging service 1.5.0 not exported in karaf 4.4.1

[Steinar Bang <sb...@dod.no>]

>>>>> Steinar Bang <sb...@dod.no>:

> Hm... but maybe I can override the org.osgi.service.log version set by
> the BOM?

Nope.  Tried that, didn't work.

> And maybe I should move the import config of maven-bundle-plugin to
> plugin mangement in the parent POM?

But this, on the other hand, worked.

<configuration> content is mixed with existing <configuration> content
where maven-bundle-plugin is actually used.

So the <Import-Package> is added to whatever is there already.

> Both would give me less pom config.

The working one gives less config.

> Overriding the org.osgi.service.log version set by the BOM would be the
> simplest solution, if possible.

But unfortunately didn't work

> (But ideally it should work out the box)

Yep.