Re: Some logs are missing when the Configuration is updated via ConfigurationAdmin

Hi, Yes we are missing some logs, due to the asynchronous nature of the configuration update, there is a gap between the configuration update via ConfigurationAdmin and receiving the update to the ManagedService (in the PaxLoggingServiceImpl). I further looked into the pax logging code and I

Re: Pax Logging release?

On 2016-09-06 07:48:55 -0700, r...@evosent.com wrote: > Actually, this only affected the pax-logging-log4j2 module, right? No, all modules. > What prevents these users from running pax-logging-api 1.8.5 with > pax-logging-log4j2 with 1.8.1? > > Our OSGi import version ranges are pretty lax:

Re: Pax CDI and Camel...testing...

It makes me wonder if since this is still in RC if the @OSGiServiceProvider and @OSGiService shouldn't just be removed. Or, at the very least, market as deprecated. On Tue, Sep 6, 2016 at 10:53 AM, Brad Johnson wrote: > A very cool. Thank you. I'll give that a

Re: Pax CDI and Camel...testing...

A very cool. Thank you. I'll give that a shot. And I agree with 100% that having to specify a start order is a recipe for spaghetti and circular dependencies that could make you pull your hair out. On Mon, Sep 5, 2016 at 2:47 PM, Guillaume Nodet wrote: > Yeah, that looks

[ANN] OPS4J Pax Logging 1.8.6 Released

Hi, The Pax Logging team is happy to announce the release of *OPS4J Pax Logging 1.8.6*. This is a minor release with couple of bug fixes. See announce for details: https://ops4j1.jira.com/wiki/display/paxlogging/2016/09/06/Pax+Logging+1.8.6+Released Enjoy. Pax Logging Team -- --

Re: Pax Logging release?

I did Pax Logging 1.8.6 release. I'm preparing the announcement and update on wiki. Regards JB On Tuesday, September 6, 2016 at 4:48:55 PM UTC+2, ra...@evosent.com wrote: > > Actually, this only affected the pax-logging-log4j2 module, right? > > What prevents these users from running

Re: Pax Logging release?

Agree, but not on a minor release. Pax Logging 1.8.1 worked on Java6 and we broke this on 1.8.5, which is unfortunate (it should have been a 1.9.0 at that time). It's not a big deal, but some users complained. Regards JB On Tuesday, September 6, 2016 at 4:31:27 PM UTC+2, ra...@evosent.com

Re: Pax Logging release?

I don't think this project should be accommodating of the minimal minority who still run JDK6 – which is end-of-life since 2012 – and, as a consequence, forcing old versions on the rest of the world. If anything, users still clinging to JDK6 should understand they cannot get the latest kid on

Re: Pax Logging release?

Correct, I meant Java7 (not Java8). On Tuesday, September 6, 2016 at 4:18:32 PM UTC+2, Matt Sicker wrote: > > I thought the problem was that it required Java 7, not 8. None of the > pax-logging dependencies require Java 8. > > On 6 September 2016 at 09:16, Jean-Baptiste Onofré

Re: Pax Logging release?

We discussed while ago to a Java version change we did on Pax Logging 1.8.x: this version requires Java8 whereas it was supposed to work with Java6 as well. So, what I propose is to release 1.8.6 asap and prepare the rollback of Java8 requirement. Regards JB On Tuesday, September 6, 2016 at

pax runner eclipse plugin?

Hello. https://ops4j1.jira.com/wiki/display/paxrunner/Plugin+Installation The wiki points to an update site that does not exist. Is the plugin still alive? M -- -- -- OPS4J - http://www.ops4j.org - ops4j@googlegroups.com --- You received this message because you are