This code is actually not AAA specific... org.ops4j.pax.web.cfg is laid down by karaf, which is provided by odlparent, so adding in that mailing list. It looks like you aren't following those

Hi Michael, As mentioned in the last two kernel calls, I want to release 3.0.2 with as few changes as possible compared to the current snapshot, since that’s what we’ve been testing all the

Michael Vorburger <vorburger@...> wrote: Ah, now I remember! The directive was present in the initial caches commit, along with the Import-Package directive with a version range; I removed the

FYI anyone interested in (automatic configuration of) SpotBugs support in Eclipse: I've finally found the time tonight for putting together

Stephen, can we still get the following merged soon-ish for odlparent 3.0.2, in order of priority: 1. https://git.opendaylight.org/gerrit/#/c/66626: spotbugs-maven-plugin bump 2.

Tom & Stephen, re. the <Karaf-Commands>* thing we were talking about during the Kernel Projects call earlier: now realized that I had added it to

Tom Pantelis <tompantelis@...> wrote: Yes, it’s in 3.0.2-SNAPSHOT now (thanks to Michael for merging the patch). Regards, Stephen

Hello again to anyone interested in http://errorprone.info, I just wanted to let folks know that I'm meanwhile successfully using error-prone in all of infrautils - I like it, and to me it seems

> >> > - Normal log output seems to be lost, ie it doesn't go to the > >> > karaf.log. log:display shows nothing. ERROR output like above is > >> > directed to the karaf console. Not good.... > >> >

Very good, thanks for keeping it backwards compatible.

Tom Pantelis <tompantelis@...> wrote: Yeah. Having enabled the logs I’m seeing more detailed exceptions which are probably involved here... Yes, anyone with specific logging configuration

I'll push a patch to change this to debug. I don't think it's worth trying to figure out why the error happens for those 2 bundles, especially since they're not our bundles and wouldn't have CSS XML

This is going to break all of our configuration management tooling. Can you give some docs about how we (and users) should migrate?

Hi Tom, Tom Pantelis <tompantelis@...> wrote: I’ve seen these too, and they do seem benign (diag doesn’t complain once they stop). I think this is related to the switch from Log4J to

Hello, I gave the controller karaf distro a spin with the new version. A few weird things I noticed: - I see a lot of these errors repeated: 03:16:08.712 [ConfigFeatureListener - ConfigPusher] ERROR

Hello all odlparent interested parties (not just committers), I am curious about your views re. https://git.opendaylight.org/gerrit/#/c/66270/ and invite you all to vote with +1 or -1 about where you

Hi michael, Yes, we will add these to the test environment, and get back to you if we still face any complications. Besides that, just wanted to get an idea of the outlook for this bug to see if its

Faseela, are you aware of the workaround(s) available for this problem? I've just updated https://jira.opendaylight.org/projects/ODLPARENT/issues/ODLPARENT-113 with a comment.. particularly that

The priority just now is getting odlparent 3 working for everyone (starting with AAA) :-(. The SSH picture is changing a bit with the various Karaf upgrades too, which affects 113, but I would like to

Thanks for the update Stephen! Is this something in plan to be fixed for Oxygen? I donot see the TR assigned to anyone, so assuming that is not in the priority list? Thanks, Faseela